Protocol v1
Protocol model
Canonical identifiers, event facts, registries, and version discovery.
Detalk's protocol is designed so multiple implementations derive the same identifiers and rebuild the same canonical state.
Stable identifiers
channelIdis derived from the execution chain ID and target EVM address. CAIP-10 is an external representation, not the hashed string.- Public and custom subchannel identifiers use explicit ABI encoding. The current product presents one main discussion, even though the versioned protocol reserves structured identifiers.
messageIdcommits to the protocol version, chain, registry, channel, author, author nonce, kind, reference, paid amount, and content hash.
Implementations use abi.encode, fixed integer widths, and raw submitted content bytes. They must not silently normalize text before computing an ID.
Discovery
A protocol version is discovered through an immutable registry bundle containing the Message Registry, Channel Manager, Payment Membership, Session Key Registry, earliest start block, and schema hash. Deployments are not valid documentation until their network, addresses, start blocks, source verification, and schema hash are published.