Skip to main content

SolanaConfiguration Field Reference

SolanaConfiguration is the single source of truth for Toolbelt runtime wiring. The Unity inspector groups map directly to serialized fields in Runtime/Toolbelt/_Data/_Scripts/SolanaConfiguration.cs. Use the sections below to locate the matching fields and confirm your values before shipping.

Source of truth: Runtime/Toolbelt/_Data/_Scripts/SolanaConfiguration.cs

RPC Endpoints and Priorities​

These fields determine where the runtime sends JSON-RPC traffic and how failover is prioritized.

  • RPC endpoint list + priority order: the ordered list the endpoint manager evaluates first. Place your preferred primary endpoint at the top to control default routing.
  • Primary RPC selection: the runtime selects the first healthy entry as the primary endpoint on startup.
  • Priority notes: keep private or paid endpoints higher in the list so they are used before public fallbacks.

Streaming RPC URLs​

Streaming endpoints power websocket subscriptions and real-time listeners.

  • Streaming RPC URL list: the ordered list used for websocket connections.
  • Streaming fallback: confirm the runtime can switch to a secondary streaming URL when the first is unavailable.
  • Consistency: ensure streaming URLs match the environments used by your RPC list (same cluster, same provider).

RPC Rate Limits​

These fields guard request throughput and retry pressure.

  • Per-endpoint rate limits: caps applied to each RPC endpoint entry.
  • Burst vs. steady-state: validate both sustained request rates and any burst allowances.
  • Runtime behavior: rate limits are enforced before dispatching to the SDK, so align them with provider contracts.

OGAL Program, Namespace, and Authority​

These fields identify which on-chain OGAL program and namespace your runtime uses.

  • OGAL program ID: the deployed program address that mint and metadata operations target.
  • Namespace account: the namespace that governs collections and authority rules.
  • Authority accounts: runtime-signing or admin authorities used for minting and updates.

Minting Compute Unit Settings​

These values shape transaction fees and success rates for mint flows.

  • Compute unit limit: maximum units allocated for mint transactions.
  • Compute unit price: prioritization fee (micro-lamports) applied to mint transactions.
  • Override behavior: confirm whether the toolbelt uses defaults or applies configured overrides.

Memo Formats​

Memo configuration standardizes how the runtime writes human- or analytics-readable markers into transactions.

  • Mint memo format: the string format template used for mint transactions.
  • Transfer memo format: the template used for transfers or other asset operations.
  • Required tokens: ensure any placeholders (player ID, asset ID, etc.) are populated by your runtime.

Rent Deposit Settings​

These fields control lamport deposits for metadata or storage accounts.

  • Rent-exempt deposit amount: the lamports reserved for rent-exemption.
  • Deposit caching: confirm whether rent values are cached to reduce repeat RPC calls.
  • Balance guardrails: check thresholds that warn or fail if deposit funds are insufficient.

Cache TTLs​

Cache settings define how long Toolbelt retains remote data before refreshing.

  • RPC response TTLs: duration that on-chain fetches are cached.
  • Metadata TTLs: how long off-chain metadata stays in memory before refresh.
  • Access cache TTLs: durations for ownership/access gating caches.

Collection Configuration​

Collection settings describe which on-chain collections the runtime treats as canonical.

  • Collection list: array of collection IDs or metadata addresses.
  • Expected update authority: authority expected by validation checks.
  • Collection metadata constraints: rules or toggles used to validate minting inputs.

Service References​

SolanaConfiguration exposes references that the runtime resolves during initialization.

  • Wallet + session services: references to wallet, session, and authentication services.
  • Storage services: uploaders, gateways, and storage adapters.
  • Gameplay-facing services: minting, inventory, metadata, and access services.

Field Mapping Tips​

To map a field in the inspector back to code, open Runtime/Toolbelt/_Data/_Scripts/SolanaConfiguration.cs and:

  1. Search for the header text or inspector label that matches the section name above.
  2. Confirm the serialized field name and default value in the class definition.
  3. Track any runtime usage in ToolbeltRuntime or service builders to understand how the value is applied.

This keeps the documentation aligned with the code even if new fields are added later.