CHICKEN BROKERS4,444 chicken brokers
working the floor.
32×32 of flat colour and hard black outline — and the contract
draws every one of those pixels itself. No IPFS, no gateway, no image server: the bird
comes out of tokenURI as an SVG the chain generates on demand. Supply is
capped in code, not in a tweet.
Drawn by the contract ·
Twelve of the four thousand.
Plumage, pattern, comb, headwear, eyes, neckwear, suit, prop and background — nine trait
slots rolled from keccak256(tokenId). Every bird below is the exact SVG the
renderer returns, not a screenshot of one.
What the birds are wearing.
Percentages are the real distribution across all 4,444 tokens, counted at generation time.
Three steps, no allowlist.
Get on Robinhood Chain
Connect any EVM wallet. The site adds and switches the network for you — chain ID 4663, gas paid in ETH.
Mint at 0.0001 ETH
Up to 20 per transaction. The contract charges price() × qty read at mint time and refunds anything above it.
There is no reveal
Your bird exists the moment the token does — the renderer draws it from the id. No pinning, no placeholder box, nothing for the team to switch on later.
Straight answers.
Is 4,444 actually the supply?
Yes — HARD_CAP is a constant in the contract. The owner can shrink the drop
but no function, owner-only or otherwise, can mint past 4,444.
What can the owner do?
Open and pause the sale, change the price, change the per-transaction cap, shrink the supply, set the metadata URI and reveal, mint team tokens inside the cap, and withdraw the mint proceeds. That is the full list, and it is all in the source.
What if I overpay?
The contract sends the difference straight back in the same transaction. If your wallet is a contract that rejects ETH, overpaying will revert — send the exact amount.
Is the art on-chain?
All of it. ChickenRenderer holds the trait tables and the pixel spans in its
own bytecode and builds the SVG inside an eth_call. tokenURI
hands back a data:application/json;base64 blob with that SVG inlined —
no IPFS CID, no HTTP host, nothing that can 404 in five years.
Can the team change the art later?
No. The renderer address is immutable, fixed in the constructor, and the
collection has no setBaseURI, no setRenderer and no reveal
flag — those functions were removed, not just left unused.
How do I know the pictures match the contract?
The Python art engine and the Solidity renderer are diffed against each other pixel by
pixel across all 4,444 token ids before deploy (onchain/verify_onchain.py).
The birds on this page are the strings the contract returns.
Why chickens?
Every trading floor already runs on birds. These ones wear the suit.