Altcoins
Oraichain approves an upgrade that enables account freezes
Proposal 332 passed on November 22. The planned system can block outgoing transfers from an account and reserves its operations for an authorization requiring four of six signatures.

Voting closed on November 22
Oraichain governance passed proposal 332 when voting closed on November 22, 2026, at 07:54 UTC. The chain’s public endpoint shows that the proposal passed. The final tally contains only votes in favor, with no votes against, abstentions, or vetoes. The result describes the votes recorded. It does not mean every ORAI token holder participated.
The proposal was submitted on November 17 and calls for upgrading the network to version 0.50.16. The decision covers installing a new mechanism in the chain’s software. It names no account to freeze. The distinction matters for users and node operators alike. The vote outcome has been decided, while the new rules still have to take effect at the scheduled block.
Four of six signatures to intervene
The proposal adds an account blocklist to the `x/txfees` module. An address on the list can no longer make outgoing transfers. The text provides for three distinct operations. Freezing blocks outgoing transfers, lifting the freeze removes the account from the list, and recovery transfers the remaining balance to a secure address. The authors present the procedure as a way to gain time after an account has been compromised.
Each operation is reserved for the Oraichain Foundation’s authorized group and requires four of six signatures. A key held by one member is therefore insufficient. Module accounts, which serve the chain’s internal operations, are excluded. The adopted text sets these operating conditions. It leaves open the criteria that will guide signers in a specific case.
Activation depends on block height
The plan recorded on-chain sets activation at block 131,260,000. The proposal text gives November 23 at about 07:00 UTC as an estimate. The network’s arrival at that height determines the actual time. The announced date gives operators time to prepare. Nodes are then expected to halt so their operators can replace the software with version 0.50.16. The November 22 vote confirms neither that halt nor the resumption of block production.
The outcome leaves two distinct steps to follow. The first is technical and can be verified by the transition at the target block and by the chain resuming operation. The second concerns use of the mechanism. Approval makes it possible to freeze an account or transfer its balance under the stated conditions, without establishing that an account has been targeted. Any intervention will require its own on-chain evidence.
