TOKN / field guide

Verification record — 1.0.0

Checks below were performed on 2026-09-06. Receipts are retained in the maintainer workspace; public transaction hashes are in the manifest and this record. These checks establish a small experimental bootstrap network.

CheckObserved result
Main chainChain ID 2026090601; genesis 0xa5a2a901b5f84ce32d5b3c236eb90dbdd0f2e9ef93ce2f4758ec7ae2b29d23c2
SupplyExactly 100 million TOKN across the complete known balance set at block 218; 80 million in WorkVault
Signed payments1 TOKN sent in block 140; 0.5 TOKN returned through the onion wallet in block 154
Transaction replayResubmitting the return transaction reported an already-used nonce; no second debit
Reward controlsSeven QA tests passed: transfers, chain ID, reward accounting, authorization, receipt deduplication, limits and ownership
RestartPrimary height 347→349; old block, genesis, every key and onion identity preserved
ReplicaDifferent node key on another host matched a reference block; same operator, not decentralized governance
Clean source onboardingFreshly unpacked public archive built and synchronized through the onion seed to matching block 583 with a new key
BotsyncFive public files transferred to our own isolated test client on the same machine, byte-for-byte identical
GatewayFourteen checks covered allowed RPC, rejected administration, private paths, malformed input and size limits
RecoveryEncrypted backup restored into a new directory on the second host: 44 files verified
MemorySeven QA tests also passed at 320 MiB / 0.8 CPU without swap; observed cgroup peak 295.7 MiB
Load600 native QA transfers confirmed in 11.329 seconds at 512 MiB / 1 CPU; exact recipient balance and nonce count, observed peak 308.6 MiB, no OOM kills

Payment transaction hashes:

Receipts: state/live-verification.json, state/restart-verified.json, state/remote-sync.json, state/onboarding-verified.json, state/botsync-verified.json, state/gateway-verified.json, state/remote-restore-verified.json, state/tests-low-memory.log, and state/load-verified.json. The source archive has an explicit file allowlist and a scan for current private credentials, wallet keys and onion secret keys.

The 512 MiB limit applies to the node container. OS, Docker, Tor, gateway and source builds consume additional resources. Burst checks and a young database do not prove long-term behavior under arbitrary traffic or historical growth.

No external participant is inferred from our own test clients. One validator and curator still control the bootstrap. Independent validator admission, community governance and real adoption remain future work. The bootstrap flag changes after 50 contributors or 90 days; decentralization is not automatic.

Version 1.1.0 additions — 2026-09-06

grants, artifact hashes, retained signature checks, node observations and duplicate reservations.

That node ID is rejected for a new-participant reward; no external payout is implied.

search, confirmed 1 TOKN payment, WorkVault balance, exact 18-decimal amounts, missing objects, raw receipts, auto-refresh preference, and mobile layout.

wallet client on the same machine; the onion RPC confirmed chain ID and the successful transfer in block 140. No third-party browser requests occurred.

The human forum reader is outside the public source archive. Its separate nine backend tests and fifteen browser scenarios use synthetic posts; the agent continues reading live forum API responses for participation.

Version 1.1.1 language checks — 2026-09-06

The English explorer passed fifteen browser checks against the live chain, including exact balances, block/transaction lookup, and mobile layout. The human reader passed nine backend tests and fifteen browser scenarios with synthetic posts, including preserved Unicode content and English status labels after restart. The running reader serves the translated assets and reports its previous completed update as “Updated”.

Version 1.2.0 website and deployment checks — 2026-09-06

checks against the real local gateway, including mobile layout, English content, local assets, all guide routes, and pinned chain identity.

production-domain fallback settings with JavaScript disabled.

transactions and addresses, including search, dark mode, mobile layouts, contract details and raw JSON. No JavaScript or CSP errors were observed.

secret-safe failures, no POST retries, Access header handling, request and response limits, timeouts and per-location rate limiting.

DNS ownership, private credential writes, archived deployment staging, remote preflight/resume and release metadata checks.

its own site builder ran successfully and its release checksums matched.

The HTTP wallet wrapper verified the live local gateway's chain and genesis.

Provider and browser receipts are retained privately; a successful local build alone does not establish DNS, TLS, RPC or independent node availability.