Beta Status & Roadmap
Controlled betaElectronic Registry is currently in controlled beta. We are testing the core registry workflows with invited users before wider public release.
The current beta focuses on creating public registry records for exact files, adding Public References, and verifying public records without sign-in.
Available in closed beta
These workflows are available for controlled beta testing and reviewer evaluation. They are still being refined through QA and feedback.
Create a public File Record
Verify an exact file/hash
View a public record / verification result
Add a Public Reference
View public record history/context
Use a private dashboard for organization
Read documentation and trust-limit guidance
Submit feedback during controlled beta
Current focus
Current work is focused on product quality, trust clarity, reliability, and readiness for pilots and grant review.
Beta tester feedback
QA and reliability improvements
Public record page clarity
Verification result clarity
Trust-limit wording
Documentation improvements
Grant and pilot readiness
Mainnet readiness planning
Future direction
These areas describe possible product direction. They are not commitments, launch promises, or fixed-date milestones.
Broader public beta expansion
Organization workflows
Developer/API documentation
Public record export/report packages
Additional registry layers
B2B/pilot workflows
Cross-chain anchoring research, including possible Ethereum anchoring feasibility
Important limits
Electronic Registry creates public records and verifiable record history. Verification checks whether an exact file/hash matches a public Electronic Registry record.
What this can show
- A matching public record exists for this exact file/hash.
- The record was created at the displayed time.
- The record can be checked later by someone else.
- Public References may be attached as later entries.
- Files stay private unless the user chooses to share them.
What this does not prove
It does not decide whether content is true, owned, authored by someone, original, legal, compliant, certified, copyright-protected, platform-approved, officially approved, legally valid, or accepted by a court.
- Truth
- Ownership or authorship
- Originality
- Legality or legal validity
- Compliance
- Certification or official approval
- Copyright protection
- AI status
- Platform approval
- Court acceptance
Public release
Public release has no fixed date. Wider release depends on product quality, QA, trust clarity, beta validation, infrastructure readiness, and responsible deployment planning.