XGR.NETWORK / DOCUMENTATION

Deployment Reference

Recorded deployments and route inventory

Documentation index. Snapshot of public xgr-interchain commit 9518472c04432c57a5939a3688e90be332180636. These are recorded deployment identities, not a fresh live-chain availability claim. Verify current code, bindings, set, fees and reciprocal routes before signing.

1. Supported compiled chain policy

Network Chain/domain Node name Finality Source Registry activation (RPC receipt height)
XGRChain 1643 xgr Locally committed IBFT 12053797
Base 8453 base Checked safe 53026521
Arbitrum 42161 arbitrum Checked safe 517836903

The policies are pinned in node interchain/config.go. Polygon prospect definitions do not establish active node support. Arbitrum activation uses RPC L2 receipt height, not Solidity L1-origin block.number.

2. Shared infrastructure

xgrchain

Component Address Receipt block / evidence
validatorRegistry 0x9b6b92ef1745611f402341965f7fc649cbe0da8c 12053438
ism 0x1bd47599e8e7436948e596a0e055f2c7ec02cc30 12053472
transportBundle 0xeeb50ae5ade22969a5ec3b9da0878ab57211d606 12053674
mailbox 0x37a8c5f601adf3cbbe70ea66df2f964321c0e02a 12053674
dispatchHook 0x0a6e9d3e672b281f3351aaa77bfcfbfb5ed019fd 12053674
requiredHook 0x0a6e9d3e672b281f3351aaa77bfcfbfb5ed019fd 12053674
nativeRouterDeployer 0x62a9fb2f0df77aa0297dbc567079813ccf7c4ea1 12053694
syntheticRouterDeployer 0x511ebf6ce53781c279e88ecf7681f0ea59cc4cad 12053719
collateralRouterDeployer 0x6e886a9c17bea13190a2dc26a4c61e1a258d608e 12053745
factory 0x0e657364c1a82ecb4c62d16e8c4560d95610fe56 12053771
sourceRegistry 0xea887a7f2f519f291732aaadf578baf3ff374df6 12053797
executionGateway 0xedd68419d215c8e4fdc9fc5f0d63f824747bc176 12053833

The ExecutionGateway is optional commercial infrastructure. dispatchHook and requiredHook identify the same zero-fee ProtocolFee hook in the Direct transport; no MerkleTreeHook is required.

base

Component Address Receipt block / evidence
blsVerifier 0x0e657364c1a82ecb4c62d16e8c4560d95610fe56 53026233
validatorRegistry 0x3dc4cc1912792749d320789a67c2c14b7ee4ee33 53026281
ism 0xedd68419d215c8e4fdc9fc5f0d63f824747bc176 53026311
transportBundle 0x7bc756993559a26bac564fdf4abc5a5dabbf4849 53026338
mailbox 0xa77c34aa23d190c71a1d0b9d4ac469b0fb01b363 53026338
dispatchHook 0xe83d5ad3014c4d31584b87fd892f51969c385172 53026338
requiredHook 0xe83d5ad3014c4d31584b87fd892f51969c385172 53026338
nativeRouterDeployer 0x3617775089b94591a60316f63b200a5963b442ea 53026366
syntheticRouterDeployer 0x2dbdd19c9cd267ffe6830bb61f7988c140a7a75a 53026396
collateralRouterDeployer 0x719e08364b4a1f04f6364dd81df0ca6456676c9c 53026443
factory 0x01ddcbbda44b2a7d72b6c5801b88cd36319cec94 53026472
sourceRegistry 0xf243093350b1b4ef8a9e3b0c13be3495297461b0 53026521
executionGateway 0x8910679c883b00e42f9c52fd6664571cd64833f4 53026984

The ExecutionGateway is optional commercial infrastructure. dispatchHook and requiredHook identify the same zero-fee ProtocolFee hook in the Direct transport; no MerkleTreeHook is required.

arbitrum

Component Address Receipt block / evidence
blsVerifier 0x504f241c1c177d811021f6412a0c2474d410ec99 517835200
validatorRegistry 0x1a6610cc7dd0d0f42e22c3608e025d891065814c 517835411
ism 0xcf7e1a877d919c1c8dba48b42a832bdb1042101f 517835602
transportBundle 0x402d1eabd5b11e517688231a641d027376c6ed10 517835797
mailbox 0xd4c7665f3c984bfbbeca9e67e593a5bab3881fe3 517835797
dispatchHook 0xb58225ac533243b03bde6d38720310c24b1dd37a 517835797
requiredHook 0xb58225ac533243b03bde6d38720310c24b1dd37a 517835797
nativeRouterDeployer 0x2c7a18747fda9b8a3d98e8603ddab24a5248dcce 517836007
syntheticRouterDeployer 0x495eeac5e0ae1eba54fb30de31483929d847a5db 517836210
collateralRouterDeployer 0xa91b1e7179a50f0d798d284676d3ba9ff705fe82 517836423
factory 0xa27eadcaf70631e29009019d390e48410a830e64 517836718
sourceRegistry 0x51e3b684ed61fc88083497e475825a6cecaf21f5 517836903
executionGateway 0x64d9da5d8365069d79ea82344c4ce488bb6a72e7 517837223

The ExecutionGateway is optional commercial infrastructure. dispatchHook and requiredHook identify the same zero-fee ProtocolFee hook in the Direct transport; no MerkleTreeHook is required.

3. Asset representations

XGR

Canonical Asset ID: 0xa7585b8fbd074c1a7fa6df8b8e2e5ce73395ccbb64bf99b631c5da8ff2ac44e0.

Chain Role Address Evidence
arbitrum syntheticRouter 0x5a31a62bb6441b499718df8fb767b6286267c74b Receipt
base syntheticRouter 0xd7443427ca21ae0907d2aa55446470307c990092 Receipt
xgrchain nativeRouter 0x7d9354baab0bf308d17e90ee3895609680e355ed Receipt

ARB

Canonical Asset ID: 0xb913a68b77dc8b9df32e6e7d6158dfd4abb3b2c57fd127321c2727a17c207528.

Chain Role Address Evidence
arbitrum collateralRouter 0x76f5d761ae41116ba5fa2ecb358e5fad15e0d992 Receipt
base syntheticRouter 0xc78929dc2d877ced57034319c3f162407cd605b9 Receipt
xgrchain syntheticRouter 0x96940e83d3096eb868541adf29aa8da44a783e85 Receipt

4. Recorded directed routes

Each row is a separate source operation. Reverse direction has its own route ID/Gateway/vault. This snapshot contains four directions per recorded asset, not one global route.

Asset / direction Full route ID Gateway FeeVault
XGR: xgrchain → arbitrum 0x1b75cf1eb34fa922258e4d4f1fc8d2d5e181cfde74c0bc307498147dcd56e7a2 0xd79fca769f7ecd45593411abb905cb93dd0230f7 0x17eb63cc1af0c1a206781e3b4ad7faa1e3c3fbc7
XGR: xgrchain → base 0x34147bb992614ff3b01fb4be16fff55d9be7f7973f74d567c4b9a7a53e4f92fb 0x44a479f722cb146ccb1dffa46e297879ab76268d 0xc2fd91639964d91e069225f2a08e70f1c0228eed
XGR: arbitrum → xgrchain 0x6b8b2d38524393eea76cda62f54300d169d4834bd8e8eb18644f2e1f7f2c105a 0x88da20e5ae14c2ec48c3b3069f0d88a33f5849db 0x834291e15b9db12b599bfc201ad5516490776d7f
XGR: base → xgrchain 0x7c10670b7cc28d27d88805d8eef081ef2ec50f5a7e69ca50864c057b16d94e0a 0xeeb21da92aaeca479009346c8f27f2fd4d3571f3 0xdf4289e8037c736955127af53371e1002677b35f
ARB: xgrchain → base 0x32fbba0d007fcdae2e5cef59701691dd8b00e40144c5ffa3199c393b34176312 0x6084f3136d6d9563f19acd41a8afb3020cd2859f 0x1c5ba6dcc7ed4caa8748462789b6eb5df494e1cd
ARB: arbitrum → xgrchain 0x49f483f6b1014e24a60955d33ce662104ca70b2cf142527f969b72517b578f40 0xa979d979d1f9aab0e246b307b8192620310a9d18 0x21c248434512378906cc19c70e6401d65247b048
ARB: xgrchain → arbitrum 0x4c5c82424f051f210ee1383a60fb1d2d84c4e12187fb285485664030554abeba 0x731dd9a0417810013b2958555c79038dfb93aa90 0xc60375387eb571e0fd58e518b89619eaec4a8da3
ARB: base → xgrchain 0xacd9cc536b3f809a8d40c34a554557d9341b8db032ad087ec3c7ce0ad6f01e83 0xa2785616b468a92829c48806fbd2cd22be37ffb4 0xc1349b7c7bef9e49e314716d1e28f2b5a4aced04

5. Verification procedure

  1. Verify RPC eth_chainId, canonical deployment receipt status/hash/block and expected contract address/Factory provenance. Read runtime bytecode and compare Keccak-256 with the reviewed receipt and artifact, accounting for the verified compiler/constructor build.
  2. Match shared transport: Mailbox local domain, default/required hook, default ISM and ISM validator Registry. Check compiled node Registry/source Registry identities.
  3. Match Factory/source Registry and the route tuple, asset metadata, router token and Creator provenance. Recompute Asset/Route IDs from exact ABI encoding.
  4. Match Gateway immutable Registry/route/domain/router/token and FeeVault Gateway/route/domain/governance registry. The cumulative Gateway fee counter is not a balance proof.
  5. Verify destination reciprocal route and verifyInboundRoute, current set/key format and available escrow; quote the exact recipient/amount before use.
  6. After a transfer retain both canonical source identity and confirmed destination execution evidence. A deployment receipt does not prove transfer E2E, current quorum, production service rollout or sufficient native gas.

6. Updating records

Public receipt files are append-only evidence. Do not replace a historical receipt to make it look current. Record new identities through the verified deployment/receipt workflow, regenerate catalog and documentation from the same reviewed revision, and re-evaluate compiled policy when shared network infrastructure changes. Do not publish secrets or applicant contact details.

This generated inventory checked 60 component/representation/route references against their existing receipt address, chain and recorded runtime hash. This is internal record consistency, not a new RPC bytecode verification.