Protocol Specification
This section is the canonical reference for the XChain Protocol; ACTION command formats, token metadata standards, database naming conventions, and machine-readable JSON schemas. Intended for protocol developers, indexer implementors, and anyone building tools that must interoperate with the platform at the data level.
| Resource | Description |
|---|---|
| ACTION Specifications | Authoritative format specs for every named ACTION command |
| ACTION Manifest | The authoritative cross-repo ACTION registry (action-manifest.json) and the conformance tests that enforce it |
| Token Information Standard | Standard for token metadata fields and discovery |
| Token-Gated Content | End-to-end design for cryptographically secure token-gated file publishing (single files and packs) |
| Taproot Envelope | Large-payload carrier for Bitcoin and Litecoin: one commit/reveal pair writes a whole file into a single tapscript witness |
| NFT Standard | Non-fungible tokens as a composition of existing primitives: uniques, editions, collections, content attachment, display |
| Project Registry Standard | Chain-native curated directories; a project tick attests its official tokens via an owner-validated LIST + LINK roster |
| Controller-Bound Tokens | Programmable policy layer: a contract gates native actions on a bound token or address, with royalty enforcement |
| Contract ABI | Optional self-declared display metadata (method summaries, typed params, read-only flags) contracts export for wallets and explorers |
| Contract-Targeted Staking | Design and VM API for staking any token against a smart contract with contract-decided slashing |
| Cross-Chain Contract Calls | XCALL: a contract on one chain calls a contract on another, verified by federation capability signatures |
| Cross-Chain DEX | Network-scoped mirror settlement: trading a token on one chain against a token on another |
| x402 Payments | HTTP 402 payment interop: machine-payable web resources settled with XChain actions |
| Attestation Providers | Provider specs for the attestation framework (http_get, llm) |
| Error Codes | Stable machine-readable error-code registry |
| XChain URI Scheme | Cross-chain payment and action URI format for QR codes, deep links, and clipboard payloads |
| Index ID References | The ^<id> compact wire form for tickers and addresses, and the deterministic reorg-safe id assignment rule |
| Database Naming Structure | Naming conventions for all platform databases |
| Protocol Activation (Flag Days) | How consensus changes activate: the per-network time/height gate, the three activation cohorts, and forking vs halt-recoverable straggler behavior |
| Upgrade Notice Policy | Minimum lead time between a release carrying consensus activation values and the moment they fire |
| JSON Schemas | Machine-readable schemas for ACTION payloads and API responses |
Copyright © 2025–2026 Dankest, LLC
Based on XChain Platform by Dankest, LLC – https://dankest.llc
Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-or-later) with a commercial license available for proprietary use.
You may use, modify, and distribute this material under the terms of the License. See LICENSE and NOTICE for full terms. See the licensing overview.