We just shipped the biggest update to the Revoke extension ever.
New features, new partner, and a completely overhauled approach to protecting your wallet.
Here’s everything 🧵
Your crypto is not stored in your wallet.
Your wallet stores the keys that give you access.
A simple concept, but one every crypto user needs to understand.
Read more here ⤵
Octant has been an incredible positive force for public goods funding in the crypto space. It was great to meet the team at EthCC and chat about future plans for Revoke. 👀
Why is @RevokeCash so important to our industry?
We spoke to Revoke's founder @RoscoKalis about user safety, crypto adoption, and Octant's role in supporting Revoke's journey.
"Who has access to my wallet?"
Most crypto users do not question this until it is too late.
Token approvals are normal in crypto.
But old, unlimited or forgotten approvals can become a risk when smart contracts get exploited.
Revoke helps you see them and clean them up.
PulseChain support update: after some hiccups with our underlying data APIs, we've managed to fix PulseChain support with the help of the PulseChain community. Stay safe on all chains 🫡
When was the last time you checked who has permission to move your tokens?
Token approvals make DeFi and NFTs seamless, but leaving them open indefinitely leaves a backdoor to your wallet.
Use Revoke to audit your active permissions and reclaim total control.
Once again, we're amazed by the support from our community.
317 individual donors supported Revoke during the @Giveth Ethereum Security Round.
While we're waiting for the final numbers and matching:
We want to say thank you!
Your support keeps fueling our work.
Here's the link to our project in the round with an 500 ETH matching pool for eligible donations.
We appreciate your support! 🫡
qf.giveth.io/project/revoke…
Only 3 days left to support us in the @Giveth Ethereum Security Round.
Support us and our mission to make token approvals disappear from your wallet.
Every donation counts!
In case you were wondering if old approvals will come back to haunt you.
Yes, they totally will.
AurellionLabs suffered an exploit for ~455k, including approved user funds.
🚨SlowMist TI Alert🚨
💸 @Aurellion_Labs Loss: 455,003 USDC (~$455,003)
🔍 Root Cause: Unprotected initialize(address varg0) in SafeOwnable Facet. Diamond set owner via non-initialize path without updating _initialized version slot (bytes 0-7 of 0xf0c57e...) from 0,