X Layer testnet
Current Grantline contract evidence on X Layer testnet, including network settings and deployment-specific limitations.
The current contracts MVP is deployed and exercised on X Layer testnet. This page records the network and deployment-specific evidence; shared authorisation and execution mechanics belong in the enforcement and execution pages.
Network settings
| Setting | Value |
|---|---|
| Network | X Layer testnet |
| Chain ID | 1952 |
| Gas token | OKB |
| RPC | https://testrpc.xlayer.tech/terigon |
| Explorer | OKX X Layer testnet explorer |
Deployment status
Its addresses, dependency wiring, runtime hashes, Vault authority, and evaluator settings are recorded in the deployment manifest and shown in Contracts and deployments.
The deployment is verified against the expected chain and runtime hashes before the integration flow runs. The manifest is authoritative for this environment, so the network page does not duplicate its addresses and a deployment update has one public reference point.
Submission status
The current testnet integration uses the root or delegated agent as the transaction submitter, and that account pays its own gas. This describes the integration that was exercised on this network, not a requirement of the authority model. The evaluator, nonce, escalation, executor, and Vault checks still apply regardless of who submits the transaction.
Sponsored submission remains deferred. A future relayer will be documented on the relevant integration page once it exists and has been tested.
Evidence covered
The X Layer testnet integration exercised:
- a successful root
ALLOWtransfer; - a hard-denied over-limit plan and a consumed-nonce replay;
- escalation submission, controller approval, and execution;
- delegated authority through a child and a grandchild Mandate;
- inherited Preflight denial followed by controller-approved execution;
- ancestor tightening and lineage revocation;
- failed execution receipts that moved no funds;
- Vault and Mandate pausing and unpausing;
- validity window enforcement (
validAfterand expiredvalidUntil); - controller nonce cancellation;
- minimum native amount enforcement;
- a hook recipient receiving native transfer; and
- Vault upgrade preserving pause state.
This is evidence of the current contract flow on this network. Use Inspecting evidence for the reusable receipt, event, and explorer workflow.
Deployment-specific limitations
The current deployment has no Chainlink USD feed or SWAP adapter configured. Native-USD rules, Preflight floors, and SWAP actions are not available on this deployment until a fresh deployment with a configured feed and adapter is performed.
Offchain indexing, sponsored submission, production USD resolution, and assembled Decision Receipts remain deferred. Those are product or integration capabilities, not properties of X Layer testnet itself.
See Transaction lifecycle for shared transaction behaviour and Enforcement boundary for the contract path that applies on this network.
Last updated on