Development Status
This page exists to answer a simple diligence question:
What is live today, what is in progress, and where is the real execution risk?
The goal is clarity, not optimism.
High-Level Summary
The system is intentionally built bottom-up, with the most critical layers hardened first.
Current status:
- OGAL (Protocol Layer) – Live on Solana mainnet and backing a real production pipeline
- Solana Toolbelt for Unity – Shipping, developer-facing infrastructure with real runtime value
- OPP (Open Package Protocol) – Specification-complete, tooling underway, on-chain execution in progress
This is the correct maturity order for an infrastructure company.
OGAL — Owner-Governed Asset Ledger
Status: Production-ready
OGAL is deployed on Solana mainnet and is actively used in a live application pipeline.
What Is Live
- Canonical asset identity via ObjectManifest PDAs
- Ownership and update authority enforced through SPL Token ownership
- Manifest updates gated by NFT ownership verification
- Metaplex metadata URI updates via CPI
- Namespace governance, pause controls, and authority rotation
- Deterministic PDA derivation and provenance tracking
What This De-Risks
- Asset truth and provenance
- Ownership enforcement
- Mutability rules
- Upgrade discipline and operational constraints
OGAL is no longer theoretical. It is already doing its job.
Solana Toolbelt for Unity
Status: Shipping and usable
The Toolbelt is a Unity-first SDK that makes OGAL practical to integrate without requiring teams to become blockchain specialists.
What Is Live
- Centralized runtime configuration and RPC endpoint orchestration
- Wallet lifecycle and session management
- OGAL mint, update, and admin helpers
- Metadata upload and retrieval helpers
- Bundlr / Arweave automation for content persistence
- Access control and NFT-gated feature helpers
- UI bridge contracts for clean UX integration
What This De-Risks
- Developer onboarding friction
- Integration complexity
- Runtime reliability in real applications
- Unity-specific consumption patterns
The Toolbelt is not scaffolding. It provides real runtime value today.
OPP — Open Package Protocol
Status: Spec-complete, execution in progress
OPP is the final layer in the stack and is intentionally being hardened last.
What Is Complete
- Packaging and composition schema
- Deterministic build and hashing rules
- Software Bill of Materials (SBOM) design
- Asset inclusion and ownership declaration
- Revenue intent declaration (not enforcement)
- Installer lifecycle design (validation, activation, rollback)
What Is In Progress
- On-chain OPP program implementation
- End-to-end integration with OGAL assets
- Tooling polish and UX
- Indexing and discovery helpers
Why This Is Acceptable Risk
OPP does not affect:
- Asset truth
- Ownership enforcement
- Developer adoption of OGAL
- Creator workflows
It only affects optional value capture and execution.
That is where execution risk should live.
Token Toss — Reference Implementation
Status: Live
Token Toss is a first-party reference implementation that proves the stack end-to-end.
It demonstrates:
- Explicit, user-approved minting flows
- Permanent content storage via Irys → Arweave
- OGAL ownership enforcement
- Real asset updates and reuse
- Live gameplay with on-chain assets
Token Toss is proof, not the business.
No platform needs to adopt Token Toss to adopt OGAL.
What Is Not Yet De-Risked (Intentionally)
The following remain execution work:
- OPP on-chain execution
- Expanded marketplace integrations
- Advanced creator tooling
- Ecosystem-scale adoption
These are the correct risks to take after the core protocol is live.
Risk Distribution Summary
De-Risked
- Canonical asset truth
- Ownership enforcement
- Unity consumption
- Mainnet operation
- Developer workflow viability
Execution Risk (Acceptable)
- OPP execution layer
- Tooling polish
- Marketplace and discovery layers
Not Risky
- Protocol design
- Layer separation
- Economic philosophy
- Adoption strategy
Final Framing
The core ownership layer is live.
The adoption rails are usable.
Value capture is the last layer to harden.
That is exactly where an Open UGC infrastructure project should be at this stage.