Skip to main content

Unity Developers: Start Here

If you're shipping a Unity game or tool and want Open UGC support without rewriting your stack, start here. The Solana Toolbelt for Unity exists to make OGAL practical in real production projects.

This section is designed to give you two things fast:

  1. A clean mental model for how Open UGC & Beyond is structured.
  2. A quick path to a working Unity integration you can validate in minutes.

You do not need to redesign your game, your backend, or your business model to start. You can integrate OGAL read and verify flows without touching OPP or any marketplace, letting you respect asset portability across games without changing how you monetize or operate. If you want to learn more about using OGAL, check out the OGAL Guide.

If you want quick definitions of core terms, check the Glossary.

Start fast: Toolbelt Overview • Unity Quickstart • Token Toss proof

What this page gives you​

  • A Unity-first entry point into OGAL and OPP concepts.
  • Clear next steps for validating ownership, access, and runtime loading.
  • Links to the exact guides you need to move from proof to production.

The Unity-first path​

OGAL integration is designed to feel like standard Unity workflow:

  1. Install the Solana Toolbelt (UPM) in your Unity project.
  2. Read OGAL asset state at runtime (no wallet required).
  3. Connect a wallet only if you are verifying ownership or minting/updating assets.
  4. Validate ownership and access rules before loading content.
  5. Stream or hydrate assets as part of your existing loading pipeline.

Reading OGAL assets does not require a wallet; wallets are only needed for creation, minting, or updates (gas fees).

You do not need to change your UX, economy, or content pipeline to validate the core loop.

What this is​

Open UGC & Beyond is layered on purpose.

OGAL: Ownership Truth Layer​

OGAL is an on-chain protocol that defines:

  • Canonical asset identity
  • Ownership and provenance
  • Mutability and permission rules
  • Transfer and custody logic
  • Update control enforced by program rules

Tooling: Adoption Layer​

The Solana Toolbelt for Unity exists so you can integrate OGAL without becoming a blockchain engineer.

It provides:

  • Wallet and session orchestration
  • RPC abstraction and account fetching
  • Transaction helpers and signing flow scaffolding
  • Asset verification and reconstruction helpers

Tooling reduces friction, not control.

OPP: Packaging and Composition Layer​

OPP is an optional protocol that packages OGAL assets with other files to form portable, reusable bundles.

OPP supports bundles that can include:

  • OGAL assets
  • Metadata
  • Code
  • Images
  • 3D models
  • Animations
  • Audio
  • Config files

OPP includes a machine-readable SBOM (Software Bill of Materials) that makes asset inclusion and intent auditable.

What this is not​

It does not:

  • Run your marketplace
  • Enforce monetization or payouts
  • Control your UX
  • Take custody of user funds
  • Move money for you

OGAL defines what is true. Your platform or application enforces monetization.

The mental model​

This is the simplest model that stays true:

  • OGAL governs truth
  • OPP governs composition
  • Tooling governs friction
  • Markets govern discovery
  • Applications govern experience and monetization

If you only remember one sentence, remember this:

OGAL defines ownership, OPP defines packaging, and platforms define how value is captured.

How most Unity teams start​

Most teams begin with one of these integrations.

Path A: Verify ownership​

Use OGAL to verify that a wallet owns a specific asset before you unlock:

  • A level editor
  • A cosmetic set
  • A creator role
  • A premium mode
  • Access to an asset bundle

Path B: Load creator content​

Use OGAL to load UGC content that is referenced by an on-chain identity:

  • Levels
  • Items
  • Avatars
  • Configured experiences

Loading OGAL-referenced content does not require a wallet connection; only mint and update flows do.

Path C: Enable reuse​

Use OGAL to allow assets minted in one app to show up in another.

This is the “compounding” behavior OGAL unlocks.

You can start with one of these in a single sprint.

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.

Read-only verification and asset loading can be done without a wallet connection; wallets are only needed for asset creation, minting, or updates (gas fees).

Instant gratification checklist​

If you want to know you have it working quickly, aim for this first:

  • Connect a wallet in Unity (only if verifying ownership or minting)
  • Fetch an OGAL asset by public key
  • Verify ownership and mutability
  • Load the metadata URI
  • Reconstruct the content at runtime
  • Render or use the content inside your app

Once you can do that, you are OGAL-enabled.

Support and feedback​

If you hit friction:

  • Document it
  • Share it in Discord
  • We treat integration friction as a product bug

The goal is that OGAL feels like an accelerator, not a burden.

Design rule for integrators​

Start small.

Use OGAL for truth first. Only add packaging or monetization when you have a real reason.

That is how the ecosystem stays open and future-proof.

Success checklist​

Next steps​

Follow this order:

  1. Quickstart A minimal end-to-end Unity integration you can validate quickly.

  2. Toolbelt Overview What the SDK includes, and how to structure dependencies cleanly.

  3. Compatibility Matrix Supported Unity versions, platforms, and tooling requirements.

  4. Common Patterns Proven Unity workflows for production implementations.

When you should reach out​

If you need help mapping OGAL into an existing live Unity title, or you want to validate a custom asset pipeline, start with the Quickstart and then move to the integration guide. These two documents cover the fastest path from prototype to production readiness.