soup retweeted
Replying to @DOGElonMusk420 @larry0x
Yeah. We invented a new scheme called 2pc-mpc, which lets you keep absolute control over your funds (if no one steals your key, no one can steal your coin), whilst allowing an external decentralized network called Ika check every message you sign against a policy (smart contract) before signing.
This way, even if someone would have stolen the user key like the trust wallet hack, Ika wouldn’t have signed the transaction if the policy doesn’t approve.
Its very easy to define policies for what transactions are suspicious or anomalies and block them, or require extra confirmations (eg, if you want to withdraw all funds to a non-white listed address, you need an approval from a hardware wallet / Google Authenticator / Gmail whatever you want).
This lets you have the flexibility of a hot wallets without the associated security risks
soup retweeted
Replying to @austincampbell
True, and imagine that if it was using dWallets on @ikadotxyz , the attack wouldn’t have been possible, even if the attacker has stolen the seed phrase.
That’s my motivation for building it in the first place, allowing end-users to have access to MPC enforced policies, in a decentralised zero-trust way.
soup retweeted
building for scale determines the winner
building for scale can’t be an afterthought, can’t be something you’ll eventually get to, and can’t be a “fake it till you make it” kind of thing
@solana proved that you have to be obsessed with building for scale from day 1, even when you have zero activity, because that’s the only long term plan. it’s also one of the main reasons ethereum has not only lost their 5 year head start to solana, but also don’t look like they can to catch up at this point
and it’s even more critical to build for scale from day 1 with cryptography, because cryptographic systems have hard limits and structural constraints that cannot be coded away with clever engineering
—————
we at @ikadotxyz have been obsessed with scale in a way that seems almost delusional, especially when considering the limitations of what used to be the state of the art threshold signature mpc tech before ika (at first thorchain and then icp)
our end goals around scale are assuming the entire world will run on crypto rails, and in that world, we will own (almost) all of the world’s accounts, and we will process (almost) all of the world’s transactional volume. that means billions of accounts (actual accounts! not derived addresses!), tens or even hundreds of thousands of signatures per second, blazing fast latency to be compatible with all use cases, and super low cost.
anyone familiar with the previously available threshold signature mpc tech and reads the above requirements will view it as delusional, and when adding to that both a massively decentralized network and zero-trust guarantees for the user, it just sounds like the ravings of a lunatic. and many cryptographers told us what we wanted to achieve was just impossible.
—————
imagine us in 2022 looking at a world where the state of the art pushing threshold signatures to the absolute limit was thorchain with:
- max 20 parties
- operating a single account
- no user participation
- 1 signature per second
- over 10s latency
and then deciding we’re going to build a system with hundreds of parties operating billions of accounts with user participation, sub second latency and tens of thousands of signatures per second
now imagine us actually building it. spending over 2 years purely doing cryptography research, achieving breakthrough after breakthrough, redefining everything that was thought possible. not compromising on anything and eliminating tradeoffs completely. and still never stopping, not even now, that we already launched tech that’s 100x everything else that exists, because there’s still more work to do before our scale can reach our end goals. we shipped 2pc-mpc v1, v2, v3 and are working on v4 and v5.
—————
i have heard that some people take offense when i say that other systems like near and icp and lit are legacy mpc solutions. but it is not meant as a dig, the leap ika delivered in threshold signatures, specifically in the context of a decentralized network, is not only orders of magnitudes better across all parameters, it’s also the only way to scale.
that is the very definition of something that makes previous technology legacy, not how long it was on the market. mp3 players made the sony mini-disc tech legacy pretty fast because it couldn’t compete on any level. it doesn’t mean it wasn’t great (i loved my mini-disc) it was just made legacy by something that was categorically better across the board.
—————
custody and interoperability are some of the last and largest unsolved problems of crypto, they are preventing mass adoption and are forcing the industry to be held hostage by trusted 3rd parties, the exact problem crypto was born to solve.
proof of concepts don’t have to be built for scale. they might even get traction. but they just can’t win.
and ika will win these categories because we have been obsessed with scale from day 1
soup retweeted
.@humntech had 2.2 million users and 34.5 million credentials before touching @SuiNetwork
They acquired Gitcoin Passport.
Distributed $225M in grants and airdrops.
Bootstrapped their network on EigenLayer with $3B in restaked security.
They were as Ethereum-native as it gets.
@humntech is now migrating its 2PC signing layer for its Wallet-as-a-Protocol to Ika's decentralized 2PC-MPC network.
Why?
Because @ikadotxyz's infrastructure on Sui let them decentralize wallet security in a way Ethereum couldn't.
That's not an ecosystem product.
That's an established project with millions of existing users choosing @SuiNetwork THROUGH @ikadotxyz because the tech is better for what they're building.
I hope you got a bit enlightened today @Ikh011. You're welcome!!
soup retweeted
I can’t overstate how easily nation state actors can hack any web3 project.
We even showed that with super low resources in-house with 0d.
Even small teams of NSO-level hackers can likely gain control over entire networks with months of works, and I’m saying that from first-level knowledge given my background.
This is why it was super important for us to create Ika such that there’s a cryptographic guarantee that, even given the entire network is compromised on the event of such hack, the user’s funds will not be.
2pc-mpc is unbreakable in that sense
It is mathematically proven:
Ika is undeniable
a remote code execution vulnerability that was publicly disclosed was exploited by (probably) chinese nation state actors in the past hours. one of the victims was pumpkin, with the old vaults that required providing the private key, and those wallets got drained - the exact scenario i warned could happen a few months ago
when i publicly call out and warn users about custodial solutions, like beep and like pumpkin, and highlight the very real risks they create, i get SO MUCH SHIT FOR IT, not only on twitter but also in dms, that you just won’t believe. i am told they’re really good solutions and make users money, or that investors are lining up to invest in them so they must be doing something right, and I’m just spreading fud and being negative and that i’m harming sui and harming ika and i should stop.
there’s literally only one way forward for crypto and it keeps being proved to us over and over and over
Zero-trust
Usability
Decentralization
ZUD is the end game and @ikadotxyz is the path there
soup retweeted
since the dawn of crypto they’ve been trying to convince you the solution for custody and interoperability is trusting 3rd parties
they’re still trying to convince you
satoshi was saying all along what @ikadotxyz is saying
zero-trust cryptography
soup retweeted
crypto’s has a major catch-22 paradox
the only reason to choose crypto over faster cheaper centralized alternatives is removing trust in 3rd parties
so
not your keys not your coins
but
self-custody creates usability challenges that prevent mass adoption
so
trusted 3rd parties (custodians, exchanges, wallet as a service) are used to abstract those difficulties
but
the only reason to use crypto over faster cheaper centralized alternatives is removing trust in 3rd parties…
no one could solve this. until now.
zero-trust custody and interoperability with @ikadotxyz is the only way to break the cycle
no ika, no mass adoption
soup retweeted
WaaP is coming ✦
After laying the foundations for wallets and identity with @humntech, we're ready to ship
Wallet as a Protocol is the answer to blind signing, forced fees, and fragmented wallets
Official launch during WalletCon by @reown_
Wallet infra is evolving - and @0xHolonym is helping shape what’s next.
As a WalletCon partner, they’re introducing WaaP (Wallet-as-a-Protocol) - a free, composable framework rethinking wallets as secure, interoperable layers for the onchain world.
soup retweeted
have you seen this cool deal between @officialSUIG and @bluefinapp?
teapawt.net/officialSUIG/status/19…
now imagine it's an on-chain contract, instead of an off-chain paper deal
the "revenue stream marketplace" rfp describes a protocol enforcing these type of deals for any on-chain revenue generating project on any network - dexes, l2s, liquid staking, you name it
@ikadotxyz solves that
and btw, the @0xbeepit use case is a great example for one of our rfps that i discuss here:
ai agent access control framework
when you hear the vision of a beautiful and magical ai agent economy, you should always ask "who is holding the funds?"
@ikadotxyz solves that
soup retweeted
Once the larger market finally understands what IKA is building, there will be no “dip” to catch.
But one thing I’d strongly suggest: @illuminfti and @ikadotxyz should start posting more clearly about what they actually are not in a super technical way, but in a way the average user can grasp.
soup retweeted
Another project building aggressively on @ikadotxyz 🦑 to unlock users and use-cases.
soup retweeted
I am so bullish on sui and ika that i bet mine and @apeapesui entire business on their success.
its never a good idea to bet against the best tech stack in crypto
soup retweeted
i am so bullish on sui that i bet my entire business on it’s success
it’s never a good idea to bet against the best tech stack in crypto
soup retweeted
Understanding the #IKA Network: How 2PC-MPC Technology is Revolutionizing Blockchain Interoperability // Claude Opus 4.1
Introduction: The Challenge of True Blockchain Interoperability
In the rapidly evolving world of Web3, one challenge has persistently stood in the way of mass adoption: how can we enable seamless, secure interactions across different blockchain networks without sacrificing decentralization? The IKA network @ikadotxyz from dWallet Labs @dWalletLabs presents a groundbreaking solution to this problem through its innovative 2PC-MPC technology. But to truly understand why this technology is revolutionary, we need to start with the fundamentals.
Part 1: Digital Signatures in Blockchain – The Foundation of Trust
What Makes Digital Signatures Essential?
Think of a digital signature as your unforgeable proof of identity and consent in the blockchain world. Just as your handwritten signature authorizes a check, a digital signature proves that you, and only you, authorized a blockchain transaction. However, unlike a physical signature that can be copied or forged, digital signatures use mathematical principles that make them virtually impossible to fake.
In blockchain systems, every user has a pair of cryptographic keys: a private key (kept secret) and a public key (shared openly). Your blockchain address is derived from your public key, while your private key is like the master password that controls everything at that address. When you want to send cryptocurrency or interact with a smart contract, you use your private key to create a digital signature that proves you authorized the transaction.
The Mathematical Magic Behind Signatures
The process works through a clever mathematical relationship. When you sign a transaction with your private key, you create a unique signature that anyone can verify using your public key. The beauty of this system is asymmetric: while anyone can verify your signature is authentic using your public key, only someone with the private key could have created it. This creates a trustless system where mathematical proof replaces the need for trusted intermediaries.
Traditional blockchain wallets give you complete control over your private key, which sounds ideal but creates significant problems. If you lose your private key, your assets are gone forever. If someone steals it, they have complete control over your funds. And perhaps most limiting: your private key only works on one blockchain. You can't use your Bitcoin private key to control assets on Ethereum or Solana.
Part 2: Enter MPC – Distributing Trust Without Losing Control
Understanding Multi-Party Computation in Context
Multi-Party Computation, or MPC, represents a paradigm shift in how we think about cryptographic operations. Instead of having one private key that creates signatures, MPC splits this capability across multiple parties. Imagine if, instead of having one key to your house, you had a special lock that required multiple people to turn their individual key pieces simultaneously to open the door.
In the blockchain context, MPC allows multiple parties to collectively compute a digital signature without any single party ever possessing the complete private key. Each party holds a "share" of the key, and a predetermined threshold of parties must cooperate to generate a valid signature. For example, in a 3-of-5 MPC setup, any three of the five parties can work together to create a signature, but two or fewer cannot.
The Traditional MPC Limitation
While MPC solves some problems, traditional implementations have faced significant limitations. Most existing MPC networks can only handle 4-8 nodes efficiently, creating a tension between security and performance. They're also typically slow, taking 30 seconds or more to generate a signature. Perhaps most critically, traditional MPC systems often require users to trust the network completely, essentially trading one form of centralization for another.
This is where the IKA network's innovation becomes transformative.
Part 3: The 2PC-MPC Breakthrough – Best of Both Worlds
The Nested Architecture Revolution
The 2PC-MPC protocol can be thought of as a "nested" MPC, where a user and a network are always required to generate a signature. The "2PC" stands for two-party computation between the user and the network, while the network's participation is managed through an MPC process between hundreds of nodes.
Think of it like a sophisticated safety deposit box system. Traditional systems either give you sole control (risky if you lose your key) or give the bank control (risky if the bank acts maliciously). The 2PC-MPC system creates a box that requires both your key AND agreement from a decentralized network of validators to open. Neither you alone nor the network alone can access the contents.
How the Split Actually Works
When you create a dWallet (the fundamental building block powered by 2PC-MPC), the system generates cryptographic key shares through a process called Distributed Key Generation (DKG). During this process, both a user share and a network share are created, with the network share encrypted by a network decryption key used as part of the protocol.
Here's where it gets interesting: The protocol ensures non-collusivity, meaning the user is always required to participate in generating a signature, but it also allows the network to be completely autonomous and flexible. When you want to sign a transaction, you initiate the process with your key share. The network validators then engage in their own MPC protocol, where a threshold (typically two-thirds) must agree to co-sign. The final signature is only produced when both conditions are met: you've provided your share, and the required threshold of network validators have provided theirs.
Performance at Scale
Unlike traditional MPC solutions that support only 4-8 nodes and require 30+ second signature times, IKA scales to hundreds or even thousands of nodes while achieving sub-second signature generation. The protocol exhibits superior performance with linear scaling in communication (O(n)) and through novel aggregation techniques, achieves an amortized cost per-party that remains practically constant even with thousands of participants.
Part 4: Enabling Revolutionary Custody and Interoperability Solutions
True Zero-Trust Security
The term "zero-trust" gets thrown around frequently in technology, but the IKA network genuinely achieves it. dWallets utilize the 2PC-MPC protocol where the user is always cryptographically required to generate a signature, eliminating the risk of trusted third parties that can be hacked or act maliciously.
This architecture solves what dWallet Labs calls the "Sovereignty Problem" and the "Honeypot Problem." The Sovereignty Problem refers to users having to give up control of their assets to bridges or custodians. The Honeypot Problem describes how traditional bridges become attractive targets for hackers because they hold large amounts of funds in centralized or semi-centralized control.
Native Multi-Chain Interoperability
Perhaps the most groundbreaking aspect of the IKA network is how it enables true cross-chain functionality. dWallets are programmable and transferable signing mechanisms with addresses on any blockchain that can sign transactions to those networks. This means a smart contract on Sui (where IKA is natively integrated) can control Bitcoin, Ethereum, Solana, or any other blockchain that uses standard signature schemes.
Consider the implications: You could have a single smart contract on Sui that manages a portfolio across Bitcoin, Ethereum, and Solana, executing complex DeFi strategies without ever using a bridge. The assets never leave their native chains, eliminating bridge risk entirely. This technology enables DeFi super apps built on Sui that manage liquidity across multiple chains while maintaining zero-trust security.
Programmable Control Without Compromising Security
Traditional approaches to cross-chain interactions force an impossible choice: maintain security by keeping assets in simple wallets with no programmability, or sacrifice security by sending assets through bridges to access smart contract functionality. The IKA network eliminates this dilemma.
Builders on Sui can use dWallets natively and utilize IKA as a composable modular signature network, adding powerful multi-chain access control capabilities to their protocols. Smart contracts can define complex logic that governs when and how signatures are generated, enabling sophisticated features like:
Spending limits and time-locks: A dWallet could be programmed to only sign transactions below certain amounts or after specific time periods
Multi-signature approvals with conditions: Require additional approvals for large transactions while allowing routine operations to proceed normally
Automated trading strategies: Execute trades across multiple chains based on predefined conditions without giving any single entity full control
Account recovery mechanisms: Build in social recovery or time-delayed recovery options without compromising security
Real-World Applications Already Taking Shape
The IKA network enables several groundbreaking use cases including programmable Bitcoin on Sui with secure DeFi and custody, instant cross-chain DeFi operations including atomic swaps and lending, and secure MPC guardrails for AI applications to ensure AI agents don't have unchecked power over user assets.
One particularly interesting application is in the realm of institutional custody. Traditional institutional custody solutions require trusting a third party completely. With IKA's approach, institutions can maintain custody of assets across multiple blockchains while enforcing complex compliance rules and multi-party approval processes, all without any single point of failure or trust.
The Road Ahead: Scaling to Meet Web3's Ambitions
The ambitious goal of IKA is to support millions of users and tens of thousands of signatures per second with thousands of validators. The network can already scale to process transactions up to 10,000 times faster than current MPC solutions, but this is just the beginning.
The recent advancements in 2PC-MPC V2 introduce even more capabilities. The protocol now supports not only ECDSA but also Schnorr and EdDSA signatures, operates efficiently in asynchronous networks, introduces dynamic participant quorums for permissionless validator sets, and includes features like HD wallet compatibility and secure wallet transfer.
Conclusion: A New Foundation for Web3
The IKA network represents more than just another blockchain project; it's a fundamental reimagining of how blockchains can work together. By solving the seemingly impossible challenge of maintaining user sovereignty while enabling network-level programmability across chains, 2PC-MPC technology opens doors that the industry didn't even know existed.
soup retweeted
What if you could use your Bitcoin as collateral for an Ethereum loan? Or your Solana bag to borrow USDC on Sui?
Without bridges. Without wrapping. Without giving up custody.
We're building something that changes everything. ✒️
🧵 Thread 👇
soup retweeted
one of the coolest things about waap.xyz is you can add your hardware wallet as a signer and clear sign with any connected app ~ no more blind signing!
soup retweeted
This conversation with @d3h3d_ and @omersadika opened my eyes to THE BIGGEST first mover plays in all of crypto rn i.e. @ikadotxyz
Listen to the full Podcast👇
00:00 Intro
05:06 The Origin Story of Ika
09:05 What is Ika?
14:31 What Makes Ika Different from Bridges like @wormhole and projects like @LayerZero_Core
19:13 The Technical Bet on @SuiNetwork
24:21 Mainnet Launch Lessons
29:50 The Marketing Play That Changed Everything
34:30 The RFP Program and Builders
50:57 What’s Next for Ika
soup retweeted
The End of Bridges in Crypto - Voices #62
Bridges failed. Custody broke. Interoperability never scaled.
@omersadika and the team behind Ika are building the fix, a zero-trust key infrastructure where one wallet secures every chain.
Powered by @SemanticLayer | @Semantic_42
Chapters:
04:20 Why bridges failed and the zero-trust thesis
17:20 Native BTC on Sui & the first wave of builders
30:20 Tokenomics, governance & community distribution
34:00 Builder grants, RFPs
43:40 Vision for the next 12 months
46:40 Founder lessons, mindset & advice
soup retweeted
Most people will never truly see @ikadotxyz’s utility and that’s exactly what makes it powerful.
Built on the Sui blockchain, IKA isn’t a product you use directly.
It’s the zero-trust infrastructure layer where the magic quietly happens in the background, scaling to 10,000 TPS with sub-second latency across hundreds of nodes.
At its core, IKA runs on advanced 2PC MPC technology, a breakthrough threshold signature scheme that lets users and a decentralized network of validators sign and verify transactions together without ever exposing private keys.
It removes trust from the equation and enables secure, non-collusive interoperability at massive scale, far beyond legacy MPC limits of slow speeds and small node counts.
But here is why people often miss it. @ikadotxyz’s users aren’t everyday traders or fans.
They are the builders integrating its cryptography into wallets, DeFi systems, and identity protocols.
So when you one day use an app that feels faster, safer, or more private, maybe staking Bitcoin natively on Sui or making a trustless cross-chain loan, you may never realize IKA is the engine behind it.
The irony is beautiful.
The more invisible IKA becomes, the more powerful its impact truly is.
It’s not here to be seen like your usual products.
It’s here to be felt in everything built on top of it.
🦑 🦑 🦑 🦑





















