Sui doesn't have a direct equivalent to EVM's 'revoke cache' or token approvals because of its object-centric model. In Sui, assets are individual objects owned by your address. When you interact with a dapp, you explicitly sign a transaction to send specific objects to that dapp's contract, or to perform an action on objects already held by the contract. Dapps don't gain persistent 'approvals' to access or spend arbitrary assets from your wallet without your explicit, per-transaction signature. Your wallet's security after using dapps on Sui primarily relies on carefully reviewing each transaction you sign to understand what objects are being moved or affected, as there's no lingering 'permission' to revoke later for other assets in your wallet.

After using a dapp, simply disconnect your wallet to ensure security. This is a general safety measure when dealing with decentralized applications. Regarding SUI and Aptos, Suimove is different from Aptos move, and each might have different protocols for security. It's not exactly the same approach, so it's always good to verify how each handles disconnecting wallets.

SUI does not have a tool equivalent to EVM's revoke cache. The Move programming language used by SUI operates differently from EVM. To ensure security, you can disconnect your wallet after using a dapp to remain safe.