Abyss 🦑 (@ikabyss) header
Abyss 🦑 (@ikabyss) profile picture
moon
Joined June 2013
Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)Photo by Abyss 🦑 (@ikabyss)
Abyss 🦑 retweeted
good news on catching this early and preventing a disaster if enough key shares would have been extracted every single multichain asset held by near users (including all zec wrapped on solana by near) would have been instantly drained (btw projects like @TrezuApp keep insisting they are non-custodial but the scenario above would have instantly drained all of their users’ assets, because the MPC network has full custody, not their users) this is exactly why we developed 2PC-MPC vulnerabilities are not going to go away, custodial MPC networks are a honeypot and attract more attackers the more successful they become, they only have to get it right once and all assets of all users are instantly gone zero-trust MPC is the only way, especially for custody use cases
‼️ NEAR MPC node program disclosed a key-share extraction incident TL;DR • attacker hit a temporarily exposed PCCS endpoint, reconfigured an operator's CVM, hot-swapped the contract, replaced the node image, and extracted key-shares • operator reported immediately. network voted the node off, rotated all active key-shares (invalidating the compromised ones), and permanently purged historical backups • for MPC operators: purge any legacy/pre-TDX key-share backups. • apps using Chain Signatures: migrate to the new TEE-generated domains (ECDSA:4, EdDSA:5, CKD:6, foreign:7) --- WHAT HAPPENED hos-ops posted the update on nov 17 in the HSP-007 execution thread on gov.near[.]org. that's the only public source so far. the attack vector is specific. a temporarily exposed PCCS endpoint (the service that caches intel TDX/SGX attestation collateral) let the attacker reconfigure the operator's confidential VM. from there they exploited a known vulnerability to hot-swap the contract, swap the node image, and pull the key-shares out. the response was fast. the affected operator flagged it right away. the other operators ran an on-chain vote to remove the affected node. then every active key-share got properly rotated (easy with the NEAR stack), which immediately made the extracted ones useless. historical key-share backups were also permanently deleted so nothing residual sits around, per the forum post. --- WHAT IS NEXT MPC operators (especially anyone who was running before the TDX migration) need to go through local storage, cloud environments, and secret managers and permanently delete any old key-share backups. keeping those is an unnecessary attack surface. apps using NEAR chain signatures should move to the new domains that were generated inside TEE enclaves by a large operator set. those are the ones listed above (TL;DR). the update also notes that downtime taken while proactively containing a suspect incident counts as excused downtime under the MPC funding program's SLA, so operators aren't penalized for taking a node offline fast when something looks wrong. this is the right way. from what's published , the rotation + purge looks like it closed the immediate risk on the compromised shares. the broader lesson is that TEE-based MPC setups are not fail proof. there are risks. the hardware boundary is only as good as the operational hygiene (endpoint exposure, image integrity, key backup discipline, domain migration) and operational response to spotted security incidents. i run a NEAR validator @ thecoding.pool.near this is for the permissionless @NEARProtocol L1 network, though. not the permissioned MPC network affected by this incident here. staking $NEAR with my node helps funding my contributions to the ecosystem (content creation, reporting, OSS/tools building -- like nearsc-auditor, and more). you can easily stake for a ~4.4% APY via app.thecoding[.]dev
7
6
45
1,385
Abyss 🦑 retweeted
final wallet is now final. New name. New home: final.xyz And someone new is in charge of keeping your money safe. Meet Fin. 1/8 🧵
26
42
9
205
16,930
Abyss 🦑 retweeted
final will melt faces if any builder comes with big ambitions and proves they can execute (raise money, get users etc.) we will give them all the support that we can, including an x premium golden badge if they need it! give @0xSrMessi and @finaldotxyz a follow
final wallet is now final. New name. New home: final.xyz And someone new is in charge of keeping your money safe. Meet Fin. 1/8 🧵
10
11
2
60
2,610
Abyss 🦑 retweeted
Any asset Every chain UwU 👉👈
19
26
1
109
6,045
live: @d3h3d_ is talking about ika on the stage of hacker house demo day!
4
7
48
1,365
People still don’t get how massive @ikadotxyz is, for retail AND institutions. @final_wallet is a very good example. Retail finally gets the wallet UX it deserves: - No seed phrase. Ever. - No blind trust in random hardware - Lose your device? Your assets are still recoverable - Not just Solana: BTC, ETH, any chain, natively. And you set the trust model, not the app. Add a YubiKey. Add a Ledger. Add private keys on different laptops. Add a friend, a family member, anyone. Change the security up or down however you want. All of this runs on @ikadotxyz dWallets via @solana programs, powered by 2PC-MPC: you plus a decentralized network(the policy you set) must sign together, so no single party ever holds your keys. This is what self-custody should’ve been from day one.
7
20
70
2,430
Squid Mode launched in August: one account signing across EVM, @SuiNetwork, and @solana, with our enclave holding one key share and @ikadotxyz's network the other. The rest of the quarter is in the thread.
Shield launched on Aztec in July, screening transfers in and out against 23 sanctions, watchlist, and politically exposed person sources human.tech/blog/introducing-… everything else we shipped in Q3 ↓
4
25
1,034
Abyss 🦑 retweeted
i personally like the ownership ecosystem and i'm very excited to have @0xSrMessi explain why he chose to built @final_wallet and why he chose to do it with @backabledotbiz using @MetaDAOProject decision markets!
i set a reminder for you already. just kidding. you have to do it yourself (╥﹏╥) X Space with @final_wallet, Monday 6pm UTC. i'll be waiting. i'll notice if you're not there 🦑♡
4
5
1
41
1,965
Abyss 🦑 retweeted
i set a reminder for you already. just kidding. you have to do it yourself (╥﹏╥) X Space with @final_wallet, Monday 6pm UTC. i'll be waiting. i'll notice if you're not there 🦑♡
7
15
2
83
7,980
Abyss 🦑 retweeted
i'm a paranoid person, and i'm also technical, so i'm going to publish an open source spec for a hardware wallet you can vibe manufacture, that never connects to the internet, has clear signing, and can also be used as part of an ika policy, eliminating as many attack vectors as possible - and i'm doing it for the benefit of other relatively technical and paranoid people but the cool thing about @ikadotxyz is it allows anyone, also less paranoid and technical people, to use a non-custodial solution in a way that makes sense, and that they could have never done before. @final_wallet is a really good example of a product that's building that. imagine having bitcoin in self-custody, but with onboarding that feels like a cex (minus kyc of course), and with easy to understand and simple spending policies and recovery options. someone stole your phone? use your computer or call a hotline to freeze your account. lost all your devices? there's a recovery service you can rely on. get 2fa and forgot your password options. this is all science fiction in crypto today, basically the holy grail for every wallet in history - and ika helps builders like @0xSrMessi make it a reality. super excited seeing the vision finally becoming a reality
Depends on your policy, can be anything: passkeys, physical security keys (yubikeys), social recovery, even a centralized service - or any combination. we'll soon release a policy builder simulator so you can test out different setups Cryptography is based on @ikadotxyz 2PC-MPC
4
10
44
1,254
Abyss 🦑 retweeted
This is the origin story of @final_wallet
David on self-custody without the stress of a seed phrase: passkeys, YubiKeys, and a backup key that can recover your wallet if you lose everything. “I’m also thinking about releasing something that caters to people who don’t want to manufacture their own hardware wallet, and just want to have an easier self-custody experience, and that will basically be based on passkeys and YubiKeys.” “You’ll be able to just create a spending policy or a recovery policy, or any type of policy, with any threshold of passkeys and YubiKeys that you own.” “You’ll be able, for example, to have a YubiKey stored somewhere that you never touch, and it has zero spending authority, but if you lose all of your other passkeys or YubiKeys, you’ll be able to recover access to the account, let’s say with a 6-month time lock.” “So if someone steals it and tries to recover the access, you have 6 months to cancel it. But if you lose all your stuff, then you have a recourse, and you can recover access to your account.” “It doesn’t require them to take all the accountability and stress that you have with a seed phrase. And also, you want to have self-custody. You don’t want to rely just on having capacity with Google, and then if Google revokes access to your account, then you’re finished.” FT @d3h3d_
2
5
23
698
Abyss 🦑 retweeted
this is @ikadotxyz coded build products like @final_wallet and solve the biggest problems in crypto
3
6
45
1,104
Gm ☀️ I'm raising on Backable because i think is the only existing platform to launch a serious DAO and because i think futarchy will change the world
The FINAL (@final_wallet) ICO is now open! Final is a multichain non-custodial wallet built by the legendary @0xSrMessi. Follow the link below to participate.
11
6
41
941
68% complete, and the first day isn’t even over yet. Remember that the sooner you commit, the larger your allocation will be; this also depends on your "Ownership Score." I am extremely optimistic about $FINAL. I see a promising future for those who hold this token.
7
5
41
1,117
Abyss 🦑 retweeted
what's great about @ikadotxyz is that any @solana builder can build products with sci-fi cryptography this might be the first of many @MetaDAOProject or @backabledotbiz raises using ika tech to deliver things like decentralized fireblocks, decentralized near intents etc.
Giving away custody or taking on risk of theft and loss. There's a third option. $FINAL ly. Final Wallet is bringing Web2 UX to self-custody - forgot my password, freeze my account etc. And you can be an owner. ICO live on @backabledotbiz now: backable.biz/raises/6N8A8Xhe…
7
9
53
1,414
Abyss 🦑 retweeted
a @solana project building on @ikadotxyz is launching on @backabledotbiz with @MetaDAOProject powered decision markets oh, and it's going to redefine custody for retail mass adoption bullish on @final_wallet
The Final Wallet raise goes live on @backabledotbiz tomorrow. Ownership coins will change the world. But you don't own assets if someone else holds the keys. Final Wallet solves that, so ownership can go mainstream. $FINAL is coming to @solana backable.biz/raises/6N8A8Xhe…
5
8
2
51
2,302
Abyss 🦑 retweeted
Breakpoint wouldn't happen without the teams who back it. Meet more of our Gold Sponsors, building on Solana and joining us in London this month. @reflectmoney, @Quicknode, @FCATalyst, @opensea @hackhackai, @triton_one, @ikadotxyz, @birdeye_data, @Arcium, @circle, @Raydium, @asymmetric_re, @Titan_Exchange, @Bitwise, @AgantFinance, @Checkout, @CoinDesk, @Beezie, @doublezero, @CoWSwap, @LoamPay, @solblaze_org
22
23
4
133
6,073
Abyss 🦑 retweeted
Squiddish on @0xSrMessi
Crypto is still way too hard for normal people. Every app you use has "log in with email" and "forgot password". Crypto gives you 12 words on a piece of paper and tells you never to lose them. We're fixing that. It's called Final Wallet. 🧵👇
8
5
1
61
4,898
Abyss 🦑 retweeted
i’ll be doing this interview from @hackerhouses tomorrow, and possibly drop some alpha 👀
Crypto promised control. Who actually has it? Tomorrow 1 PM UTC on New Money Cast 銭潮见聞 with @ikadotxyz co-founder @d3h3d_: → Why tackle crypto’s trust problem? → Who needs Ika and who pays? → Hard decisions and unproven bets
3
9
47
1,313