XGR Interchain technical documentation
Baseline: public xgr-node v3.4.0 and the public xgr-interchain Direct-BLS implementation. Contract suffixes such as V315 and registry version 3 describe contract interfaces; they are not node release numbers.
This documentation separates the protocol, the validator implementation and optional applications. Start with the architecture, then follow the reference for the component you operate. A transfer user does not need validator secrets, the XITA website or a managed relay account.
| Document | Contents |
|---|---|
| System context and contract interactions | Whole-system diagram, contract interaction diagrams, all production Solidity roles and value flows |
| Architecture | Components, multiple assets/routes, hub topology, authorization and transaction flow |
| Security and wire format | Exact signing bytes, metadata, receipt verification, current sets, replay and trust boundaries |
| Assets and permissionless registration | Asset/route identity, Factory procedures, reciprocal bindings, supply, escrow and native claims |
| Declared Solidity API | Source-declared functions, events and errors; inherited ABI and generated getters identified separately |
| Contract and fee reference | Public calls, results, events, error handling, source fee governance and FeeVault claims |
| Independent transfer runbook | Quote, approval, wallet dispatch, original receipt, quorum, unsigned recovery, delivery and two-hop transfer |
| Validator runtime | Discovery, grouped observation, evidence witnesses, signing/P2P, durable state, cleanup and monitoring |
| CLI reference | Every Interchain subcommand, flags/defaults, output, examples and failure semantics |
| JSON-RPC reference | Every Interchain RPC, request/response fields, progress states and errors |
| Optional applications and services | Website, admin, indexer, read proxy, intake, quote, sponsor and onboarding APIs; operating boundaries |
| Deployment inventory | Recorded shared contracts and asset representations; receipts, activation heights and route verification |
| Source map and validation | Repository/module ownership, reproducible source inventory, test coverage and evidence limits |
| Release/consensus activation | Binary verification and securityAccounting; separate from Interchain deployments |
Operational entry points
- Sending or recovering a transfer: independent transfer runbook, then RPC and security reference.
- Running a validator: validator runtime, CLI, RPC and node release instructions.
- Registering another asset/router pair: assets, contract reference and deployment evidence.
- Running an independent executor: runbook and native-relayer configuration in the services reference.
- Operating XITA: services, deployment inventory and source map. Its listing policy is separate from protocol admission.
The older versioned Interchain URLs redirect readers to these current references. Dated audit evidence remains historical evidence. Source review describes implemented behavior; live transfer completion and network availability require actual chain evidence.