ᚱoko Network has been quiet… building. Time itself required recalibration — now the signals return. Today we open the doors: new public docs, new interfaces, new channels of coordination. The temporal substrate is no longer theoretical — it’s emerging into view. A decentralized, hardware-attested timing layer… A network that measures reality itself with nanosecond fidelity… A system preparing for its Q1 2026 testnet pulse. Full announcement ↓ docs.roko.network/pages/sign… If you want to build with us — or test the clocks — 📩 [email protected] ᚱ onwards.

ROKO NETWORK github this month we have been busy and focused ------ Sep 8–10: testing push on the main node code (roko_network). About 120 commits in three days. Most of it tests the consensus rules against faults and recovery. It also covers: - Keeping release packages that passed testing and promoting them without rebuilding. - Security scans required before images are published. - Checks on the published ARM64 images. - Fixes to time sync between peers, a participation policy for the early testnet, and long relay tests. The public docs, node docs and marketing site were updated to match the "September 10 recovery" of the testnet. Sep 10–14: block explorer (the Blockscout fork and its frontend). - Transaction counts load without slow full scans, and the homepage now shows user totals. - The pwROKO token page and wallet welcome screen were redesigned. - New guided lookups for developers (RPC and storage) and a guided address page. Sep 8–17: validator sign-up tools (roko-edge-tools v1.4.0 and v1.4.1). - Validators can now set up a wallet locally on the node. - Added a check that the RPC endpoint is safe, and safe reuse of existing session keys. - Added a watcher that tracks validator recovery. - Wallet setup guides went out in public-docs and roko-nodes. Sep 15–17: runtime features (roko_network). - A fee policy controlled by governance, closing issues #88 and #89 from July. - pwROKO now accepts standard Solidity function selectors (#92). - A fix for validator heartbeats. Tester filip-git-git had reported an elected validator stuck disabled for 90+ sessions. - Three old onboarding tickets from May (#48, #49, #52) were closed. Sep 24: "preserve outstanding work for host migration review." jmagly made the same commit in 7 repos. It looks like a snapshot of unsaved work before moving to a new machine. Sep 28–29: fixes for outside bug reports. - ataraxismaximus found that the published list of authority peers had expired on Sep 13, which broke new validator installs. A second report was a false clock-check failure when the installer runs without root. - Both were fixed the same day and shipped as v1.4.3–1.4.5. roko-ops gained a monitor that re-publishes the peer list before it expires. Sep 29 → Oct 7: testnet halt. - filip-git-git reported the testnet halted at block #1536941 (edge-tools #40). - jmagly found the cause (#100): a consensus rule required transactions that could no longer be included, which deadlocked block production. The fixes (PRs #102 and #103) were merged Oct 1. - More fixes followed Oct 7 (PR #116). - edge-tools #40 is still open. Two related issues are also open: #105, where nodes ban each other and split the network, and #104, moving builds to Ubuntu 26.04. - GitHub doesn't show whether the testnet is producing blocks again. Oct 5–7: your work. - roko-build: the XDC bridge, 21 commits, PR #2 open. - roko-pq v0.2: 7 commits. - Issues #106–#112 on roko_network: a BLAKE2F precompile, k-of-n receipts, the BEEFY leaf, receipts over RPC, time quality, missing mixHash, and the broken fallback RPC plus empty faucet. - PRs #113 and #114, which implement part of those. - jmagly closed one consensus issue (#115) the same week. None of your 10 issues or 3 PRs has been reviewed or merged yet.

In 1994 Peter Shor wrote down the algorithm that ends the world we built. Not with a bang — with a proof. Every signature guarding every wallet, every contract, every validator on every chain rests on one bet: that deriving a private key from a public one is computationally impossible. Shor's algorithm turns that impossibility into arithmetic. secp256k1, the curve under Bitcoin and Ethereum and nearly everything you touch, is not "hard" for a quantum machine — it's polynomial. And here is the cascade nobody wants to say out loud: the day a cryptographically-relevant quantum computer becomes credible, every public key ever exposed on-chain becomes a private key waiting to be recovered, every ECDSA signature ever made becomes forgeable, and the entire signed past of the digital world converts from proof into rumor in a single stroke. This is not a data breach. It is the retroactive collapse of history itself — and you cannot patch it, because the wound is in the record, not the key. The only structure that walks out of that fire is one Shor cannot touch: a hash-chained, witnessed ledger of what happened and when, anchored in verified time by a network no single party controls. That is exactly what ROKO.Network is building — quantum-durable by construction today, migrating to lattice-based post-quantum signatures by design — the flight recorder that survives the day the signatures die. We are not selling protection from the next hack. We are building the one record that remains provable after Q-day turns everyone else's past into a claim. Whoever controls the clock controls reality. We are making sure that after the fire, the clock still tells the truth. (roko.network)

Do you have ROKO?

Payment links should be inspectable before they become wallet prompts. ROKO Payments is live: payments.roko.network Review first. Connect only when ready. Sign only if the wallet preview matches.

Try the testnet flow: 1. Open burn.roko.network 2. Connect only when ready 3. Classify the mechanism 4. Review the simulation 5. Burn only if you understand the irreversible result

ROKO Burn keeps those categories separate, simulates reviewed actions, and waits for canonical-block checks before finalized totals move.

Those are not interchangeable. A sink transfer can retire access without decreasing supply. A wrapper redemption can destroy the wrapper while releasing backing. A supply burn needs supply evidence.

at burn.roko.network. Before signing, the useful question is not "can this be burned?" It is: what kind of state change is this? Native supply burn. Token supply burn. Wrapper redemption. Claim destruction. Sink retirement.