Entry conditions
Current gated dev testnet for protocol validation, reproducibility, and interface testing. Access is controlled and resettable; no production readiness is implied. Actions and events are recorded on-chain as tamper-evident state and used to compare views across independent indexers; outputs can lag or reset and are not durable records. Operational flows are stablecoin-native by design. Test assets may be used where provided; no fiat rails, custody, or settlement guarantees are provided.
XML-only surface. Not linked from navigation. Internal access only.
Dev testnet GUI access is provided after approval. Local sandbox kits are provided to approved operators via private repo invite or bundle link.
Login access
Log in with issued credentials to access gated testnet endpoints and bundles.
Login is restricted. Credentials are issued after review.
Request access
Share the details needed to review testnet access and provision credentials.
- Your role and organization.
- Access type: dev testnet GUI testing or local sandbox kit.
- Testing scope (operator, indexer, builder, observer).
- Jurisdiction and contact email for credentials.
- If requesting a sandbox kit, preferred delivery method (private repo invite or bundle link).
- Any compliance or operational context needed for access.
No public faucet or onboarding flow is provided.
Access is granted for validation and reproducibility only. Requests are reviewed case-by-case; approval is not guaranteed and access can be reset or revoked without notice.
Environment posture
Testnet is split into local and shared environments. Both environments are resettable and subject to change.
Local and dev only
Environments are limited to local sandbox and dev testnet; no mainnet posture is implied.
Resettable state
State resets and parameter shifts are normal during early validation cycles.
No guarantees
No uptime, availability, or support guarantees are provided.
Environment map
| Environment | Purpose | Access notes |
|---|---|---|
| Local sandbox | Local testing environment. | Standalone, non-shared state; kit provided after approval. |
| Dev testnet | Shared testing environment. | Controlled access; credentials issued after review. |
Access surface list
Access surfaces are provided when approved for testing. All surfaces are resettable and may change without notice.
| Surface | Purpose | Status | Access notes |
|---|---|---|---|
| Config bundle (if provided) | Genesis, peers, and base settings for testnet. | Gated | Changes may occur between resets. |
| Reference interface (GUI) (if provided) | Test the reference UI against dev testnet. | Gated | Credentials issued after review; testnet-scoped. |
| JSON-RPC endpoint (if provided) | Operator and integration testing. | Gated | Access controlled; resettable environment. |
| Local sandbox kit (if provided) | Single-node sandbox for isolated local testing. | Gated | Delivered via private repo invite or bundle link after approval. |
| Indexer API (if provided) | Reproducibility checks and reporting tests. | Gated | Data may reset; formats may change. |
| Explorer view (if provided) | Read-only visibility during testing. | Read-only | Non-public; may change without notice. |
| Faucet (if provided) | Test token distribution for development. | Gated | Internal access; rate limits may apply. |
Boundary constraints
In scope
- Testnet mechanics, validation cycles, and resettable environments.
- Controlled access for protocol validation, reproducibility, and interface testing.
- Non-authoritative reference surfaces for testnet-only use.
Out of scope
- Mainnet access or production readiness claims.
- Public onboarding, availability, or access guarantees.
- Support or uptime commitments.
- Custody, compliance, or legal guarantees.