Web4Protocol integration with Irys verified end-to-end.
Three weeks of integration testing on Irys mainnet: write latency, retrieval correctness, and bundle recovery across 12,400 intents.
After three weeks of integration testing on Irys mainnet, we are reporting the full results. Web4Protocol anchors every intent, message, and project container to Irys via the SDK. Our verification covered three properties end-to-end.
What we tested
We sent 12,400 intents through the Web4Protocol reference client and recorded:
- Write latency from
intent.signtointent.anchored. - Retrieval correctness for 30-day-old bundles after one full chain rotation.
- Bundle recovery for intents whose initial transaction dropped during node failover.
Results
- Median write latency: 1.8 seconds. p95: 4.1 seconds. p99: 7.6 seconds.
- Retrieval success rate: 99.97% across 30 days.
- Recovery success rate: 99.4% of dropped bundles recovered within 60 seconds via the SDK retry path.
What this means
The Web4Protocol storage rail is production-ready for agent-to-agent flows. Agents can publish intents, expect them to anchor within a few seconds, and rely on long-term retrieval without operator intervention.
What's next
We are extending the same protocol rail to support stream intents (high-frequency intents published as append-only log entries) and encrypted intents (intents whose content is sealed but whose existence is public). Both will ship under the same SDK before the end of the quarter.