Most of what a blockchain does is let value move freely. Every now and then, though, the right thing to do is to stop some of it from moving. BZE v8.2.0, live on mainnet since October 26, added two tools for exactly that: one that refuses a token at the border, and one that freezes a token on the DEX. This article explains why we needed them, how each one works, and what they mean for you. It is a little more technical than our usual updates, but no deeper than it has to be.
Why we needed them
A decentralised exchange is honest about one thing only: the balance of its pools and order books. It cannot tell whether a token is still backed by anything. As long as someone is willing to trade it, the DEX will trade it.
That is fine until a token loses its backing. Circle is retiring USDC on the Noble chain, the chain that brought USDC into Cosmos and onto BZE, where it shows as USDC.n. Circle closes the migration window on January 12, 2027. After that, only USDC sitting in a wallet its owner controls on Noble can still be redeemed, through a manual process, and USDC.n left on BZE is not in such a wallet. Left alone, the last holders would keep swapping it into BZE and other real assets, draining the good side of every pool it sits in, including the liquidity the protocol itself owns. The same thing happens, more quietly, when a chain shuts down: its tokens on BZE can no longer go home, and whatever they were worth, they now trade only on hope.
There are two doors a bad token can come through. The bridge, which lets new coins in, and the DEX, which lets coins change hands. v8.2.0 gives governance a key to each.
Closing the door: blocking inbound transfers
A cross-chain transfer over IBC works like a handshake. The sending chain locks the coins in escrow and sends a packet. The receiving chain mints a matching voucher and answers with an acknowledgement. Only when that acknowledgement arrives does the sender consider the transfer done.
The inbound block sits right in front of BZE’s side of that handshake. Governance keeps a short list of channel and token pairs that BZE no longer accepts. When a packet arrives for one of them, BZE answers with an error acknowledgement instead of minting anything. The sending chain reads that answer and refunds the escrowed coins to the sender. Nothing is minted on BZE, nothing is lost on the other side. The coins simply bounce back.
Press enter or click to view image in full size
Three details matter here:
Only the inbound direction is inspected. Outgoing transfers, their acknowledgements, timeout refunds and the channels themselves behave exactly as before. You can always send USDC.n back to Noble.
Coins that originated on BZE always come back. If you moved BZE to another chain and send it home, that is a return, not a new mint, and the filter lets it through. Blocking it would strand BZE-origin funds abroad.
Every refusal leaves a trace. Each bounced packet emits an event with the channel, token, amount, sender and receiver, so relayers and the explorer can see what happened.
Since the upgrade, the list holds one entry: USDC from Noble. New USDC.n cannot enter BZE any more. The deposit form in our apps stops offering it, and if you try from another wallet, the coins come back to your Noble address.
Freezing a token: the halt
The second tool works inside BZE. With a governance proposal, any token except BZE itself can be halted on the DEX. A halt is a single switch per token, kept in a list that costs the chain one lookup to check, however many tokens are on it, and it is lifted the same way it is set.
Get beezee’s stories in your inbox
Join Medium for free to get updates from this writer.
Subscribe
Remember me for faster sign in
While a token is halted, everything that would create a new position in it is refused before any trading fee is charged or any of your funds move: placing an order or filling orders on any market where it is the base or the quote, swapping through any pool that holds it, even as a middle hop of a longer route, opening a new market or pool with it, adding liquidity to a pool that holds it, and paying transaction fees in it. The refused transaction still pays its network fee, like any failed transaction on any chain. That is why the apps hide these actions for a halted token, so you never send one by accident.
Everything that lets you get out keeps working: cancelling your resting orders, removing your liquidity, sending the token to another address, transferring it over IBC, and staking or rewards that merely hold it. Nothing is swept, force-cancelled or taken. Your resting orders and your pool shares stay exactly where they are until you decide what to do with them.
Press enter or click to view image in full size
Two consequences are worth spelling out. First, both sides of an order book freeze. Every fill has one party receiving the halted token, so there is no safe “sell only” direction. Second, orders that the chain had already accepted a block or two before the halt took effect still execute normally. The halt stops new orders from entering, and the small backlog drains within a few blocks.
The apps follow the chain. The DEX shows a “Trading halted” notice on the asset, its markets and its pools, replaces the buy, sell and add-liquidity forms with an explanation, and leaves Cancel and Remove Liquidity exactly where they were. The explorer lists every halted token on its Parameters page, with the same explanation.
The first use: USDC.n and three tokens from closed chains
The first halt is already in effect. Proposal 50 passed on October 31 without a single vote against. It halted USDC.n on the DEX, and with it three tokens whose home chains have gone quiet: the old Vidulum VDL, Jackal’s JKL and OmniFlix’s FLIX. Their IBC connections to BZE have expired, so those tokens can no longer move in either direction. Halting them means nobody can trade a token that can never leave for something that can.
Press enter or click to view image in full size
If you hold USDC.n on BZE, the halt changes nothing about what you should already be doing: move it back to Noble and on to Injective-issued USDC before Circle’s deadline. If some of it is in a liquidity pool, remove your liquidity first. A step-by-step guide is coming. The protocol-owned USDC.n liquidity has already been moved to USDC.inj, and new deposits of USDC.inj are the way forward for stablecoins on BZE.
If you hold one of the three stranded tokens, there is nothing you need to do. They stay in your wallet. The halt only makes sure they are not swapped for real value on the way out.
Why we built it this way
Neither tool knows anything about USDC. One is a governance-managed list of channels, the other a governance-managed list of tokens, and both can be edited or reverted by a later proposal. The next time an issuer retires an asset or a chain goes dark, the answer is a proposal, not a chain upgrade.
Both are also deliberately narrow. The inbound block looks at one direction of one handshake. The halt refuses new positions and nothing else. We would rather have two small, well-understood switches than one big emergency lever, because the point of these tools is to protect people’s funds without ever touching them.
BZE keeps moving forward.
First time hearing about us? Visit our website to learn more about BZE.
Feel free to engage in a discussion with us on any of our communication channels: Twitter, Medium Publication, Discord or Telegram.
