DOCS
Technical reference for the collection, ERC-404 state, attributes, activation, rewards, fee flow, market surfaces and frontend behavior.
PIXEL PIPS IN ONE PAGE
Pixel Pips are receivers. Each normal pip is tuned to one of ten channels, the floors, and its antenna decides how well it holds the signal, the tier. Dormant is off. Burning a unit switches it on. Everything below is that sentence in contract terms.
Pixel Pips is a fixed supply collection of 3,334 IDs on Robinhood Chain. IDs 0 through 3329 are 3,330 normal Pips divided evenly across ten floors. IDs 3330 through 3333 are the four specials.
Normal Pips have a floor and tier. Floor is the reward destination and the background identity. Tier is the reward weight and is represented visually by the antenna. The cosmetic attributes are generated deterministically from the collection attribute bytes. New traits must never be inserted into the PRNG stream because doing so would shift every subsequent trait.
The collection has three visual states: pre reveal cartridge, revealed dormant Pip and revealed activated Pip. Status is derived from actual on-chain activation state.
3,334 FIXED IDS
Special IDs never enter the normal random allocator. They do not receive fake floor or tier values. Their metadata exposes their special class instead.
TEN REWARD STREAMS
Every normal floor contains exactly 333 Pips. The floors are NVDA, AAPL, TSLA, GME, SPCX, SPY, PLTR, NFLX, RDDT and MSTR. Floor is represented by background hue and pattern and is also the key used by the reward accumulator.
A floor with zero activated weight does not lose incoming value. Its reward is parked in a pending pot. When the first Pip on that floor activates, that pending value becomes part of the floor's claimable accounting.
WEIGHT IS THE RARITY ENGINE
Tier is stored in the attribute byte and drives the antenna. It is not another cosmetic PRNG draw. The deployed attribute audit verified all 3,330 normal IDs against the manifest with zero tier or floor mismatches.
REVEALED ATTRIBUTES
Revealed normal Pips expose Floor, Tier, Face Colour, Mouth, Ears, Eyewear, Blush, Pupils and Status. Antenna is deliberately excluded as a separate metadata trait because it is the visual representation of Tier.
Status is Dormant or Activated and must follow the actual on-chain activated state. The pre reveal cartridge is an unrevealed image state, not a trait.
BURN ONE UNIT
Activation is a state transition on a specific Pip. The caller must own the Pip. A dormant Pip can be activated once. Activation burns exactly 1 UNIT, changes the status to Activated and adds the Pip's tier weight to its floor's active accounting.
The special IDs do not enter this normal weight path.
ACCUMULATOR MODEL
Rewards are tracked by floor and weight. This makes the accounting scale with activated weight rather than requiring a distribution transaction for every Pip.
On transfer of an activated Pip, accrued value is settled to the current holder before ownership changes. The NFT does not carry an unclaimed seller balance to a new buyer.
THE FEE PIPELINE
The fee system uses a 10,000 BPS denominator. The base fee is 300 BPS. The launch fee is 9000 BPS until the owner calls finalizeLaunchFees(). Whitelist and keeper addresses use the 300 BPS rate from launch. The buyer cooldown is one hour.
At 300 BPS of gross swap volume, that becomes 2.0000% reflections, 0.6375% LP, 0.2125% burn and 0.1500% creator. At 9000 BPS, the corresponding values are 60.000%, 19.125%, 6.375% and 4.500%.
The Pixel Pips fee math was differentially tested against the reference implementation's deployed fee library with 419 carve inputs and 400 fee from gross cases, with zero mismatches.
POT BASED DISTRIBUTION
The WETH reward hook accumulates reflections, LP and burn amounts into pots. The keeper can pull those pots using the hook's pull functions. The hook is not a push based distributor that sends every allocation immediately.
Sinks are configured through configureAndSealSinks and then sealed. The owner and keeper are distinct roles. The keeper is the address used for operational draining and also receives the privileged 300 BPS trading rate.
Verified addresses are kept on the Contracts page.
WHERE PIPS ARE BOUGHT
The market page is the acquisition surface for Pixel Pips. There is no mint. The supply is seeded into the PIPS/WETH pool at launch, so the primary route is the swap: buy PIPS, and every whole unit held is a Pip. The secondary marketplace is for buying a specific Pip from another holder.
The fee engine is not a marketplace. It supports the Pixel Pips reward flow, while buying and trading remain on the Market page.
NO FAKE LIVE NUMBERS
Static collection facts can be shown before deployment. Wallet balances, ownership, activation status, reward balances, market price, liquidity, volume and reward hook pot balances should be read from chain or a defined indexer once the relevant contracts are deployed.
If a contract is not deployed yet, the frontend should say pending deployment rather than inventing a number.
64 PX NATIVE ART
Native art is 64×64. PNG output is 512×512 using nearest neighbor. GIF output is 256×256 using nearest neighbor. The style is a Game Boy Color inspired palette with deliberate dithering, crisp pixel edges, a single dark outline, 1px shadow shell, contact shadows, integer snapped circles, round eyes, eye specular dots, outward ears, hand drawn mouth bitmaps and a forced contrast anchor palette.
Dormant art is cold and near monochrome. Activated art is full color. The antenna is the tier visual. Floor is the background.
WHAT IS DEPLOYED VS PENDING
Pixel Pips is not yet deployed to Robinhood Chain mainnet. The ten contracts were tested two ways before deployment: a mock suite against a simulated pool manager, and a mainnet fork suite that runs the assembled swap path through the live PoolManager, the stock pools and the canonical router.
The attribute audit read all 3,330 normal IDs from a test deployment and verified exact tier counts, exact floor counts, 333 Pips per floor and zero manifest mismatches. A special ID bug was found and fixed. tierOf() and floorOf() both revert for special IDs, and specials no longer enter normal weight logic.
STATE TRANSITIONS
Normal activation requires ownership, normal Pip status and dormant status. Exactly 1 UNIT is burned. The Pip is marked activated, its tier weight is added to the active weight of its floor and a reward accumulator checkpoint is established.
Double activation must revert. Special IDs use a separate path and do not use the normal weight system.
Rewards do not follow the NFT. Before an activated Pip transfers, accrued reward value is settled to the current holder. This prevents the buyer from inheriting the seller's unclaimed rewards.
EXACT CARVE MATH
The fee system uses a 10,000 BPS denominator and 240 total allocation parts. The normal base fee is 300 BPS, or 3%. The launch fee is 9000 BPS, or 90%, until the owner calls finalizeLaunchFees(). Whitelist and keeper accounts pay 300 BPS from launch. Buyer cooldown is one hour.
This math was differentially tested against the reference implementation's deployed fee library using 419 carve inputs and 400 fee-from-gross cases with zero mismatches. The extracted libraries used for the comparison were FullMath and FeeLib.
POTS, NOT PUSH DISTRIBUTION
The WETH reward hook is pot based. It accumulates reflectionPot, lpPot and burnPot. The keeper pulls these balances with pullReflections(), pullLp() and pullBurn().
The hook is not a push distribution that executes a downstream distribution on every swap. Sinks are configured through configureAndSealSinks() and then frozen.
WHAT THE SITE MUST READ
Before deployment, frontend values that depend on contracts must remain pending or not deployed. After deployment, live surfaces should read total supply, activated count, UNIT burned, active floor weights, reward pots, market price, liquidity, volume, reward-engine purchase totals, WETH conversion totals and reward hook pots.
My Pips should enumerate owned Pips and expose IDs, floor, tier, status, activation state and rewards, with activation and claiming actions enabled only when the corresponding contract functionality is live. The Market page remains the place to buy and trade Pips. The fee engine remains internal and never becomes a separate destination page.
64 × 64 NATIVE GRID
Native art is 64×64. PNG output is 512×512 using 8× nearest-neighbor scaling. GIF output is 256×256 using 4× nearest-neighbor scaling. No smoothing or interpolation is allowed.
The locked art direction uses a Game Boy Color look, a single dark outline, no light rim, a 1px shadow shell, contact shadows, integer-snapped circles, round eyes, eye specular dots, outward ears, a minimum 2px antenna stem, hand-drawn mouth bitmaps and a forced-contrast anchor palette. Face hue remains unsnapped. Dormant art is cold and near monochrome. Activated art is full color.
Floor is visually represented by the background. Tier is visually represented by the antenna. Tier must not become a separate metadata trait, and new cosmetic traits must never be inserted into the PRNG stream.
WHAT IS LOCKED
Why are the specials outside the normal allocator?
They are a separate special layer and do not have normal floor or tier semantics.
Does activation require a marketplace?
No. Activation is a direct contract interaction from the wallet dashboard. The market is where the Pip is acquired.
Does the reward token follow the NFT when it is sold?
Accrued value is settled before transfer, so the seller does not hand a hidden reward balance to the buyer.
PIXEL PIPS