Sui conducted a protocol upgrade on May 20th, 2026, which is now fully supported on Fireblocks.
What changed?
Sui added an account-based model, which now exists alongside the original object-based model.
How does this affect Fireblocks customers?
Incoming transactions
Fireblocks now supports both object-based and account-based incoming transactions.
Outgoing transactions
Outgoing transactions are still sent as objects. This follows guidance from the Sui Foundation to ensure ecosystem readiness for the upgrade and to prevent cases where the receiver does not yet support the account-based model.
AML
With Sui’s upgrade, Fireblocks’ AML process now supports both the legacy object-based model and the new account-based model. The freezing logic now automatically adapts based on how the flagged transaction was constructed:
- Object-based transactions: If a transaction utilizing specific Coin objects is flagged, those specific objects are frozen and remain unspendable, maintaining the original protocol behavior.
- Account-based transactions: If a transaction utilizing the new Address Balance mechanism is flagged, only the specific amount (value) is locked within the address balance.
- Existing frozen assets: All objects currently frozen prior to the upgrade remain locked as specific objects. Since the protocol continues to support the object-based model, there is no impact on customers; these assets stay frozen exactly as they were without requiring any migration or change in status.
By supporting both models simultaneously, Fireblocks ensures that security and compliance are maintained with zero disruption to your existing workflows, regardless of which transaction method you use.