Feature and design list
Locked
This page distinguishes registered release facts, observed health, roadmap, and historical designs. Testnet 69420 is value-less and resettable. Do not use real funds.
Registered network identity
Section titled “Registered network identity”| Surface | Registered value |
|---|---|
| Registry profile | testnet-69420 |
| Chain ID | 69420 |
| RPC | https://rpc.monolythium.com |
| Genesis hash | 0xe22733f4d7e013b93f0f825667fcf852cbf7ad1ca31a42a1bfcf1ab6d79c89a3 |
| Genesis file SHA-256 | 5e5e6e0301bf742e2b7e81794ac20ca3fb5f39fdadf54230e1e0c625f9bf2cbb |
| Runtime release | v0.4.0-testnet |
| Runtime commit | da04f8f5e8391811f80e8d0511dff74311f4e811 |
| Runtime binary SHA-256 | 259c67c1c7fc8bc3f8ca22c82953ea7dc54a9e2ceaa02d0fe0879ab5192f8227 |
Verify these values against the registered profile and lyth_runtimeProvenance; do not silently follow a network whose identity differs. Identity agreement is not liveness evidence.
Observed health
Section titled “Observed health”At 2026-07-16T14:25:32Z, the public RPC was reachable and reported the registered identity, but finalized state was stale at height 74907 with latest timestamp 2026-07-08T22:39:05Z. Observed round state was not progressing and the peer-health summary was predominantly lagging/stale. Treat current health as degraded, not live.
Consensus and cryptography
Section titled “Consensus and cryptography”- The registered topology is four clusters with ten operator positions each and a 7-of-10 threshold; the registry advertises two relays.
- Account and consensus signatures use ML-DSA-65 under the registered release profile.
- Public addresses use the released typed bech32m helpers.
- The public mempool is plaintext. There is no encrypted, sealed, private-send, or threshold-decrypted transaction lane.
- There is no released SLH-DSA account, backup-key, or emergency-rotation path.
- No active proof-verifier or bridge path should be inferred from an SDK type, historical whitepaper, or reserved symbol.
This is a bounded post-quantum claim, not a statement that every cryptographic component is post-quantum.
Execution and SDK
Section titled “Execution and SDK”- The chain uses native Monolythium RPC and protocol surfaces; Ethereum-shaped compatibility calls are not the documented application contract.
- The current public TypeScript package used by these docs is exactly
@monolythium/[email protected]. - SDK exports can outlive or precede a chain feature. Serialization support is not activation evidence.
- The verified public examples are read-only chain identity calls, address conversion, deterministic local key derivation, and local ML-DSA signing/verification.
Product and protocol boundaries
Section titled “Product and protocol boundaries”| Surface | Current posture |
|---|---|
| Stele public catalog preview | Available at https://stele.monolythium.com/; no wallet required to browse; catalog data remains illustrative unless provenance says otherwise |
| Browser-wallet authentication | Challenge proof plus a persistent wallet connected-site grant; no value transfer |
| Provider listing draft Studio | Browser Wallet-authenticated private workspace at https://stele.monolythium.com/studio; durable wallet-owned create/edit/preview/delete; drafts are unpublished, outside the catalog, and have no publish, booking, signing, submission, payment, or settlement control |
| Hosted Stele MCP | Live resource at https://stele.monolythium.com/mcp; keyless OAuth surface whose authenticated tools/list response is authoritative for the runtime inventory; deployed stele_search_services and non-economic stele_create_booking_draft; authenticated Codex and Claude Code interoperability passed; production currently has 0 published services, so no successful booking-approval draft can be created; booking-draft creation fails closed unless its durable backend and release-readiness gate are healthy; only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another; the operation cannot list, read, update, delete, or publish an existing draft and cannot sign, submit, or settle a transaction |
Local lyth_mcp Stele profile |
Public v0.1.0 GitHub prerelease with exact-three connection/search/dedicated-wallet-status tools; no key access, transaction preparation, signing, submission, or broadcast authority |
| Agent wallet custody, signing, or submission | Unavailable |
| Protocol spending policy | Unavailable |
| Booking, payment, escrow, dispute, or review | Unavailable |
| In-tree bridge or Foundation-operated production route | Unavailable; external-provider interop is only under evaluation |
| SLH-DSA account or recovery path | Unavailable |
| On-chain governance | Not part of the current product boundary |
| Native perpetuals or margin | Not part of the current product boundary |
Mainnet
Section titled “Mainnet”Chain ID 69422 is reserved for mainnet. It is not a running public network and has no announced public launch date in this documentation.