Lite Whitepaper

Sandbox GHI Whitepaper

Generative Hive Intelligence

ExperimentalDraft tokenomicsEarly infrastructure phase

Public protocol overview of the Sandbox GHI ecosystem, covering Agent NFTs, rentable intelligence, marketplace access, control disclosures, and draft token layers.

Draft v0.95Last updated 2026-05-10Pre-launch clarity revision
Draft status: token mechanics, governance scope, fee details, and some operational parameters remain subject to change before any public token launch.
NFT Supply5,000agent identities
Fee ModelDraftsubject to final marketplace rules
Tier Slots2-4module capacity by rarity
SettlementSOLphase 1 direction

What Is Sandbox GHI In 30 Seconds?

Sandbox GHI is best understood as degen intelligence infrastructure plus an access marketplace, not as a passive-yield NFT pitch.

Sandbox GHI is degen intelligence infrastructure for Solana.

Agent NFTs act as configuration and access-control objects, not company equity.

Renters buy time-bounded access to tools, dashboards, alerts, and APIs.

Some control surfaces may remain multisig-administered during early launch.

One-Page Trust Surface

The biggest pre-launch requirement is clarity. These are the assumptions users should understand before mint, before rentals, and before any future token event.

01

Initial multisig control is expected for critical operational and security actions.

02

Centralized emergency actions may exist during early launch phases.

03

Tokenomics remain draft-stage and are subject to change before any public token launch.

04

Off-chain outputs can leak through screenshots, forwarding, and copied data.

05

No NFT or token should be treated as a guaranteed financial return instrument.

Product and Control Flow

Sandbox GHI should be understood as entitlement-aware software infrastructure layered on top of Solana and off-chain delivery systems.

UserHolder / Renter

Chooses listings, configures agents, consumes outputs.

MarketplaceListings + Payments

Rental term, pricing, entitlement record, history.

Access LayerSessions + Revocation

Dashboards, APIs, webhooks, Telegram routing, rate limits.

Agent ToolingModules + Feeds

Wallet tracking, launch monitoring, risk scans, narratives.

Lifecycle Before Revenue Accounting

Delivery rules matter more than hype. The rental path should be observable, time-bounded, and revocable at the product layer.

01

Listing opened with explicit duration, price, and access scope.

02

Renter pays and protocol records rental instance.

03

Access layer activates sessions, tokens, and delivery channels.

04

Agent tooling serves dashboards, feeds, alerts, and APIs during active term.

05

Expiry triggers revocation, token rotation, and listing history updates.

Marketplace and Agent Rental Paths

These quick visuals make the trust surface obvious: discovery, entitlement, delivery, and control are separate layers.

Marketplace Flow

Discover listingReview termsPayRental recorded

Admin / Control Plane

Multisig / adminUpgrade / freeze / reviewTreasury / reserve custodyInfra credential rotation

Agent Rental Flow

Holder configures agentListing goes liveRenter gains accessOutputs delivered

Executive Summary

Sandbox GHI is a Solana-native intelligence marketplace built around rentable Agent NFTs. The NFT is the ownership and configuration layer. The tooling is the service layer. The marketplace is the distribution layer.

holders configure and control agent behavior

renters buy time-bounded access to tools, not the NFT itself

protocol fees and listing rules remain marketplace-defined

reputation should reflect uptime, delivery quality, and marketplace behavior

Core Concept

Each Agent NFT is intended to represent a persistent agent identity tied to configuration state, module capacity, listing rights, reputation history, and future upgrade path eligibility.

private mode for direct self-use

rental mode for marketplace distribution

hybrid mode for keeping some outputs private while exposing selected renter surfaces

Marketplace Mechanics

Listings are intended to represent protocol-managed access to dashboards, alerts, APIs, and other configured outputs. Terms should be explicit before payment and should not change retroactively during an active rental.

fixed-duration rentals with explicit activation and expiry timestamps

product-layer entitlement checks for dashboards, APIs, webhooks, and Telegram routing

capacity-aware listings when concurrency limits apply

protocol records of rental state, entitlement state, and listing history

Rental Delivery & Access Policy

Successful delivery means the rental is recorded and the renter receives the promised access surfaces for the active term, subject to documented outages or degraded conditions. It does not mean perfect alpha, perfect uptime, or guaranteed exclusivity.

access may include dashboards, feeds, alerts, Telegram notifications, and APIs

expired rentals should trigger session invalidation, token rotation, and entitlement revocation where possible

rate limits, duplicate-session checks, and session monitoring reduce abuse but do not eliminate it

Refund, failed-delivery, and dispute handling rules will be published before paid marketplace rentals go live.

Control & Security

During early launch phases, certain operational controls may remain under multisig administration to respond to critical security, marketplace, or infrastructure incidents. This should be treated as an explicit trust assumption, not a hidden one.

Upgrade authority, treasury custody, reserve NFT custody, signer thresholds, emergency pause authority, and marketplace control surfaces will be disclosed before public mint or marketplace activation.

emergency pause, listing freeze, and abuse-response powers may exist early

early governance should be read as signaling-oriented unless binding governance is explicitly introduced later

Draft / Subject to Change Before Token Launch

These token layers are still draft-stage. Users should not assume fixed conversion, fixed utility, fixed governance power, or fixed fee linkage until a finalized economics annex is published.

Draft / Subject to Change Before Token Launch

GHI

Draft supply: 1,000,000,000

Longer-term utility, upgrades, premium protocol actions, and optional governance participation.

  • Draft-stage only. Mechanics may change before launch.
  • No guaranteed governance power, liquidity, or fee rights.
  • Emissions, sinks, and treasury release remain subject to future specification.
Draft / Subject to Change Before Token Launch

SGHI

Draft supply: 100,000,000

Early access, whitelist positioning, community participation, and pre-launch ecosystem growth.

  • Draft-stage only. Conversion and redemption treatment are not finalized.
  • No guaranteed conversion into `GHI` or permanent utility scope.
  • Launch sequencing and allocation details may change before any token event.

Supported At Launch

The point of this section is to reduce assumption drift. Day 1 scope should be explicit.

Agent NFT mint and ownership tracking.

Basic marketplace listing structure for time-bounded access.

Planned/configured delivery surfaces, activated only when available.

Access revocation, session control, and rental state tracking at the product layer.

Manual review and admin-assisted incident response during early infrastructure phase.

Not Supported At Launch

This is where expectation management matters most. If something is not live, not final, or not enforceable yet, the paper should say it directly.

Advanced decentralized governance across all control surfaces.

Finalized token utility, final token conversions, or final fee-link guarantees.

Guaranteed agent demand, profitability, or utilization.

Perfect anti-leak enforcement for screenshots, forwards, or copied outputs.

Fully trustless removal of multisig or emergency admin powers on day 1.

Token Ecosystem

Sandbox GHI is designed around Agent NFTs plus draft-stage `GHI` and `SGHI` token layers. These mechanics are not final launch commitments.

`GHI` is intended for longer-term utility, upgrades, and optional governance participation

`SGHI` is intended for early ecosystem access, community positioning, and pre-launch growth

users should not assume guaranteed conversion, guaranteed liquidity, guaranteed fee share, or guaranteed governance power

a finalized token specification and economics annex is expected before any public token launch

Reputation & Integrity

The protocol should assume attempts at self-rental abuse, wash usage, fake engagement, cartel feedback loops, and sybil reputation farming. The goal is to make manipulation harder, costlier, and easier to detect.

anomaly detection on rental and rating patterns

delayed weighting for new or suspicious activity

linked-wallet heuristics and integrity scoring

manual review powers during early launch phases

Known Risks

Sandbox GHI is an intelligence product, not a guarantee engine. Users should expect infrastructure, market, and governance risk during early launch.

Solana congestion, RPC dependency, and smart contract risk

off-chain dashboard, API, and alert pipeline downtime

data quality degradation and delayed or noisy signals

output leakage, centralization risk, token non-finality, and evolving regulatory treatment

What Users Should Assume Early

Solana outages or congestion can affect activation and settlement timing.

RPC, indexing, and off-chain infra failures can degrade output quality or uptime.

Smart contract or upgrade mistakes may create operational or fund-handling risk.

Screenshots, forwarded alerts, and copied outputs can reduce exclusivity.

Early multisig/admin powers create real centralization and operator-trust surface.

Clearer Surface, Same Core Idea

Sandbox GHI remains a Solana-native degen intelligence marketplace. The main upgrade here is not more legalese. It is clearer admin trust disclosure, cleaner rental behavior, more realistic product risk framing, and less investment-pitch ambiguity.