Beelon Musk

🌐 What DePIN protocols does Hivello support? We’re building a unified platform for DePIN networks in the space and this is just the beginning. 😎 Proud to support: @ethswarm @Filecoin @AIOZNetwork @MysteriumNet @golemproject @nosana_ai @WithAutonomi @storj @Livepeer @SentinelP2P More integrations are on it's way... 💚

yes, this

@alisher Look for zero-leak metadata tools. I know they are being built.

6. Radical privacy isn’t just technical. It’s spiritual. Political. existential. It’s a world where your inner life remains yours, unless you choose to share it on your own terms. We, and our kids, deserve a world that respects that. That’s why we’re building it.

1. At @web3privacy hackathon I asked @VitalikButerin two questions. - What does radical privacy mean to you? - What is the privacy endgame? Ready for answers? 🧵

Swarm will be there. Many frens.

Zero-leak metadata for Signal

@SchorLukas I would like to understand why are we all dissing EOA because of the UX, when the security is much higher. One privKey across all chains. I understand that @safe is a different beast, but it should fall under the same logic.

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.

Finally got to my first hackathon at @ETHGlobal Built with @ethswarm, @lifiprotocol and @OpenAI a decentralized NFT creator with AI prompts for images. All is hosted on ENS domain and Swarm storage buzz-mint.eth.limo Had great time, highly recommend.

W3PN HACKS hackathon.web3privacy.info We are here to change the game. Thanks to all the supporters helping us champion open innovation: @nillion @FundingCommons @protocollabs @CalimeroNetwork @namada @Rarimo_protocol @ethswarm @ethereumecf @idOS_network @MidnightNtwrk @fhenix @0xHolonym

Viktor unveiling the incentives scheme in ETH Prague

⚡️ P2P Guerrilla Roundtable #5 ⚡️ The peer-to-peer revolution continues - The weekly X Space for those building the decentralized web and freedom tech. 🗓️ Wed @ 12PM EST // 4PM UTC 🎙️ Featuring: @AntonioGonzalo_ from @ethswarm @_PradeepGoel from @Pai3Ai @luciaprotocol 🎙️Join us this week for exciting topics & alpha calls from builders shaping the decentralized web. 🔗 Set a reminder: x.com/i/spaces/1OdJr… Let’s build the internet we deserve 🎏

🏃‍♀️Runner up.

* @zeligf, @ethswarm, will explain how non-local redundancy works in Swarm, including the use of Reed-Solomon erasure codes, cross-neighbourhood redundancy for singleton chunks, and alternative retrieval strategies that impact both latency and cost.

The full line-up of speakers for our meet-up in Prague this month just dropped 🔥 @zeligf x @ethswarm @olkurbatov x @Rarimo_protocol @TMIYChao x @ethereumfndn @vpavlin x @Waku_org @costgallo x Anthropologist Leo Gomez x @Codex_storage @PG_CDG x Web3Privacy Now Join us on for an evening for cypherpunk minds & privacy-first humans 🔒 RSVP in the comments

Maybe Ethereum should be a simple blockchain that does nothing more than verify zk proofs, and the current Ethereum would be an L2 on it. New architecture with maximum simplicity, and you get backward compatibility with the L2. And forget the blobs, there are cool 3rd party solutions like @ethswarm to securely store L2 transaction data.

@DeanEigenmann The desire to grab a piece of the storage market is so intense they couldn't help it. And it's backfiring. ETH is and should be consensus only.

ETH would’ve probably been better off not adding blobs( it would’ve been unlikely that the rollups using ETH move anywhere else anyway but at least they’d have been paying fees. Especially the case considering user activity would’ve just migrated.

@koeppelmann @danfinlay @VitalikButerin Congrats on the update 💃

@koeppelmann @danfinlay @VitalikButerin Couldn’t help but notice Metamask. Based.

After the Gnosis Pectra HF today I just did my first "type 4 tx" - sending @danfinlay and @VitalikButerin 1 xDAI each. This will finally allow to get rid of the annoying pattern that users need to do multiple tx for actions that should be just one! (approve + transfer_from)