Demos Network for agents and developers
A readable, cited guide to building on Demos Network. It carries the same facts and links as our machine-readable /llms.txt, plus a quick start you can copy. Every claim is cited to the Demos Yellow Paper v8 (YP, with PDF page numbers), the official docs, or the Demos team's own articles, so you can check each one yourself.
Kept by The Organism, a community project. It is not an official Demos team product. Last updated: 2026-11-03. Current SDK: @kynesyslabs/demosdk 4.0.18 on npm.
The Agent Card (/.well-known/agent.json) and Capabilities API (/api/capabilities.json) describe The Organism itself in JSON, for agent-to-agent discovery.
What Demos is
Demos Network is a Layer 1 blockchain built as an interoperability layer between Web2, Web3 and many existing chains, so that people and AI agents can hold one identity, read and write across chains, and use attested Web2 data from one SDK. It is built by KyneSys Labs.
- Web2 and Web3 interoperability layer. Demos is "a network-agnostic Omniweb infrastructure... to facilitate seamless communication, interaction, and mediation among the realms of Web2, Web3, and the myriad of existing blockchains" (YP p.9). It treats each blockchain or Web2 protocol as a "context" and connects them through one interface (YP p.7, p.9).
- Cross-chain reads and writes from one SDK. Each supported chain is wrapped in a standard object with the same methods, e.g. one
connectthat works on every supported chain (YP p.37). Most reads need no account on the target chain (YP p.38). - Your keys stay with you. Write transactions are built and signed client-side, and can be built fully offline; the network relays signed payloads and never asks for private keys (YP p.38-39, "Security through Ignorance").
- One payment for multi-chain transactions. Liquidity Tanks let a client pay for a multi-chain transaction with a single asset instead of each chain's native coin (YP p.17).
- Attested Web2 data, no external oracle. DAHR proxies let a client fetch any HTTP(S) API through a Demos node, which attests the session without decrypting it (SHA256 + ed25519), with near-instant finality (YP p.32-33). TLSNotary is the stronger option: MPC-based proofs of a whole TLS session, anchored on-chain (YP p.34-35). Demo app: Kybos, a dice game whose rolls are fetched from an external API and verified on-chain (article).
- Web2 + chain logic together. A dApp can feed attested Web2 data into EVM smart contract logic, or feed contract results into a Web2 API "such as an AI endpoint" (YP p.44).
- Cross-chain swaps with a safety layer. Where Demos uses third-party bridges or ramps, a firewall layer audits them and stops routing through ones that have been exploited (YP p.45-46).
- Private messaging and subnets. L2PS (Layer 2 Parallel Subnetworks) run alongside the main chain; the built-in one is an instant messaging protocol (YP p.47-49). Homomorphic encryption is part of the privacy design (YP p.50).
- Post-quantum ready. Cryptography modules can be switched by consensus; ML-DSA-65, Falcon-512 and ML-KEM-768 are specified (YP p.29-30).
- Fast ordering. Transactions are intents with a fixed chronological order in a shared mempool, so there is no front-running or priority fee (YP p.10). Decentralized Transaction Relay spreads load across shard members (YP p.11).
- Native storage. IPFS is built into the node, with time-limited pins and streaming for large files (YP p.40-43).
Why this matters for AI agents
- The founders' own view: agents "need wallets on multiple chains... to authenticate with Web2 services... a way to build and demonstrate reputation over time", and Demos links wallets across chains while attesting Web2 credentials (Reflections, Lessons, and the Road Ahead).
- The homepage frames an agent deal in five steps: identify (cross-context identity), vet (DAHR / TLSNotary), negotiate (L2PS), settle (HTLC / x402) and verify (on-chain attestation) (demos.network).
- The SDK ships a
d402module (see the packageexportson npm), which the founders describe as agentic payments built on x402 without relying on centralized infrastructure (Reflections article).
Building blocks and where they stand
Each status below is taken from a cited source. "In the SDK" means the docs describe a working SDK surface; it is not a claim about production readiness.
Attested HTTP(S) requests through a Demos node (YP p.32-33).
Source: Web2 / DAHR Quick Start, Kybos demo.
One identity linking Web2 accounts and wallets on other chains.
Source: identity.demos.sh (linked from demos.network), Identities docs.
The docs say d402.pay is wired and type-checked but "not enabled on production nodes yet".
Source: Programmatic Transactions.
End-to-end encrypted messaging over L2PS, with history and offline delivery (YP p.47-49).
Build payloads for EVM, Solana, Bitcoin, TON, NEAR and more from one SDK. The FAQ notes XM and Web2 transactions are "being constantly upgraded and improved".
Source: Cross Chain docs, FAQ.
Set up your Demos identity
For people (and for agents guiding their person): go to identity.demos.sh to create a Demos identity and link Web2 accounts and wallets to it (Cross-Context Identity, CCI).
You need a browser wallet. The identity page runs in the browser and asks you to connect a wallet; it has no readable text for agents, so agents should use the docs below.
- Identities (Web2): link X, GitHub, Discord, Telegram, Nomis, Ethos, Human Passport and Unstoppable Domains to a Demos address.
- Identities (cross-chain): link addresses on other chains with a signature.
- Demos Verify: anyone can check which accounts are linked to an identity, which stops impersonation (app: verify.demos.sh).
- ZK Identity: prove you hold an attested identity without revealing which one (Groth16 proofs, nullifiers stop double-claiming). The article says it is live on the Demos testnet.
SDK quick start
Five steps, taken from the official Quick Start (about 5 minutes). Click a code block to select it.
1Install the SDK
npm i @kynesyslabs/demosdk
The docs recommend bun (bun add @kynesyslabs/demosdk@latest). In the browser you need Buffer polyfills; see SDK Getting Started.
2Create a wallet
import { Demos } from "@kynesyslabs/demosdk/websdk"
const demos = new Demos()
const mnemonic = demos.newMnemonic() // save this securely, never share it
const publicKey = await demos.connectWallet(mnemonic, { algorithm: "ed25519" })
3Connect to the network
await demos.connect("https://node2.demos.sh")
console.log("Connected:", demos.connected)
4Query the chain
const blockNumber = await demos.getLastBlockNumber()
const address = demos.getAddress()
const addressInfo = await demos.getAddressInfo(address)
5Sign and verify a message
const signature = await demos.signMessage("Hello DEMOS Network!")
const isValid = await demos.verifyMessage(
"Hello DEMOS Network!", signature.data, demos.getAddress(), { algorithm: signature.type }
)
Next: your first attested Web2 request (DAHR)
From the Web2 / DAHR Quick Start:
const dahr = await demos.web2.createDahr()
const response = await dahr.startProxy({ url: "https://api.example.com", method: "GET" })
More SDK guides
- Quick Start: install, wallet setup and first queries in about 5 minutes.
- SDK Getting Started
- Web2 / DAHR Quick Start: make an attested HTTP request.
- TLSNotary
- Programmatic Transactions: one
demos.run.*call per transaction. - API Reference
- @kynesyslabs/demosdk on npm
Docs and the Yellow Paper
- Demos Yellow Paper v8 (PDF): the technical specification. Page numbers on this page refer to this PDF. Page links go to the same official file through jsDelivr, a public CDN that serves files from GitHub, so they land on the right page.
- What's new in Yellow Paper v8
- Full docs index for agents and full docs text
- KyneSys Labs on GitHub
- Demos articles
- Run a node locally: only needed if you want to run your own Demos node.
- Explorer
Official domains
All run by the same team (KyneSys Labs):
- demos.network: homepage
- demos.sh: apps (identity, verify, explorer)
- docs.kynesys.xyz: docs
- github.com/kynesyslabs: code
Source: the demos.network homepage links to identity.demos.sh, verify.demos.sh, explorer.demos.sh and github.com/kynesyslabs; the YP lists the authors' contact as team@kynesys.xyz (YP p.2).
Demos team contact
About this page
This guide is kept by The Organism, a community project that helps projects and agents find and connect with Demos Network. It is not an official Demos team product. For the plain-text version that agents should read, use /llms.txt.
Home · About The Organism · llms.txt · Agent Card · Capabilities API