Non-Unity Developers

If you are integrating OGAL without Unity, this page points you to the core repo and concrete starting steps.

Non-Unity track: Non-Unity Quickstart • OGAL Integration • Token Toss proof

Who this is for

• Unreal, Godot, or web client teams
• Backend services or middleware
• Solana/Anchor program developers
• Indexers and data pipelines

Core repo

Start with the OGAL program source:

• https://github.com/NanoRes/Owner-Governed-Asset-Ledger

Key entry points

When you clone the repo, go straight to:

• programs/owner_governed_asset_ledger/src/lib.rs (Anchor program entry)
• Root README.md for build/run expectations
• Any IDL output directory (often idl/ or target/idl/) once you confirm it exists

Minimal getting started sequence

1. Clone the repo and open the Anchor program at programs/owner_governed_asset_ledger/src/lib.rs.
2. Review the program ID and instructions to understand the canonical entrypoints and account ownership rules.
3. Inspect account layouts to model them in your client, indexer, or backend storage.
4. Follow the Non-Unity Quickstart to validate an OGAL asset account and fetch its metadata: Non-Unity Quickstart.
5. Use the OGAL Integration doc to align protocol expectations with your runtime and validation logic: OGAL Integration.

If you need Unity-specific tooling instead, start with the Unity track: Unity Developers.

---

Integration Ladder

Adoption typically climbs in small, reversible steps:

1. Read-only → verify ownership and provenance
2. Mint-aware → allow minting or registration of assets
3. Reuse-enabled → load OGAL assets created elsewhere
4. Optional monetization → use OPP only when it adds value

This matches the Platforms adoption phases so teams can align terminology across product and engineering.