Izzy

8K posts

Izzy banner
Izzy

Izzy

@IsdrsP

Chief of Staking at @LidoFinance

Katılım Mayıs 2020
5.3K Takip Edilen2.7K Takipçiler
Sabitlenmiş Tweet
Izzy
Izzy@IsdrsP·
2025 has been a triumphant year for @LidoFinance, which has broken new ground in both DeFi and TradFi. Lido v3, launching soon, will transform Lido from a “one size fits most” solution into one that offers customizable staking solutions for any need.
English
51
21
170
15.6K
Izzy retweetledi
Wisp
Wisp@usewisp_io·
If you're tired of being the training data, our waitlist is open.
English
0
1
9
257
Izzy retweetledi
cyber•Fund
cyber•Fund@cyberfund·
AGI is 3 years out. Humanity faces a choice: 𝐀𝐜𝐜𝐞𝐥𝐞𝐫𝐚𝐭𝐞 𝐭𝐡𝐞 𝐂𝐲𝐛𝐞𝐫𝐧𝐞𝐭𝐢𝐜 𝐄𝐜𝐨𝐧𝐨𝐦𝐲 𝐨𝐫 𝐀𝐜𝐜𝐞𝐩𝐭 𝐂𝐲𝐛𝐞𝐫𝐬𝐥𝐚𝐯𝐞𝐫𝐲 Today we share our thesis on why a transition from Capitalism to the Cybernetic Economy is inevitable. cyber.fund/content/cyber-…
English
4
24
51
10.7K
Izzy retweetledi
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
Last week Alex Karp said we need to rebuild trust in AI by asking these 5 questions to your LLM provider. So here's @usewisp_io answering them to Alex
English
4
4
20
2.1K
Izzy retweetledi
EthStaker 🦇🔊
EthStaker 🦇🔊@ethStaker·
Next week we'll have Community Call #70 about Operationalizing ePBS for Glamsterdam! We'll hear from a variety of teams across the staking ecosystem (core devs, builders, protocols, guides) to share how ePBS is getting put into action for the upcoming Glamsterdam hard fork and answer any questions. Join us live with Q&A: Wednesday, July 22nd at 15:00 UTC Link below
English
1
2
7
642
Izzy retweetledi
Lido
Lido@LidoFinance·
Integrated Fast Swaps are back in the Lido staking widget. Skip the withdrawal queue and unstake into multiple assets - including ETH, USDC & WBTC - for instant liquidity via @CoWSwap. Native. Seamless. Instant.
English
6
22
99
10.8K
Izzy retweetledi
Hong Kong Ethereum Community Hub
As global finance is experiencing the next wave of technological upgrade via tokenization, evaluating structural efficiency, liquidity frameworks, and institutional readiness becomes paramount. Jointly organized by @BGDA_UK @ethereumhkhub @snzholding #BlockUnion, and co-hosted by @Sharplink @GSR_io @LidoFinance , the Asia Onchain Finance Summit brings together leaders across financial institutions, fintech and decentralized ecosystem to explore how institutional finance is evolving onchain. 📅 July 17, 2026 (Friday) | 14:30 The countdown is on 🇭🇰 Register now: luma.com/izc85bmc Here's a look at the key conversations shaping the programme 👇
English
3
7
27
4.6K
Izzy retweetledi
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
This week we opened up the waitlist for @usewisp_io (verifiably private AI) and people had a lot of questions. I'll answer the most common ones here:
Captain Nemo 🦞 tweet media
English
4
5
37
3K
Izzy retweetledi
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
Sneak peek of @usewisp_io! Forced @ibidino to analyze his cholesterol on screen and show you how to use skills, connectors and more in a fully private manner.
English
8
15
54
6.4K
Izzy retweetledi
Vasiliy Shapovalov
Vasiliy Shapovalov@_vshapovalov·
I'll give a long answer because I'm afraid just saying a short yes would leave some readers with impression that I promised immediate buybacks or something. At current moment: all there is of Wisp is owned by foundations that by bylaws and funding are nailed to Lido DAO with nine inch nails. There's no for profit company anyone on the team has any shares exposure to. This has been set up the right way from the start, which was not a small and easy thing to agree on with the team. Folks are basically founders in residence and letting go of equity structure is no small personal concession. There is a lot of unknowns in the future, e.g. if it's clear that wisp success will require a big fundraise - what's the best way to do this? How does the founding team (just for clarity - doesn't include me) gets upside that is in line with their contribution and dedication to the success? Is Lido brand a useful help beyond early adopters? What if AI regulation continues to expand and become tougher? What should be done if there's a juicy acquisition inquiry? And some of these unknowns might ask for changing the structure above. If so it's going to be handled with a DAO vote, not a fait accompli fundraise.
English
4
4
23
1.2K
Izzy retweetledi
kolsolv
kolsolv@kolsolv·
Getting a lot of questions about how TEEs work in @usewisp_io and why they are the most private way to use AI. Wisp uses TEEs in 2 cases: Wisp Proxy (Anonymizer) and the actual LLM inside @PhalaNetwork with @TinfoilAI as fallback. I'll explain both and how we verify TEEs stay intact: > What is TEE or Trusted Execution Environment? It is a hardware-isolated region inside the CPU/GPU that can't be accessed even by the host's OS, hypervisor or other applications. Wisp runs AI inside TEEs. Your prompts are encrypted on your device before being sent to the LLM that lives inside a hardware-secured chip. Your prompts are only decrypted once inside TEE, where nobody can see them. > How do we know for sure that nobody can see inside TEE? Intel TDX (what Wisp uses), has a dedicated hardware memory-encryption engine in the CPU memory path that encrypts data with a per-VM key as it moves between CPU<>RAM. The key lives inside CPU and is never exposed to software. Not even @PhalaNetwork, which supplies the hardware, can see inside. > Since nobody can see inside, how do we make sure that the code running inside TEE is what we claim it to be, and also that it runs on correct hardware? Before anything leaves your device, the Wisp desktop app asks TEE for an attestation - cryptographic proof that TEE is running *this exact code* on *this exact hardware*. The flow is: 1. Wisp asks TEE to attest, sending a fresh nonce. 2. The TEE returns a quote covering a) a hardware attestation and b) a measurement of the code it booted. 3. Wisp verifies the hardware attestation is signed by Intel - proof it's a genuine, up-to-date TDX chip. 4. Wisp matches the code measurement against the published build: the exact image digest our CI produced from the code. We'll open source it soon, so anyone will be able to rebuild it and check the hash themselves. 5. Any mismatch → Wisp refuses to send a single byte off your device. > Why do you use TEEs and not FHE? FHEs are theoretically the most private option for AI inference because your prompts never get decrypted. In TEE, the prompt arrives encrypted, then the enclave decrypts it because the model has to run inference on plaintext. FHE skips the decryption step, AI hardware computes directly on ciphertext and produces an encrypted answer that only your key can open. Problem is, FHE inference is 10,000x slower atm and still doesn't prove which model ran inference, so you need the attesation anyway. Atm, FHE simply isn't commercially viable for mass market AI. When a more private + performant solution emerges, we'll adopt it. > is TEE 100% secure? Nothing is trust-free (including FHE), but the attack cost is the metric here. TEE Attestation doesn't remove trust - it moves the attack vector from 'insider greps the logs' to 'physically taking over a secure machine' which is substantially more expensive. If you need more info on how Wisp works + sign up to the waitlist, go to usewisp.io
kolsolv tweet media
English
6
8
29
11.4K
Izzy retweetledi
Mippo 🟪
Mippo 🟪@MikeIppolito_·
All roads in crypto right now point back to the brokerages. I think Coinbase, Robinhood, Binance, Kraken, etc... are about to go on an absolutely generational run. DeFi reduces the friction to create financial products, but the products will be sold on those platforms.
English
18
13
184
55.2K
Izzy retweetledi
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
Crossed 500 signups. Good moment to share why we built @usewisp_io in the 1st place. Frontier labs went from lawful neutral to feeding the surveillance industrial complex. Your secrets aren't safe with Sam/Dario, but you might not know why. So I asked Wisp to help me explain:
Captain Nemo 🦞 tweet media
English
5
13
42
4.5K
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
For the past 5 months several unwell people @LidoFinance have been trying to build the most private AI imaginable. Today I'm opening the waitlist. Wisp (@usewisp_io) is the antithesis to Sam and Dario's 'trust me bro' privacy. Architected so no one - even Wisp - can read, train on or retain your data. Waitlist: usewisp.io How it works:
Captain Nemo 🦞 tweet media
English
67
61
371
141.1K
Izzy retweetledi
apoorv.gwei
apoorv.gwei@apoorveth·
Launching skills.eth.sh ✨ One place to find AI-first Web3 resources: - MCPs - CLIs - APIs - Wallets
English
17
13
126
10K
Izzy retweetledi
EthStaker 🦇🔊
EthStaker 🦇🔊@ethStaker·
We'll have @d_gusakov this week in Community Call #69 to talk about EIP-8148: a proposal for Custom Sweep Thresholds for Validators. When: Wednesday July 8, 15:00 UTC Join the YouTube livestream (link to follow) and ask any Q&A there!
English
3
10
26
3.3K
Izzy retweetledi
Captain Nemo 🦞
Captain Nemo 🦞@ncerovac·
244 signups for @usewisp_io already! If you missed it, Wisp is what happens when a bunch of opsec lunatics ask: "what if AI, but obscenely private?" > Desktop app + local agent > 'Cowork' features (folders, skills, connectors), but Dario can't read your logs over dinner > Files and memory encrypted on your device > All profiling requests (e.g. WebSearch) are anonymized > Inference runs inside a hardware-secured enclave that no person can see inside of > Desktop app verifies TEE attestation before anything is sent from your device Design-wise, this is the most private AI can reasonably get atm. Sign up on usewisp.io
Captain Nemo 🦞 tweet media
English
6
6
33
5.5K
Izzy retweetledi
Lido
Lido@LidoFinance·
Staked ETH, meet Robinhood Chain. Your wstETH can now cross over to @RobinhoodCrypto, carrying its Ethereum staking rewards with it and unlocking a new ecosystem to put it to work in. ↓
English
14
18
145
7.3K