
@e330acidi
iAccount based inEurope!
About this account
- Account based in
- Europe
- Connected via
- West Asia Android App
! X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
P057-CRyP704n4rcHY Building with @LidoFinance | Tweets are NFA | DYOR
Bermuda
Joined June 2014
- Tweets6K
- Following716
- Followers408
- Likes24.1K
EM retweeted
"lead and adopt the same changes" in practice.
github.com/paradigmxyz/reth/…
Less than 12h between @Nethermind PR merged and Reth PR opened.
Hard to be unique in AI times - we expected that :)
What matters is who brings the innovation and that should be higlighted.
This might not be widely known, but @Nethermind improvements don’t just benefit our client.
Other clients often follow our lead and adopt the same changes, so we’re raising the performance bar across the entire Ethereum and EVM ecosystem. 👇
EM retweeted
Lido Lend: Security-First Lending
Lido contributors are unveiling the development of ‘Lido Lend’, a new decentralized lending market, designed with a novel set of security-forward safeguards and utilities that benefit both lenders and borrowers.
research.lido.fi/t/unveiling…
EM retweeted
US access to ETH staking via Lido is expanding 🇺🇸
Eligible clients of @BitGo Bank & Trust can now stake ETH and receive stETH through their existing BitGo
account.
Read more: blog.lido.fi/bitgo-extends-l…
Less validators. Same ETH. More efficient Ethereum.
@LidoFinance doing its part. 🫡
down only (this is a good thing!)
865k validators
beaconcha.in/charts/credenti…
EM retweeted
Following last week’s infrastructure investigation, MetaMask Staking has nearly completed processing the exit of its Lido validators without incident. The exited ETH will continue its re-entry to the Lido protocol over the coming weeks. The operator disclosed the issue early and acted quickly, which kept the impact to stETH holders minimal.
As the final set of validators are completing their exits, stETH APR is 2.23% - at or above where it has been since August. stETH rewards come from a diverse set of over 600 independent Node Operators across the Curated and Community Staking Modules, so a precautionary exit by one of the larger operators in the protocol has a limited effect on total rewards. The recent reduction in the Ethereum entry queue also means newly staked ETH starts earning sooner, netting more rewards for all Lido stakers.
MetaMask Staking will publish a comprehensive post-mortem in the coming weeks.
Thanks to the community for your trust and confidence to keep Ethereum staking simple, secure, and decentralized.
Following an investigation into an infrastructure compromise, MetaMask Staking (ex Consensys Staking) has taken precautionary steps to protect client assets related to its operated Ethereum validators.
These steps include exiting its Ethereum (ETH) validators in the Lido protocol, and will likely incur foregone rewards as well as possible downtime penalties should validators be taken offline in the near future to reduce risks related to potential network penalties. Relevant validators have begun the exit process, with the final validators expected to be exited (but not fully withdrawn) by the end of October 7th, 2026.
No action is required from stETH holders. ETH exited from MetaMask Staking-operated validators is expected to return to the protocol gradually as the relevant validators complete the exit, withdrawal, and re-entry cycle, which is estimated to take approximately up to 45 days due to the extended entry queue. As a reminder, staking operations are non-custodial in nature and MetaMask does not manage withdrawal keys for staking on behalf of clients.
As always, the Lido Protocol’s diverse Node Operator set and other security systems including the ad hoc reserve fund (of over 6,750 stETH), are designed to contain and mitigate disruptions to the normal operations of the protocol, in addition to other potential routes.
research.lido.fi/t/security-…
A full investigation is underway, and further updates will be shared as they become available. For further details, please refer to the MetaMask Staking release linked below.
EM retweeted
Just usewisp.io to stay private 🥷
Private AI is going mainstream.
This week, OpenAI introduced Private Intelligence, joining Apple, Google and Meta in building AI systems that keep user data private on their own platforms.
At the same time, Private AI infrastructure is being built for anyone to use, build on, or run on their own servers.
Below is a full market map of the Private AI ecosystem, from silicon to apps.
Full article coming soon.
EM retweeted
I’m very proud to announce the newest member of the Aragon team, Kay!
Kay will be stepping in as our new CTO.
He brings a wealth of experience in smart-contract architecture and development and cybersecurity.
He’s previously worked at Lido & Neutron.
Welcome! 🫡 🦅
EM retweeted
Thanks to Anthropic we can finally try fearbaiting in our marketing too.
GLM-5.3 is available and fully private on Wisp.
EM retweeted
Decentralisation is back on the menu boys.
🚨🚨🚨 the SEC released updated guidance on token buybacks 🚨🚨🚨
it seems there is a decentralization premise here after all
here is the redline
sec.gov/files/frequently-ask…
EM retweeted
every day we're getting closer to the world where the only truly global system would be ethereum
The cryptographic world computer:
vitalik.eth.limo/general/202…
My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties.
FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
EM retweeted
Glamsterdam will bring snap sync to the next level.
With snap v2, the Block-level Access List, which is basically a state diff, is used to replace the traditional healing phase.
The result, it becomes faster and simpler to sync a node.
Clients are ready with Glamsterdam.
Snycing has never been that smooth.
Reminder: you can now sync an ethereum node within half a day and with aggressive settings the space it takes up on disk can be under half a terabyte.
EIP-4444 and hard work by client teams on optimizing snap sync has improved things *a lot*.
Glamsterdam will improve the sync situation further still (eg. Nimbus's new sync protocol uses it)
EM retweeted
Lido contributors are co-hosting the Ethereum Forward Defence Summit with @safe, supported by @ethereumfndn and the Trillion Dollar Security initiative.
Protocol security, OpSec, post-quantum. Workshops, a short set of keynotes, and a focus on building.
November 4th, Mumbai. Five minutes from Devcon.
🏏 Introducing the Ethereum Forward Defence Summit
📅 Nov 4, 2026
📍 MCA Club - Mumbai's iconic cricket club, five minutes from @EFDevcon
venue.
A private summit for the top order defending @ethereum and its protocols: Security researchers, protocol teams, wallet builders, critical infra leaders.
The Agenda:
Forward defence - Accelerating security of @ethereum and its protocols and apps, in the wake of relentless offensive AI. A day full of workshops, keynotes and hands-on building sessions.
Hosted by @safe and @lidofinance. Supported by @ethereumfndn and its trillion dollar security (1TS) initiative.
Seats are limited and strictly by approved application → luma.com/vwmfpmaz
EM retweeted
Oh wow! Definitely a step in the right direction. I'll check how Lido can contribute, as we're paranoid AF when it comes to risk assessment for our products.
🫡🛡️
The @ethereumfndn has awarded cp0x a grant to build an open-source tool for comparing DeFi risk assessments. We are starting work and invite the community to contribute ideas, data, corrections and code here or on github: github.com/cp0x-org/defi-dna
EM retweeted
My good friend @A_Leutenegger always says that access control is the main reason for DeFi hacks. In @LidoFinance we agree with that. This is why we have developed “Execution Delegation Framework”, a tool that meaningfully improves the way your protocol interacts with off-chain actors holding important permissions.
The key idea is simple:
- Hot key is only for execution.
- Hot key is easily disposable and replaceable by the Owner.
- Owner is super secure but used only for hot wallet management.
So you have a hot wallet that you can rotate any moment, and owner that is immutable and very secure. This combination gives you a unique set of properties: governance less routine hot key management, easy access to the hot wallet, top level security control over the permission holder via the owner.
Read more about the basic version of EDF - github.com/ethereum/ERCs/pul…
or dive deeper to learn about Lido-specific implementation that is getting added to the Lido protocol as you read it - research.lido.fi/t/lip-37-ex…
The click-bait doomer posting of "DeFi" being too dangerous yesterday by the founder of one of the biggest security projects in Ethereum is unquestionably the bottom.
83% of exploits are fixable by following best practises on access-control and opsec.
In about 6 months from now there will be standards and hard requirements for projects to validate they are following these best practises to be integrated anywhere.
The fastest projects to do this will get a leg-up on finding institutional liquidity.
Long-term, real DeFi will prevail over CeFi masquerading as DeFi both due to stronger risk assumptions, better margins, and regulatory clearance.
EM retweeted
You may think EIP-8205 is "just for @LidoFinance". But this is not the case!
Check out the comments at Ethereum Magicians on EIP-8205 to see the real importance of this EIP
ethereum-magicians.org/t/eip…
EM retweeted
EIP-8148 solves a real issue in @ethereum staking - fixed 2048 ETH sweep border for 0x02 validators. Professional operators, home stakers, and solo stakers voiced their strong support for it at Ethereum Magicians!
ethereum-magicians.org/t/eip…
EM retweeted
The first mainnet consolidation by @LidoFinance has been submitted. It will be finalized in about 27 hours.
Big day for @ethereum validator count reduction!
beaconcha.in/validator/23649…
A new @LidoFinance Curated Module v2 is live!
- First 0x02 deposits — this week
- First consolidations — Sept 2026
- Last curated validator consolidated — Q1 2027
Massive move for @ethereum!
EM retweeted
Welcome @Cyfrin to the SEAL Certifications program! They’re now undergoing accreditation and taking on certification engagements.
Details on SEAL Certifications:
securityalliance.org/our-wor…
I have just a single checkbox for ai privacy:
- [x] Use wisp usewisp.io/
Your deleted ChatGPT chats aren't actually deleted. They're still in a training pile. Here's how to (actually) keep your chats safe in 2026:
Skip reading this post; read the entire guide instead (for free):
ruben.substack.com/p/privacy
✦ Two mathematicians solved a Millennium Prize problem with Codex. Three weeks later, OpenAI solved it too. Asked if the model learned from their sessions: "Yes. And so does every LLM company."
✦ Data training is ON by default in ChatGPT and Claude. Settings → Privacy → Off.
✦ Never thumbs up/down a chat you wouldn't want a stranger to read. Your feedback goes straight to train the models.
✦ Share any chat = Publish. Google indexed ~100,000 ChatGPT chats in 2025. Delete all the links you created.
The list is much bigger, but it makes it simpler to protect you: ruben.substack.com/p/privacy
✦ Delete doesn't undo training. If your chat was copied (without your name) before you delete, the copy still stays put.
✦ Incognito mode hides the chat from your sidebar. Not from your boss. On Team or Enterprise, the workspace owns the data.
To get the 9 stops your prompt goes through + the 10-step setup, go to: ruben.substack.com/p/privacy
It's literally everything I know about keeping your prompts private.
EM retweeted
I spent last few weeks talking about EIP-8148 with @ethereum core developers. Nerdy talks. Love it!
But now thanks to @george_avs we have an easy to understand explainer!
eip8148.com/































