Technologie & IA
Osmosis activates targeted restrictions for fund recovery
Osmosis released version 32.0.1 on November 20. According to the release notes, the new rules took effect at block 75,640,600. They limit fund movements for accounts covered by the recovery process associated with the Web3Auth incident.

A change applied at a specific block
Osmosis 32.0.1 was released on November 20, 2026, at 17:17 UTC, according to the official repository. The release notes say validators replaced their software before block 75,640,600 and that the rules took effect at that height. Below that block, the patch retains the behavior of version 32.0.0. The block number determines when the rules begin to apply on the chain, while the time in the repository marks the publication of the software.
The team describes the change as a response to a Web3Auth social login incident. The release notes distinguish accounts covered by recovery from those the project links to the party responsible for the incident. According to the release, the changes do not target other accounts. The stated scope covers Osmosis network rules. It does not establish how affected accounts are treated on other chains.
Two sets of rules for affected accounts
For wallets designated for recovery, the patch preserves the operations needed to release funds that are tied up. Transfers are limited to the recovery address designated by Web3Auth and are subject to the fee payment conditions in the release. The notes set March 31, 2027, at 00:00 UTC as the end of this temporary regime. That deadline concerns the patch restrictions. The document gives no date for when individual users would receive their funds.
Accounts the team links to the party responsible for the incident are subject to a separate freeze. The version blocks transfers, delegation, and certain transaction authorizations for those accounts. The release notes describe which operations the software restricts. They do not report how much has already been returned to users or set an individual repayment schedule. Activation opens the network’s planned recovery process and defines the movements permitted on affected accounts.
Full nodes need to run the same version
The team describes deployment as a binary replacement. It covers validators and other full nodes, including archive nodes and nodes that serve application requests. The notes warn that a node remaining on 32.0.0 can stop when the state it calculates differs from the state produced under the new rules. That can happen at the first block the two versions process differently.
The official repository provides Linux binaries for amd64 and arm64 and container images. The team also publishes checksums for the distributed files. Operators can identify the release that applies the restrictions at the announced block. For affected users, the release documents the technical conditions for recovery and the period during which the rules apply.
