GLYPHS
1500 on-chain generative pixel PFPs. Each $GLYPH token is also a unique NFT. Art regenerates with every transfer.
› SAMPLE OUTPUT
12 random glyphs · all generated 100% on-chain by the renderer contract
› HOW IT WORKS
› RARITY TIERS
*approximate distribution at full mint · actual depends on entropy
› FAQ
› What is ERC404?
An unofficial token standard created by Pandora Labs (0xacme) in February 2024. It blends ERC-20 and ERC-721 in one contract: every whole token is also a unique NFT. It's experimental and not recognized by the Ethereum Foundation. ERC404 is open-source under MIT. We adapted the pattern; we are not affiliated with Pandora Labs.
› Why is the art regenerating on transfers?
It's how ERC404 works. When 1 token crosses a wallet boundary, the sender's NFT is burned and a fresh one is minted to the receiver. The receiver's new NFT has fresh pseudo-randomness from block data, so its traits are different. This means trading is also a re-roll mechanic.
› Where is the art stored?
100% on Ethereum. Both the trait logic and the SVG drawing code are in a separate renderer contract. There is no IPFS, no Arweave, no off-chain server. tokenURI() returns base64-encoded JSON with embedded base64 SVG.
› Has the contract been audited?
Not by a paid auditor. We've written 13 passing test cases covering the supply invariant, mint flow, ERC404 hybrid logic, and admin functions. We will publish any third-party audit on /audit if and when one is commissioned. Until then, the unaudited badge stays on.
› What does the deployer hold?
700 $GLYPH (47% of supply) — used to seed Uniswap liquidity after the public sale of 800 sells out. The contract has no team allocation, no vesting, no ongoing emissions. Total supply is fixed at 1500 forever.
› What can the owner do?
Open/close the mint, set the renderer (until locked), withdraw ETH from the contract (the contract holds none — ETH forwards to the deployer immediately on each mint). Owner cannot mint new tokens, change supply, freeze transfers, or alter rarity logic.