Subscribe to Demos
<100 subscribers
Support Demos
DemosWhat's New in Demos Yellow Paper v8
Share Dialog
Share Dialog
High-throughput blockchain infrastructure needs efficient node-to-node communication. Standard HTTP+JSON protocols work fine for developers but carry a lot of overhead. Headers, brackets, whitespace, formatting. It adds up.
v8 introduces OmniProtocol, a custom binary protocol built directly over raw TCP. The network's communication now splits into two layers:
Public-facing layer (for dApps, wallets, developers): Still HTTP+JSON. Readability and ease of integration matter here.
Internal peer-to-peer layer: Rebuilt using compressed binary data. Stripping out everything meant for human readability cuts request size by roughly 70%.
Developers still get a clean API. The network gets the throughput it needs.
In 2025 we introduced DAHR (Data Agnostic HTTP(S) Relay) proxies for accessing Web2 data on-chain. v8 keeps that and adds a second approach for scenarios that need stronger guarantees.
Optimized for speed and cost. DAHR proxies monitor and attest to Web2 communications without decrypting traffic, giving you near-instant finality with minimal overhead. For most use cases this is still the right choice.
New in v8. Uses secure multi-party computation (MPC) to cryptographically prove the authenticity of entire TLS sessions. Takes longer than DAHR because you're generating and notarizing proofs. But for high-stakes applications where you need irrefutable proof (financial data, legal documents, sensitive verifications), TLSNotary provides guarantees that hash-based monitoring cannot.
High-throughput blockchain infrastructure needs efficient node-to-node communication. Standard HTTP+JSON protocols work fine for developers but carry a lot of overhead. Headers, brackets, whitespace, formatting. It adds up.
v8 introduces OmniProtocol, a custom binary protocol built directly over raw TCP. The network's communication now splits into two layers:
Public-facing layer (for dApps, wallets, developers): Still HTTP+JSON. Readability and ease of integration matter here.
Internal peer-to-peer layer: Rebuilt using compressed binary data. Stripping out everything meant for human readability cuts request size by roughly 70%.
Developers still get a clean API. The network gets the throughput it needs.
In 2025 we introduced DAHR (Data Agnostic HTTP(S) Relay) proxies for accessing Web2 data on-chain. v8 keeps that and adds a second approach for scenarios that need stronger guarantees.
Optimized for speed and cost. DAHR proxies monitor and attest to Web2 communications without decrypting traffic, giving you near-instant finality with minimal overhead. For most use cases this is still the right choice.
New in v8. Uses secure multi-party computation (MPC) to cryptographically prove the authenticity of entire TLS sessions. Takes longer than DAHR because you're generating and notarizing proofs. But for high-stakes applications where you need irrefutable proof (financial data, legal documents, sensitive verifications), TLSNotary provides guarantees that hash-based monitoring cannot.
Different applications have different requirements. A price feed aggregator and a legal attestation system shouldn't use the same trust model.
v8 adds decentralized storage as a first-class network feature by integrating IPFS directly into the node architecture.
Each node runs within a private swarm, separate from public IPFS. This improves performance and lets the network enforce its own economic model.
How it works:
Content-addressed storage with automatic deduplication
Time-limited pins with flexible duration pricing
Streaming support for large files (256KB chunks)
Genesis account benefits including free allocation and reduced rates
Storage fees go directly to nodes providing hosting capacity
Usage generates rewards for storage providers, which should bring more capacity online and reduce costs over time.
The Native Bridge functionality hasn't changed technically, but v8 adds detailed phase diagrams that make the workflow clearer:
Phase 1: Client Request & Validation
Phase 2: Deposit Execution
Phase 3: Consensus & Withdrawal
Easier for developers integrating cross-chain transfers.
The v8 updates follow a consistent pattern: provide options instead of forcing one approach on everyone.
OmniProtocol lets internal efficiency coexist with external developer experience. The dual Web2 approach lets applications choose their own security/speed trade-off. IPFS integration adds storage without external dependencies.
These aren't incremental patches. v8 positions Demos as genuinely full-stack Omniweb infrastructure: optimized communication, flexible Web2 attestation, and native decentralized storage all working together. The pieces are falling into place for a network that can handle real-world complexity across chains and contexts.
The complete Yellow Paper v8 is available at https://github.com/kynesyslabs/demos_yellowpaper
Different applications have different requirements. A price feed aggregator and a legal attestation system shouldn't use the same trust model.
v8 adds decentralized storage as a first-class network feature by integrating IPFS directly into the node architecture.
Each node runs within a private swarm, separate from public IPFS. This improves performance and lets the network enforce its own economic model.
How it works:
Content-addressed storage with automatic deduplication
Time-limited pins with flexible duration pricing
Streaming support for large files (256KB chunks)
Genesis account benefits including free allocation and reduced rates
Storage fees go directly to nodes providing hosting capacity
Usage generates rewards for storage providers, which should bring more capacity online and reduce costs over time.
The Native Bridge functionality hasn't changed technically, but v8 adds detailed phase diagrams that make the workflow clearer:
Phase 1: Client Request & Validation
Phase 2: Deposit Execution
Phase 3: Consensus & Withdrawal
Easier for developers integrating cross-chain transfers.
The v8 updates follow a consistent pattern: provide options instead of forcing one approach on everyone.
OmniProtocol lets internal efficiency coexist with external developer experience. The dual Web2 approach lets applications choose their own security/speed trade-off. IPFS integration adds storage without external dependencies.
These aren't incremental patches. v8 positions Demos as genuinely full-stack Omniweb infrastructure: optimized communication, flexible Web2 attestation, and native decentralized storage all working together. The pieces are falling into place for a network that can handle real-world complexity across chains and contexts.
The complete Yellow Paper v8 is available at https://github.com/kynesyslabs/demos_yellowpaper
No comments yet