Skip to main content

Developer FAQ

This FAQ answers the most common questions Unity developers ask when onboarding to OGAL, OPP, and the Solana Toolbelt for Unity.

It is written to be practical, accurate to the current codebase, and explicit about design intent.

If you are ever unsure how something is supposed to work, this document should remove ambiguity.

What is OGAL, in one sentence?​

OGAL (Owner-Governed Asset Ledger) is an on-chain registry that defines canonical asset identity, ownership, mutability rules, and provenance, without enforcing monetization or platform behavior.

OGAL defines what is true, not how value is captured.

How does OGAL differ from Metaplex NFTs?​

OGAL is the protocol layer that defines canonical identity and provenance, while Metaplex is the NFT metadata layer OGAL updates under strict rules.

  • Canonical identity & provenance: OGAL anchors identity in the ObjectManifest PDA + object mint, so provenance stays stable even as metadata evolves.
  • Ownership-based update rules: OGAL only permits updates when the current NFT owner proves ownership.
  • Stable identity across metadata changes: OGAL treats metadata as mutable content, not the asset’s identity.
  • Controlled CPI metadata updates: OGAL updates Metaplex metadata via CPI using the auth PDA as update authority, keeping Metaplex aligned with OGAL truth.

Is OGAL a marketplace?​

No.

OGAL:

  • Does not list assets
  • Does not sell assets
  • Does not escrow funds
  • Does not enforce monetization

Marketplaces, pricing, and discovery are optional layers built on top of OGAL.

Do I have to use the Solana Toolbelt to integrate OGAL?​

No.

OGAL is a public Solana program and can be integrated directly.

However, the Toolbelt dramatically reduces integration time by:

  • Abstracting wallet flows
  • Handling PDA derivations
  • Managing uploads and metadata
  • Translating errors into actionable messages

Think of the Toolbelt as adoption infrastructure, not a requirement for trust.

What exactly does the Toolbelt add beyond the Solana Unity SDK?​

The Toolbelt layers orchestration and domain services on top of the SDK:

  • OGAL mint/update/admin helpers
  • Wallet lifecycle orchestration
  • Storage automation (Bundlr / Arweave)
  • Access control and NFT gating
  • Metadata resilience and validation
  • UI bridge contracts
  • Centralized runtime configuration

It does not replace:

  • The SDK’s RPC stack
  • Wallet client behavior
  • Transaction submission semantics

How is asset ownership enforced?​

Ownership is enforced through standard SPL Token ownership.

OGAL does not custody assets.

When an owner requests a manifest update, OGAL:

  1. Verifies the signer owns a token account
  2. Confirms it matches the expected mint
  3. Requires a positive balance
  4. Only then allows the update

Ownership is observed, not mediated.

What is the canonical identity of an OGAL asset?​

An OGAL asset is identified by two linked anchors:

  • The ObjectManifest PDA (registry truth)
  • The Object Mint (NFT representation)

Together they form a stable identity even as metadata evolves.

Clients should treat:

  • ObjectManifest PDA + mint as the canonical handle.

Can metadata be updated after minting?​

Yes, by the current owner only.

The update_object_manifest instruction:

  • Verifies NFT ownership
  • Updates the manifest hash and URI
  • CPI-calls Metaplex to update the on-chain metadata URI
  • Preserves name, symbol, creators, collection, and fees

The asset identity never changes, only the referenced content.

Does OGAL support automatic royalties?​

OGAL records royalty intent, but does not enforce payouts.

Royalties are:

  • Declared at the asset level
  • Interpreted and enforced by platforms or OPP bundles

This separation keeps OGAL neutral and maximally adoptable.

What is OPP and when should I use it?​

OPP (Open Package Protocol) is an optional composition layer.

Use OPP when you want to:

  • Bundle multiple assets
  • Define usage rules
  • Enable monetization
  • Share revenue across contributors

If you just want reusable assets, you do not need OPP.

Does OPP move money?​

No.

OPP:

  • Describes composition
  • Declares revenue intent
  • Exposes SBOM data

Platforms and applications enforce payments.

What is an SBOM in this system?​

SBOM (Software Bill of Materials) is a machine-readable manifest that declares:

  • Which OGAL assets are included
  • Who owns each asset
  • How revenue should be split when monetization occurs

It is the economic blueprint, not the payment processor.

Are retries automatic?​

Usually no, by design.

The Toolbelt:

  • Avoids implicit retries
  • Surfaces errors explicitly
  • Lets the application decide how to recover

Exceptions exist:

  • OGAL minting supports configurable transport retries
  • RPC endpoint failover is handled by RpcEndpointManager

Retries are opt-in and scoped, not global.

How expensive are OGAL reads?​

Very cheap.

  • Reads are permissionless
  • No lamports move
  • No CPI calls
  • Suitable for frequent verification

Writes are explicit and user-driven.

Can assets be reused freely?​

Yes.

If an asset is not inside a monetized OPP:

  • No fees
  • No approvals
  • No royalties
  • Unlimited reuse

Ownership and mutability rules still apply.

What happens if metadata hosting goes down?​

The Toolbelt:

  • Validates metadata hashes
  • Supports gateway fallback
  • Encourages caching reconstructed assets

OGAL guarantees integrity, not availability of external storage.

Is OGAL upgradeable?​

Yes, with discipline.

  • Programs use upgrade authority
  • Critical flows include pause controls
  • Governance and upgrade strategy are documented separately

Upgrades are intentional and auditable.

Is this production-ready?​

Yes, at the protocol and tooling level:

  • OGAL is live on mainnet and backs Token Toss
  • The Toolbelt is shipping and used in production flows
  • OPP is spec-complete with execution in progress

This is the correct maturity order for infrastructure.

Where should I start as a developer?​

  1. Read Start Here
  2. Run the Quickstart
  3. Integrate OGAL reads
  4. Mint one asset
  5. Update one manifest
  6. Reconstruct and consume it in-game

You will understand the system far better by doing one full loop than reading everything first.

Final Mental Model​

  • OGAL governs truth
  • OPP governs optional value
  • Tooling governs friction
  • Markets govern discovery
  • Applications govern demand

If your architecture respects that separation, you are using the system correctly.