Diligence
Locked
This page separates registered-release identity, point-in-time health observations, roadmap, prototype, and historical text. The development-testnet profile is value-less and wipeable. Do not use real funds.
Canonical identity and health facts
Section titled “Canonical identity and health facts”| Area | Current public fact |
|---|---|
| Network | testnet-69420, chain ID 69420 |
| RPC | https://rpc.monolythium.com |
| Genesis | 0xe22733f4d7e013b93f0f825667fcf852cbf7ad1ca31a42a1bfcf1ab6d79c89a3 |
| Runtime | v0.4.0-testnet, commit da04f8f5e8391811f80e8d0511dff74311f4e811 |
| Observed RPC health | Reachable and identity-matched, but stale/degraded at 2026-07-16T14:25:32Z; latest finalized timestamp 2026-07-08T22:39:05Z |
| Topology | Four clusters, ten operator positions per cluster, 7-of-10 threshold, two relays |
| Mainnet | Chain ID 69422 reserved; no running network, genesis, or launch date announced |
| Mempool | Plaintext; no encrypted, sealed, or private-send lane |
| Interop | No in-tree bridge and no Foundation-operated production route; external-provider evaluation only |
| Agent economics | No supported custody, spending-policy, signing, submission, booking, payment, escrow, dispute, or review path |
| Emergency signing | No released SLH-DSA account or rotation path |
Machine-readable versions live at /facts.json, /llms.txt, and /llms-full.txt.
What the docs verify
Section titled “What the docs verify”- Exact registered chain-registry and runtime identity pins.
- Safe read-only native RPC probes for finalized-state freshness, round progression, sync lag, peer health, and runtime provenance.
- TypeScript examples compiled against exactly
@monolythium/[email protected]. - Public-copy, internal-link, local-document leak, and container smoke gates.
These checks are documentation evidence, not a substitute for a security audit, source review, legal review, exchange certification, or production-readiness assessment.
Diligence still required
Section titled “Diligence still required”Before mainnet, custody, listing, or material-value use, independently obtain and review:
- the canonical release source and reproducible build evidence;
- external security review scope and findings;
- workload-specific benchmark harnesses and raw samples;
- adversarial consensus, networking, signing, and recovery simulations;
- legal treatment, token terms, vesting, and entity disclosures;
- wallet, HSM, indexer, and operational failure drills.
Do not substitute the historical whitepaper body, an SDK export, a prototype tool name, or a local source checkout for current activation evidence.