Sergei Vorobev

@ethereanbull @0xzak Maybe @KeystoneWallet ?

@0xzak build me a hardware wallet with a iphone screen

bought a hardware wallet to verify transactions before signing them. to use the industry standard multisig i have to go into device settings and explicitly disable transaction verification. i am paying for security so i can turn it off. you set up 5 signers with offline key storage, airgapped ceremony, timelocked execution, the whole production. then every single one of them clicks approve on a hash they can't read because EIP-712 calldata doesn't fit on a 2 inch screen. billions of dollars in crypto treasuries secured by "does this browser tab look right to you" sometimes this industry just feels like a complete joke

@Ledger @Ledger The main point is: don't block send tx if your device isn't updated. This is extremely inconvenient when speed is important. It also makes you lose confidence in your wallet. Now I'm not sure my funds are always at hand; I have to set aside 5-10m for updates every time

Hi @vorobev_sa, we appreciate your feedback. Firmware updates are critical to maintaining Ledger’s top-tier security. Every update ensures that your device is protected against the latest threats. Ledger’s firmware is rigorously tested to prevent issues during updates, and our Secure Element ensures that no matter what happens, your private keys are never at risk. If you've had trouble with an update, you can find a full guide to troubleshooting here: support.ledger.com/article/360003… For official support, please connect with us directly: support.ledger.com/contact-us Always remember: Ledger will never call, DM, or ask for your 24-word recovery phrase. If someone does, it's a scam. Stay cautious, keep your crypto safe and always Clear Sign transactions where possible.

@Ledger your core product is a wallet. Its main job is simple: store and move user funds. So why restrict basic functionality if the firmware isn’t updated? Right now the UX is bad: update or you can’t transact. A wallet should never put access to funds behind a forced update.

@cryptograsi The main problem is that updating your device first isn't always convenient in all situations. I believe the software should be backwards compatible so you can always send a transaction and only then update your wallet when it's convenient.

@HarrisBell @chainlink @ensdomains I believe that full support for off-chain resolvers—provided by wallets—will be a crucial step in promoting ENS. This will allow most users to obtain ENS names and encourage CEXs to adopt ENS. If you can influence that, that would be great.

After an incredible chapter working on @chainlink, I’ve been reflecting on the people I met across the team, partners, and broader community. Grateful to everyone who made it such a great ride. For my next chapter, I’m excited to share that I’ve joined ENS Labs as Product Marketing Lead to help advance @ensdomains. I remember getting my first .eth in 2023. For me it was a lightbulb moment for how much easier onchain transactions could be. As I learned more, I realized human-readable identity is essential infrastructure for bringing the next wave of users onchain. Looking forward to connecting with the ENS community and ecosystem partners as I ramp up!

@Ledger Security updates matter — no doubt. But there are many situations where a user must send a transaction immediately and has no time — or safe environment — to perform a firmware update. Self-custody tools should prioritize access to funds first, updates second.

@mageeclegg If you haven't been there yet, you should definitely visit Mendoza.

In 2017 I left the US 🇺🇸 for Latin America… Went straight to Buenos Aires 🇦🇷. Then I rented an Airbnb in Palermo Hollywood… It had a great rooftop pool overlooking the city. (Photo below.) I spent the next year eating obscene amounts of Argentine steak… Drinking Malbec at my favorite wine bar, “Hache Almacén.” And trying to learn Spanish. Can’t believe I’m fluent now. Sometimes I look back at this photo and think… That rooftop was the beginning of an entirely different life. I wouldn’t trade the last decade for anything in the world.

How decentralized is #Web3 — really? Not the blockchain layer. The web layer. Most #dApps still rely on centralized frontends, hosted on traditional infrastructure, behind DNS and cloud providers. Crypto may be the internet of money — but where is the truly decentralized web?

Congratulations! A new home, new people, new projects.

@BowTiedMara This would be amazing news if @crecimientoar coworking space hadn't closed down just before (right after DevConnect). In fact, it's a return to status quo, but now with #etherium support. But it's still great news. Thanks - @VitalikButerin

Ethereum Lands in Buenos Aires and Aims to Create Its Own “Silicon Valley” Effereum will open its own 300 m² offices in IRSA's new Workplace at Polo Dot, located at the intersection of General Paz and Panamericana. Vitalik Buterin, the creator of Ethereum, is driving the project with a team of 70 professionals who will seek to generate synergies with its “neighbors” Mercado Libre and fintechs such as Pomelo, Cashea, Geopagos, and Ripio. Why Argentina? Crypto adoption in the country is structural and not solely dependent on the price of Bitcoin. The record 17,000 attendees at the global cryptocurrency fair in Argentina confirmed that Argentina not only consumes crypto but also develops infrastructure. About Workplace Workplace by IRSA operates under the concept of a “5-star business club,” designed specifically for high-growth technology and digital companies. It currently houses over 2,000 professionals and fosters collaboration between startups, scaleups, and established companies. See the new offices here: maps.app.goo.gl/WADNA1VcBWMqNh…

@FlynnTheMaestro @joe4deadcat @cosmoslabs_io There is an answer, and the question is not about courage but about the system—the current system does not motivate users to vote—this has been shifted to validators, but validators also have no motivation to vote.

@joe4deadcat @cosmoslabs_io Magmar doesn't have the cohones to answer for anything that's gone wrong. Complete and total lack of respect. But what do you expect from unaccountable people?

More blame thrown at @cosmoslabs_io This time a complete failure of IBC’s internal bridging system…which is like living in an apartment building that has no running water.

@KleomedesDAO @joe4deadcat @cosmoslabs_io The same situation occurred with our network, HAQQ Network, proposals 1019 and 1020... this is not an isolated case, but a pattern.

@joe4deadcat @cosmoslabs_io This is just the Bostrom client, but the point stands.

@JeremyParish69 @CosmosEcosystem This feels like a half-measure. In my view, it’s worth thinking more seriously about validator/user incentives to participate in governance — or even introducing penalties for non-voting. Some countries, like Argentina, already use compulsory voting frameworks.

@CosmosEcosystem Time to reduce quorum requirement

One more sad news... Cosmos Hub is no longer able to function as a Hub The proposal to recover the IBC-client failed solely because a quorum was not reached Only 36.61% of the minimum required 40% voted in favor of the proposal This means that networks connected to Cosmos Hub via IBC-relays no longer have the assurance that the connection will be restored in the event of a failure, which could lead to users' tokens becoming permanently stuck in another network, further reducing the use of Cosmos Hub as a Hub Since @cosmoslabs has assumed responsibility for managing Cosmos Hub, the blame for what is happening can be placed solely on them They are failing in their "leadership" responsibilities and are unable to motivate validators to vote on technical proposals What are they doing? They are selling their face, but it’s a pity this doesn’t affect the price of $ATOM

@CosmosEcosystem At HAQQ, we encountered the same problem (IBC) with @cosmoshub proposals 1019, which also failed, and 1020, which miraculously passed because we wrote to all validators asking them to vote however they wanted, but vote... It looks like this is a systemic problem. @0xMagmar fyi

@AirdropGlideApp What happened with @stride_zone ? Why do you think it winddown?

Please don't try to tell me Osmosis is still being actively developed, when the sidebar contains direct links to Apps that are in winddown. And the page to add liquidity to Pool still looks like this: Heck, I think everything on the Earn page has been sunsetted: The Apps page, most of them have closed: Any clarification @osmosis? Are you still there?

@jelena_noble @pls_giveup @jelena_noble I apologize if I didn't express myself clearly. What I mean is, what decentralized bridges do you plan to use on the new network? Or will you also use IBC via Eureca on the new network?

@vorobev_sa @pls_giveup We will continue to support IBC per our blog post.

Noble’s departure is neither something to celebrate nor something to mourn. However, from a technical standpoint, I still don’t fully understand why they felt compelled to move away from the Cosmos SDK. Isn’t it already possible to build a standalone EVM chain using the Cosmos SDK today? @jelena_noble @0xMagmar

@jelena_noble @pls_giveup @jelena_noble Performance is great, but connectivity is the real challenge. Cosmos has IBC, Ethereum has a unified L2 interface. For a new standalone L1, decentralized bridges - become the main bottleneck in UX and latency. Which decentralized bridges are you planning to use?

We decided to move away from the Cosmos tech stack for a few reasons. First, we have a lot of respect for Tendermint/CometBFT and are grateful for how well it has powered Noble to date. That said, consensus research has moved forward significantly, and adopting Simplex (via Commonware) lets us stay at the forefront of that innovation while preserving the security and finality guarantees we’re accustomed to. We’re deliberately optimizing for next-generation consensus research and implementations, and Simplex (2023) aligns better with where we want to be long-term than Tendermint (2010) like algorithms. Simplex preserves instant finality under the same ≥2/3 honest-stake assumption as Tendermint, but achieves it with a simpler, more efficient consensus core. It reduces round complexity, avoids leader churn and timeouts in the common case, and is designed for higher throughput and lower latency, especially under stable network conditions. Second, while Cosmos EVM is a meaningful step in the right direction, integrating the EVM directly via a battle-tested execution client like Reth gives us substantially more flexibility and control over the execution layer than is practical within the Cosmos SDK today. Hope that makes sense.

@0xMagmar The most critical factor for users is CEX support. DEX won’t be the bottleneck, but native bridging to other ecosystems and real usage beyond Cosmos will be essential. From a pragmatic standpoint, the optimal path may be to work directly with @circle.

Noble leaving Cosmos = likely finally time for the Cosmos Hub to have its own USDC!

@francescoswiss @MetaMask @MetaMaskSupport @MetaMaskDev @francescoswiss Thanks for checking with the team — appreciate it. Just following up to see if there are any updates or initial thoughts you can share.

@vorobev_sa @MetaMask @MetaMaskSupport @MetaMaskDev Checking with team

@MetaMask why is ENS Offchain Resolver supported in the browser extension wallet but not in the mobile app? This creates an inconsistent ENS experience across platforms. Any plans to align mobile support? @MetaMaskSupport @MetaMaskDev @francescoswiss