GRIDKEEPERSOPERATORS OF THE LIVING GRID
ROBINHOOD
03 REWARD PROTOCOL — IN DEVELOPMENT

Revenue in.
RWA planned.

The planned protocol will use only eligible revenue actually collected on-chain to fund reward inventory. No Employment position, reward route, funded pool, or claim is live yet.

Funded inventory required Claims will activate only after RWA reaches the isolated Rewards contract.
Traceable by design Revenue receipt, conversion, deposit, and claim will remain visible on-chain.
01

NFT creator royalties

Eligible creator earnings may fund rewards after royalty routing to RevenueVault is deployed.

02

Project-token fees

Future configured token fees may route into the same auditable revenue source.

03

Pool conversion

The planned allocator will budget revenue by active pool weight and buy the allowlisted RWA.

04

Pool-specific rewards

Each RWA will accrue only to NFTs employed in that asset's pool through isolated accounting.

04 PLANNED REWARD POOLS

Choose what
your NFT could earn.

Every asset below has a live token contract on Robinhood Chain. The protocol swap routes and funded inventory remain pending contract deployment.

TOKENIZED EQUITYSPCX

Space Exploration Technologies Corp. Class A Common Stock • Robinhood Token

0x4a0E65A3…Fae35eEaTOKEN LIVE / ROUTE PENDING
VERIFY TOKEN PREVIEW EMPLOYMENT
05 REVENUE BOUNDARIES

What enters.
What does not.

Protocol revenue must be explicitly owned and received by GridKeepers contracts. Marketplace volume, token volume, and headline fees are not the same as revenue collected.

ELIGIBLE SOURCE

Creator royalties received

ERC-2981 creator earnings actually paid by a compatible marketplace and delivered to the configured recipient.

ELIGIBLE SOURCE

Configured token fees

Buy/sell fees that the final token mechanism successfully routes into the Revenue Vault.

NOT PROTOCOL REVENUE

Marketplace platform fee

OpenSea or another marketplace keeps its own platform charge. GridKeepers cannot allocate revenue it does not own.

GRIDPULSEROUTES PENDING
01
02
03
06 ACCOUNTING MODEL

No wallet loops.

The planned Rewards contract maintains separate accounting for every allowlisted RWA. Each holder claims per asset instead of the contract pushing thousands of transfers.

  • Real conversion Only collected revenue can become reward inventory.
  • Gas efficient Reward accrual does not loop through 3,333 wallets.
  • Auditable Swaps, allocations, and claims will remain independently verifiable on-chain.
EXPLORE EMPLOYMENT DESIGN
07 PLANNED REWARD INDEX

Fund a pool.
Accrue by weight.

Under the planned rules, each employed NFT represents one unit only inside its chosen pool. Its accounting changes only when new inventory of the same RWA enters Rewards.

READ ACCOUNTING DOCS
POOL REVENUE ALLOCATION
COLLECTED REVENUE×POOL NFTS ÷ ALL EMPLOYED
POOL INDEX INCREMENT
RWA BOUGHT FOR POOL÷NFTS IN THAT POOL
ACCOUNT CLAIMABLE
POSITION WEIGHT×INDEX−REWARD DEBT
Integer precision and rounding behavior will be enforced by the verified Rewards contract.
08 CONVERSION CONTROLS

Automation needs
hard boundaries.

The final executor must not accept arbitrary swaps. Every asset, router, route, amount, and timing rule belongs in verified contract configuration.

Whitelisted paths

Only approved revenue assets, RWA assets, routers, and swap paths may execute.

Slippage protection

Every conversion enforces a minimum output and rejects execution outside configured bounds.

Thresholds and cooldown

Minimum revenue, maximum trade size, and timing controls limit unnecessary or oversized swaps.

Pause on failure

Authorized emergency controls stop new conversions without inventing or deleting holder balances.

VERIFY THE MODEL

Read the protocol reference.

Review proposed contract surfaces, lifecycle rules, network configuration, and deployment status.

OPEN DOCUMENTATION