Skip to main content

Non-Unity Developer FAQ

This FAQ answers the most common questions non-Unity teams ask when onboarding to OGAL and OPP.

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.

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 need Unity tooling to integrate OGAL?​

No.

OGAL is a public Solana program and can be integrated directly using:

  • @solana/web3.js (web)
  • Solana Rust SDKs (backend/indexers)
  • Godot HTTP/REST + a backend signer
  • Unreal C++ + a backend signer

The important part is that your clients derive the same PDAs and validate the same account layouts as described in the Non-Unity OGAL Integration doc.

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.

Should I run an indexer?​

If you need search, feeds, or analytics, yes.

RPC alone is fine for verification, but indexers give you:

  • Historical queries
  • Faster UX
  • Lower RPC pressure

Most teams index ObjectMinted and ManifestUpdated events and store results keyed by manifest PDA + mint.

Are retries automatic?​

Usually no, by design.

  • OGAL avoids implicit retries
  • Users must stay in control of signing
  • Network conditions are variable

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?​

OGAL guarantees integrity, not availability.

Best practices include:

  • Validate metadata hashes
  • Use multiple gateways
  • Cache reconstructed assets

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 level:

  • OGAL is live on mainnet and backs Token Toss
  • OPP is spec-complete with execution in progress

Client tooling is up to each team, but the on-chain guarantees are stable.