10,000 shielded identities, each a tokenized bond, composed in 26 x 26 pixels and minted on BNB Smart Chain.
The engine that composes them runs in this page, so an identity can be watched being built before it exists anywhere else. Pick a term at mint and the Zomi draws a coupon from a reserve that one percent of every $Z0MI swap feeds.
Six ids, composed here by the engine from the locked pixel system. They were found by scanning the issue for six different accent families and six different shell platings, so the strip shows the width of the set rather than six of the same Zomi. Open one for its explorer entry, where every layer it carries is listed.
Current lowest price
none
nothing is listed
For sale
0
no listings yet
Sales, 12 months
0
no sales yet
Lifetime sale value
0
no volume yet
Recent sales
0
30d / 90d / 12mo
Nothing has been minted, so there is nothing here to read. The moment ZomiBond is live on BNB Smart Chain this panel fills from the contract, and until then it stays empty rather than guessing.
Term
30 days
weight 10, written 1.0x
The short rung. Locked for a month, then claimable whenever the holder wants it.
Term
90 days
weight 15, written 1.5x
Half again the share of the reserve for three times the lock. The middle of the ladder.
Term
180 days
weight 20, written 2.0x
Twice the share. Six months before the first claim, and the weight never steps back down.
One Zomi, end to end
Bond index
The index only moves when the reserve is funded.
The contract that does all four is being written now and is not deployed. The controls it will ship with are written down before there is an address to point at, so the list of powers cannot quietly grow between the promise and the deployment.
Term chosen
Picking 30, 90 or 180 days writes a weight of 10, 15 or 20 into the token itself. There is no second contract to stake into and no position to open: the weight is a field on the Zomi, and the Zomi is the bond.
Index rising
Whenever the reserve grows, the index rises by that growth divided by the total weight of every live Zomi. Each Zomi remembers the index it last settled at, so what it is owed is the distance between the two, times its weight.
pending = weight x (index - checkpoint) weight = 10 | 15 | 20 by term index += growth / totalWeight on every funding claim allowed from mintedAt + term
Maturity
The claim pays BNB on BNB Smart Chain to the wallet holding the Zomi, and it costs the same gas whether ten Zomi exist or ten thousand: nothing is looped over, one subtraction settles the account. The weight does not step back down afterwards.
Transfer carries pending
A Zomi is a plain ERC-721, so it moves wherever ERC-721s move, and the pending amount goes with it. That is why the price of a Zomi carries whatever it has already accrued, and why a buyer is buying a position and not just a picture.
Reserve balance
0 BNB
Nothing has funded it yet. The reserve is a balance on the contract, separate from mint proceeds. The owner can withdraw proceeds and cannot touch the reserve.
Where the reserve comes from
$Z0MI trades in a Uniswap V4 pool with the Zomi hook attached, and one percent of every swap in either direction is routed into the reserve. That is the only inflow the coupons are paid from, and it arrives with the contract rather than being live today.
Mint proceeds are a separate balance. The owner can withdraw proceeds and has no path to the reserve, which is the control the contract page documents line by line.
Reading the rank file.
Rank comes out of composing all 10,000 once and counting what actually occurred, so these eight are the rarest the engine issues. Highest sales replace this grid once ZomiBond is live and a Zomi has changed hands for value.
Taking a walk through the issue.
Eight ids from a seeded walk. The seed is today's date in UTC, so the walk is the same for everyone who opens the page today and a different eight tomorrow. Recent transfers replace this grid once the contract is live. Open the explorer to walk it yourself.
Mint
Open the engine, watch a Zomi compose itself layer by layer, choose 30, 90 or 180 days and mint it on BNB Smart Chain. The term is written into the token and never changes after that.
Hold
Nothing has to be staked and nothing has to be locked in a second contract. Holding the token is the position, and the index keeps moving under it while the reserve grows.
Claim
After the term has elapsed the coupon can be claimed at any time, in BNB, to the wallet that holds the Zomi. The weight stays where it was: a 180 day Zomi keeps earning twice a 30 day one for ever.
Route to shielded
Set a Zcash shielded address on the Zomi and only a hash of it reaches the chain. Coupons pay in BNB today and the shielded ZEC route is next, so this stores a preference and settles nothing yet.
Trade
The token is a plain ERC-721, so it moves wherever ERC-721s move. Pending coupon travels with it, which means the price of a Zomi carries whatever it has already earned.
$Z0MI is the token whose trading feeds the bond reserve. It trades in a Uniswap V4 pool with the Zomi hook attached, and one percent of every swap in either direction is sent to the reserve that the coupons are paid from.
The address below is printed straight from the site configuration, which is written by a script that checks the code and the symbol over RPC first. Nothing is shown here until that check passes.
Token contract
issuance pending trading pair pendingTicker $Z0MI, with a zero. Never written any other way, and never uppercased by a stylesheet. The terms say how it is issued.