Solana & mainnet readiness

Where we are

The current beta writes records to Solana Devnet. Devnet is a public test network: it lets us validate the real write and verification path with invited users, but it can be reset, so beta records are not production-permanent.

Why Devnet first

Devnet lets us prove the end-to-end product — browser hashing, the backend write path, public records, and verification — without asking early users to depend on production permanence before the workflows are ready. We state this plainly rather than overclaiming.

Readiness gates

These are the areas we want in good shape before a production mainnet deployment.

• Product quality. Core create and verify flows are clear, consistent, and stable for everyday use.
• Quality assurance. Workflows are tested across devices, inputs, and edge cases before wider release.
• Security & readiness review. A security and operational review of the write path and key handling.
• Beta validation. Enough real beta usage and feedback to trust the workflows and copy.
• Funding / grant signal. Resourcing to operate a production registry responsibly over time.
• RPC & cost planning. Reliable mainnet RPC access and a sustainable per-write cost model.
• Monitoring. Monitoring and alerting for the write path and read models in production.
• Abuse & rate-limit review. Controls against abuse, spam, and runaway cost before opening writes widely.
• Operational checklist. Runbooks, backups of product data, and incident handling in place.
• Deployment planning. A staged plan to move from Devnet to mainnet without breaking existing references.

No fixed date

There is no fixed mainnet date. The move depends on the gates above being met responsibly, not on a deadline. The beta status page tracks current focus areas.