NanoRes StudiosAsset identity and ownership records, package references and supported settlement. Records do not establish copyright or licensing rights.
Technology · Open By Design
Shared truth without shared control.
OGAL tracks asset identity and ownership records. OPP packages assets and shares supported payments. Each application defines compatibility and access.
FoundationOGAL On Mainnet
CompositionOPP Locally Tested
AdoptionUnity First
OPP and Dashboard are implemented and tested locally and in private-host rehearsals.
Preparing for Solana mainnet deployment. SOL is needed for deployment rent and network fees.
Production settings, security and dependency review, and external-wallet release checks remain before public activation.
In Plain Language
One durable record tells applications what an asset is, who controls it, and where its current version lives.
Gameplay, moderation, discovery, pricing, permissions, presentation, and every local business rule.
The NanoRes Stack
Three layers. Clear responsibilities.
The truth layer persists. Composition evolves. Tooling makes adoption practical.
OGAL
Owner-Governed Asset LedgerRecords asset identity, ownership and manifest references. Deployed-source equivalence and independent dependency review remain unresolved.
DoesTrack recorded asset identityDoes NotRun gameplay or dictate platform policy
Inspect OGALStable references flow upward
OPP
Open Package ProtocolPackages assets and shares supported payments with eligible owners. It does not automatically transfer or reconstruct content in another runtime.
DoesDescribe verifiable compositionDoes NotTransfer asset ownership
Inspect OPPDeveloper workflows flow upward
Tooling
SDKs, Services & Creator WorkflowsThe Dashboard supports asset and release workflows in local and private-host tests. Unity executable quick-start and public runtime activation remain unqualified.
Inspect The ToolbeltArchitectural Restraint
The protocol stays small so the ecosystem can become large.
Ownership Lives Below Applications
OGAL records asset identity and update authority; each application defines its supported integration.
Check Each Integration
Supported payments and creation fees depend on the selected protocol and application configuration.
Layers Fail Safely
Application recovery and dependency behavior require qualification for each release.
Adoption Is Incremental
Studios keep their existing engines, databases, policies, and player experiences while adding shared truth where useful.
Asset Lifecycle
An integration workflow to qualify.
Applications can participate at the stage that matters to them without adopting the entire stack at once.
- 01Create
Build an asset inside a familiar editor or application.
- 02Register
Establish canonical identity and owner-governed authority.
- 03Package
Compose assets and supporting files for a specific experience.
- 04Discover
Index, list, or distribute through any compatible channel.
- 05Execute
Qualify content import and use in the target application under its own rules.
- 06Evolve
Version packages while durable asset identity persists.
Next Signal
Start with the layer your product needs.
Read the architecture, inspect the repositories, or explore the tools that turn open infrastructure into a practical workflow.