Understand
the system.

One protocol. Four moving parts.

GridKeepers separates the live NFT collection from planned revenue, conversion, employment, and reward modules. Minting works independently today; utility execution stays disabled until each required contract is deployed and verified.

From mint to productive ownership.

1. 01
   Prepare native ETH

   Each NFT costs exactly 0.000527 ETH plus Robinhood Chain gas.

2. 02
   Mint a GridKeeper

   The holder submits one payable mint transaction with the exact ETH value for the selected quantity.

3. 03
   Employment after deployment

   The planned flow approves one NFT and 100,000 tokens, transfers those tokens to 0x…dEaD, takes NFT custody, and assigns one selected RWA pool.

4. 04
   Fund RWA pools after routing

   Eligible revenue may be converted only through approved routes into pool-specific reward inventory.

5. 05
   Claim or reroute after funding

   Once live, rewards accrue inside the chosen pool; retirement returns the NFT and stops future accrual.

GridKeepers artwork and production IPFS metadata are complete.

The deterministic 3,333-item release has immutable asset and metadata CIDs, contract-compatible token filenames, and verified public gateway retrieval. A persistent Kubo pin and checksum-verified CAR recovery backup are active. Availability currently relies on one primary pin plus the recovery archive; this is not redundant pinning.

source artwork provenance (SHA-256)
ae18da933afa34ca4e6d0ba1bd80a2b7ff5e7ddf2dc79674c04bc1acd31999a0

production metadata provenance (SHA-256 / deployment bytes32)
8ecb1c0d40601486546bea579d73e3afcfa83cf0bce9cf4405790c940a70206e

base URI
ipfs://bafybeia2x6dyjupzkd63y2ctx3lp6ivyzrrkqo4dbssib46bxggbddpw2a/

Production token metadata uses absolute immutable IPFS asset URIs and unpadded 1.json through 3333.json filenames matching the live NFT contract. Public minting and minted-token browsing are live.

Live NFT and planned utility surface.

Native ETH public mint flow.

1. Read mintPrice() and verify 0.000527 ETH
2. Calculate value = 0.000527 ETH × quantity
3. Simulate publicMint(quantity) with exact native value
4. Submit one payable transaction
5. Wait for confirmation and refresh owned token IDs

The mint uses native ETH only and requires no ERC-20 approval. Quantity limits and live supply remain contract reads. The official interface blocks minting if the verified contract price differs from 0.000527 ETH.

One NFT, one 100,000-token burn, one chosen RWA.

The vault takes custody of one GridKeeper while the Employment contract permanently removes exactly 100,000 project tokens from circulating ownership. The tokens are not deposited, staked, retained by the vault, or refundable; ERC-20 total supply remains unchanged. The NFT contributes one reward unit only to its selected USDG, NVDA, SPCX, TSLA, or AAPL pool.

PUBLIC ROADMAP UI
RWA card → preview selected reward route
→ execution disabled until all utility contracts are verified

PLANNED ATOMIC EMPLOYMENT
approve NFT → approve 100,000-token allowance
→ employ(tokenId, rewardAsset)
→ transfer exactly 100,000 tokens to 0x…dEaD + custody NFT

PLANNED REROUTE
retire(tokenId) → NFT returned; 100,000 tokens remain at 0x…dEaD
→ employing again requires another 100,000 tokens

Reward selection and the fixed 100,000-token requirement are public as protocol documentation. Employment balances, approvals, and transactions remain unavailable until the verified utility contracts are configured; the interface does not fabricate them.

Under the planned rules, accrued balances will remain claimable per RWA after retirement while future accrual stops in the old pool.

One index per RWA, not mass transfers.

The planned protocol does not push tokens to 3,333 wallets. Collected revenue will first be allocated by active pool weight, while every allowlisted asset keeps isolated accounting:

pool budget(asset) = collected revenue × NFTs in asset pool / total employed NFTs
pool increment(asset) = RWA bought for pool / NFTs employed in that asset pool
claimable(account, asset) = pool weight × asset index − asset reward debt

Each participant claims USDG, NVDA, SPCX, TSLA, or AAPL independently. Tokenized equities may be permissioned or eligibility-restricted, so transfer behavior must be validated before a pool is funded.

Protocol revenue is explicitly scoped.

Robinhood Chain mainnet.

Required execution controls.

• Whitelisted revenue assets, RWA assets, routers, and swap paths.
• Maximum slippage, maximum per-swap amount, minimum execution threshold, and cooldown.
• Quote validation or oracle/TWAP protection before conversion.
• Pausable revenue conversion and employment entry during incidents.
• Checks-effects-interactions, reentrancy protection, and safe ERC-20/ERC-721 transfers.
• Employment transfers exactly 100,000 × 10¹⁸ project-token units to the canonical 0x…dEaD address and verifies the dead-address balance delta atomically.
• NFT custody and token burn are atomic: either both complete in one successful employment transaction or every state change reverts.
• Circulating ownership decreases by exactly the employment amount; ERC-20 totalSupply() remains unchanged, and the Employment Vault retains no project-token balance.
• No unbounded loop over NFT holders or employed token IDs during reward deposits.

What remains pending.