
RHCP evangelist - CEO of bangers according to @antoine_ships / Software engineer @kosmik_app / Music: @nowlowstune
dream canteen
Joined July 2017
- Tweets1.7K
- Following243
- Followers98
- Likes4.4K
nowlow retweeted
Dear @pewdiepie,
Thank you for raising awareness about the #deGoogle movement.
Here's our response, hope this is convincing enough for you to give @ProtonMail a try.
Unlike your custom solution, there's not much fiddling to do, and we think you'll enjoy the added features. ✌️
nowlow retweeted
As it turns out, the Protofire team was aware of this edge case for older Safes and white-hat deployed Safes to frontrun a malicious hacker taking advantage of it.
@protofire chads
100 ETH were assumed lost but could eventually be recovered. Here's what happened, how it became a happy ending and what's needed to prevent this from happening again.
Context
A user of Safe{Wallet} wanted to bridge 100 ETH from Mainnet to Base. But then they realized that they can't actually access the funds on the Base. The Safe on Base had a different set of signers than their original Safe, meaning they had no control over it. How can this happen?
Unlike EOAs (Externally Owned Accounts), smart accounts like Safe are governed by deployed smart contract code. It's technically possible to deploy a smart account with the same deployment config (same signers) on different chains at the same address (using counterfactual deployment). So normally bridging to a chain where the smart account is not deployed yet is merely an annoyance as the user first has to deploy the smart account before they can access the bridged funds.
But this case was different. The user used their @Safe smart account since 2020. The smart account version from back then (v1.1.1.) was not yet written with multichain in mind, so it was possible for anyone to deploy a smart account on a different chain with completely a different config at the same address. Something that has been changed since the v.1.2.0. version.
Rescue
Once the Safe team became aware of the incident, @tschubotz took immediate ownership. He examined the Safe on Base and noticed that the address had been deployed by an account that had preemptively deployed many other v1.1.1 Safes on Base.
Through further onchain analysis, the trail led to @protofire. As it turns out, the Protofire team was aware of this edge case for older Safes and white-hat deployed Safes to frontrun a malicious hacker taking advantage of it.
So just two hours after the incident was reported, there was hope that the funds could indeed be recovered. And few minutes later, a first test transaction and then a full transfer of the 100 ETH back to the user could be done.
This is commendable anticipation of @protofire, strong leadership from @tschubotz and fantastic support by the wider @Safe team to get the funds safely back to the user. 💪
Learnings
The root cause was the use of an older Safe version (v1.1.1), which didn’t account for multichain deployments. Since version v1.2.0, Safe includes protections that prevent conflicting deployments across chains by modifying how the CREATE2 salt is constructed.
To bridge, the user chose the native bridge integration which is essentially a @lifiprotocol widget but with some optimizations for smart accounts. For example, the bridging feature warns users explicitly if there is NO code at the destination chain, meaning that no smart contract was deployed there. However, there was no warning in place for there being different code deployed on the destination chain. This additional layer of protection has now been introduced to cover the edge-case for old v.1.1.1. accounts.
The deeper fix lies in improved keystore infrastructure (like keystore rollups) that can guarantee a consistent account config across chains. Until then, deployment behavior will remain difficult to reason about for developers and end-users.
Finally, we are still at a point where users are expected to do test transactions before moving bigger funds. This is not scalable and shouldn't be expected from users. There needs to be more innovation around hooks, guards, and other safety mechanisms that allow strong protections for users.
I'm glad this case could be resolved with a happy end and there is important learnings for wallet developers, especially ones using smart accounts. But it also clearly showed once again that a lot more work is ahead of us to truly make self-custody easy and secure for everyone.
nowlow retweeted
Kosmik is live on @microlaunchHQ 🚀
If you're there please rate us ⭐️⭐️⭐️⭐️⭐️
microlaunch.net/p/kosmik
nowlow retweeted
Click on a tag in the tag panel of any object and start a search to find related objects in all your Kosmik universes.
nowlow retweeted
Text items, images, PDFs—anything should be enough to send your small little computer person crawling the web for you.
The future of the browser → Already available in Kosmik app
nowlow retweeted
What's a browser anyway? No more writer's block, soon on @kosmik_app you'll be able to prompt your universe into existence: images, web pages, videos and pdfs. Any topic. Anytime.
nowlow retweeted
Hello internet,
Today we're sending the first batch of invites to Kosmik 3.0ß, rebuilt from the ground up. New canvas, new database, new UI, new tagging system, workspaces, new browser, it was ENTIRELY rewritten!
nowlow retweeted
Quel honneur de recevoir le grand @JeanJass dans le prochain épisode de BANGR, ça va être fantastique la famille
dispo demain à 18h 🙌
nowlow retweeted
Plus j’y pense plus je me dis que le jour de la mort de JMLP sera aussi celui de la dediabolisation finale du RN.
Vous allez voir qu’on parlera beaucoup plus de « l’indécence des gauchistes de se réjouir de la mort de quelqu’un » que de rappeler à quel point il était raciste
nowlow retweeted
This font is 1px thin and can display any text on the screen! 🤯
msarnoff.org/millitext/
nowlow retweeted
nowlow retweeted
The moon appeared inside the Olympic rings on the Eiffel Tower, which is a violation of the Olympic brand guide 📷: @Olympics
nowlow retweeted
#RappelProduit PISTOLET
Risques : MOURRIR
Motif : PISTOLET
#RappelProduit Arbalète rustique PM bois + 2 flèches - Kalid interiors
Risques : Blessures, Dommage à la vue
Motif : Risque de blessures causé par les projectiles qui ont à la fois une énergie cinétique importante et une surface de contact (...)
rappel.conso.gouv.fr/fiche-r…






























