Liquid rails for
verifiable state
Chrome is a thin settlement protocol for teams who care about receipts. Nodes gossip state, light clients verify, and nothing important lives only in someone else's dashboard.
Wire format
Every message is a compact envelope. Payload bytes are opaque to the router. Signatures cover the header and the payload hash together.
Envelope sketch
type Envelope = {
// 8 byte network prefix
net: "chr-main" | "chr-test";
seq: uint64;
from: NodeId;
to?: NodeId;
payload: bytes;
sig: bytes65;
};
Payloads carry state roots, light-client proofs, or governance votes. If a node cannot verify a signature it drops the envelope and logs a miss.
RPC methods
Light clients speak a short dialect. Full nodes accept these over WebSocket or raw TCP.
| Method | Purpose | Returns |
|---|---|---|
chr.head |
Latest confirmed state root | root + height |
chr.prove |
Membership proof for a key | proof bytes |
chr.gossip |
Subscribe to peer envelopes | stream |
chr.vote |
Submit a governance ballot | receipt |
Example call
const proof = await rpc.call("chr.prove", {
key: "acct/0x4f…c2",
height: 18422,
});
// verify locally before trusting the UI
assert(verify(proof, head.root));
Playground
Pick a method, change the params, run it. The request is what your client would send. The response is simulated for this page, and the proof check runs the same steps a light client would.
FAQ
Do I need to run a full node?
No. Light clients verify proofs against the latest head and never trust a dashboard alone.
What happens to an envelope with a bad signature?
The receiving node drops it and logs a miss. Nothing is forwarded.
Is there a test network?
Yes, chr-test mirrors the main network rules and resets on spec changes.
Can you help us integrate?
Write to the maintainers below with what you are building and the method you are stuck on.
Talk to the maintainers
Integration questions, audits, or a node operator role. Tell us what you are building.
Maintainers
AuraicPulse · Creative Studio
Protocol notes from Cape Town. If a diagram is wrong, open a PR. If a proof fails, open an issue with the envelope bytes.
Field notes
Conventions
- Hex strings are lowercase and never abbreviated in proofs.
- Sequence numbers are local to the sender and may wrap.
- Spec changes need two maintainers and one live testnet replay.