
Hyperspace Protocol
@hyperspaceagi
Agentic protocol
ID: 1849200590493978624
http://hyperspaceprotocol.ai 23-10-2024 21:26:06
19 Tweet
466 Takipçi
19 Takip Edilen


toly 🇺🇸 Dankrad Feist mteam.eth 🗼 BREAD | ∑: ZKP recursive batching is not the bottleneck, the issue is all about state. This has been the outline of our design - where based on knowing which transactions impact which state, we “send” them to relevant state committees. What does this yield (per theory): 200k TPS with 4.4s


toly 🇺🇸 Dankrad Feist mteam.eth 🗼 BREAD | ∑: Here's how it scales in our design, which involves generating STARKs based on execution traces (WASM), and then batching STARKs into SNARKs using Plonky2 and "simple batching" instead of other batching methods as this figure shows. docs.google.com/spreadsheets/d…



Varun Dankrad Feist mteam.eth 🗼 BREAD | ∑: Happy to jump on a call. Async execution would allow for very big batching and can be as far as 1 day behind the tip.

Even inside crypto there is massive adverse selection. The teams that care about building agentic workflows, ux and products like Hyperspace are out there building open source ai agents with p2p networks to serve them. Try this out: compute.hyper.space


“..It will be a normalized world for your AI startup to also have a crypto strategy (just like we are doing at Hyperspace + Hyperspace Protocol)”

What’s in a state ? At Hyperspace Protocol we are building our own agentic blockchain protocol for one simple reason: state. A world of billions of AI agents with their own state is simply not feasible on any modern chain, so we must stretch it further and invent the future. When






We are building the fastest blockchain for AI agents to transact Hyperspace Protocol. At 200k TPS with a 4.4 second finality, this design scales.



