It is rolling out. Now.
https://t.co/Z2LxY6EsLn
the V4 @Uniswap hook $0m0 Issued Bond NFT
0x116620828fa088597d13239079175507d426110d
The $0m0 privacy NFT layer is live in the console, and here is what it does:
Every sealed bond can mint its own NFT. The token carries the commitment and nothing else. Open the metadata and you find a hash, the mark, and silence. No asset, no amount, no history. That is what a privacy NFT means.
Minting is gated by $0m0. Hold the token, seal the bond, mint the proof of it.
Retiring burns the NFT and publishes a nullifier, the same construction Zcash built shielded pools on. The set stays honest without anything ever opening.
And underneath it, the Uniswap v4 hook: every swap in the pool feeds the fee layer, eighty percent burns, and the bond NFTs settle on the same rail as the token.
The contract source is public on the site. Read it, then mint.
BIG UPDATE on @omoonpons
0x116620828fa088597d13239079175507d426110d
Every bond issued through $0m0 is getting its own NFT, minted through a @Uniswap v4 hook and interlinked with the token.
Contracts are being written right now. The patient ones keep getting rewarded here.
What lands:
Seal a bond, mint the NFT that represents it onchain. The commitment lives in the token, the asset stays sealed.
The v4 hook sits on the pool: every swap feeds the fee layer, eighty percent burns, and bond NFTs settle through the same rail.
One system. The token pays, the hook settles, the NFT proves you hold the bond, and none of it opens what you sealed.
$0m0
https://t.co/yBs62bgsAG
$0m0 is boosted on @dexscreener
0x116620828fa088597d13239079175507d426110d
More eyes are about to land on the chart. Here is what they will find when they click through:
A live protocol. Sealing, transfers, and receipt verification working in the console. A privacy NFT layer rolling out on Zcash math. Fifteen million locked forever. A bug bounty with real money behind it. Contract source public on the site.
Most tickers get boosted on a promise. This one got boosted on a product.
The boost brings the crowd. You are reading this before they arrive. That is what early means.
$0m0
https://t.co/yBs62bgsAG
Today is a build day with @Uniswap
New features land on @omoonpons before it ends.
While they ship, here is what already runs, so nobody has to take our word for anything:
The console seals bonds in your browser. An asset, a secret salt, and a one-time key become a single SHA-256 commitment. That hash is all the outside world ever gets.
Transfers move bonds as AES-encrypted packages. The recipient verifies the opening and re-seals under a fresh key that has signed nothing else. The old commitment retires on the spot.
The verifier gives any counterparty exactly one bit: verified true or false. Not the asset, not the size, not the history.
Anchoring writes your commitment into a real transaction from your own wallet. Immutable, timestamped, yours.
Fifteen million $0m0 locked forever underneath it, and the engine's one-bit proofs and fee burn on the way.
The patient ones get rewarded here. They always have been. Watch this space tonight.
$0m0
https://t.co/yBs62bgsAG
The $0m0 bug bounty is open.
0x116620828fa088597d13239079175507d426110d
The whole pitch is that nobody can open your bonds, forge your receipts, or crack your transfer packages. So we are putting money behind it.
Find a real vulnerability, report it privately, get settled in WETH or $0m0. Your pick. First valid report wins, criticals negotiated at the top of the pool.
Scope, severity tiers, and how to submit are on the task page. The engine contracts join the scope the day they deploy.
https://t.co/HcajAfAflC
Still here. Still building on @Uniswap
No countdown today, no announcement. Just the work: the engine in its test pass, the console sealing bonds, the burn design headed for a verified contract on the pool.
Charts have moods. Protocols do not. Every fee that ever settles will still burn eighty percent, whether the candle is green or red, whether anyone is watching or not. That is the point of building something nobody can watch.
The people who seal during the quiet are the ones who never have to chase the loud.
$0m0
0x116620828fa088597d13239079175507d426110d
https://t.co/yBs62bgsAG
The total $0m0 locked is now 15,000,000.
0x116620828fa088597d13239079175507d426110d
Meanwhile the float keeps shrinking from the other side: every bond action burns eighty percent of its fee. Locked supply below, burn above. The middle is what trades.
Seal early with @omoonpons.The set does not wait.
https://t.co/yBs62bgsAG
$0m0 status update.
0x116620828fa088597d13239079175507d426110d
Live right now, on the site, working:
Sealing. Assets become one-hash commitments in your browser.
@omoonpons transfers. Bonds move as encrypted packages and re-seal under fresh keys.
Counterparties check receipts at https://t.co/uD8VkX5VO8 and get one bit back.
Anchoring. Commitments written onchain from your own wallet.
13,000,000 $0m0 locked forever. CA live on the site and in the console.
Shipping next, with the engine:
One-bit proofs. Prove ownership without opening anything, not even to one counterparty.
The fee layer on the Uniswap v4 pool.
Every bond action settles in $0m0 there.
The burn contract. Verified source, public burn function, eighty percent of every fee to the dead address, watchable on the explorer from day one.
Holder slots. Bond capacity that scales with what you hold, shielded like everything else.
Built in the open, sealed by design.
https://t.co/yBs62bgsAG
How an @omoonpons actually works, in plain words.
0x116620828fa088597d13239079175507d426110d
1. SEAL
You pick an asset. Your browser generates a secret salt and a one-time key, then hashes all three together. That hash is the bond. The chain gets the hash and nothing else: not the asset, not the amount, not you.
2. HOLD
Your bond sits in the set next to every other bond, and they all look identical. An observer sees the set change. They never see what changed, or whose it was.
3. PROVE
When someone needs to know, you answer exactly one question. Your counterparty checks the receipt on the site and gets one bit back: verified: true. Your portfolio stays sealed.
Transfers hand the bond over as an encrypted package, and the receiver re-seals it under a fresh key that has signed nothing else. Every action settles a fee in $0m0, and eighty percent of every fee burns.
Try it yourself in the console. Sixty seconds, no signup.
https://t.co/yBs62bgsAG
the burn is not in the token contract,
$0m0 launched through the standard Pons contract. no special functions in the trade path. You can verify that yourself from the contract, and you should.
The burn lives one layer up, in the protocol engine that settles bond actions. Every seal, transfer, and proof pays its fee at that layer, and the engine routes eighty percent of it to the dead address at settlement. That contract ships with the engine on the Uniswap v4 pool, verified source, public burn function, watchable on the explorer from day one.
People are sealing bonds with @omoponpon
https://t.co/0YWjscc5eV
Early is a choice. It is being made right now.
$0m0
0x116620828fa088597d13239079175507d426110d
Here is the part that should make you sit up:
we cannot see them. No dashboard, no counter, no list of users. The protocol was built so that nobody watches, including us. The only evidence is people telling us. That is what product-market fit looks like for privacy.
Every serious market went through this moment. Someone used the thing before it was obvious, before the pool, before the crowd needed permission. Those are the people every protocol ends up rewarding, because they were the ones holding it when it mattered.
The engine ships its one-bit proofs next. The people already sealing will be standing exactly where the volume lands.