Pinned Tweet
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.
🦑 🦑 🦑 🦑
repent from your sins oh Crypto devs and engineers. stop making users sign what they don't understand.
Blind signing has drained more wallets than any hack.
You see hex,you click sign and you hope for the best.
That's not security. That's luck.
@ClearSig_xyz shows you exactly what you're approving in plain English before anything moves.
Watch how we're fixing the thing everyone ignores.
Ikafam. retweeted
Blind signing has drained more wallets than any hack.
You see hex,you click sign and you hope for the best.
That's not security. That's luck.
@ClearSig_xyz shows you exactly what you're approving in plain English before anything moves.
Watch how we're fixing the thing everyone ignores.
Ikafam. retweeted
We've been quiet. Not because we gave up.
Behind the scenes the team never stopped.
Developers pushing code through sleepless nights. Technical problems getting solved one by one. Everyone doing whatever it takes.
We hit a wall. We regrouped. We kept building.
As @ikadotxyz approaches mainnet, so do we.
We're in the final stretch, refining the product, locking in funding, and making sure ClearSig delivers what teams, DAOs, friends, families, and agents managing shared wallets have always been missing.
The solution is almost ready.
To everyone who has supported us since day one, you have no idea how much that has kept us going.
We're just getting started.
Ikafam. retweeted
We have been in the basement.
We've been quiet. Not because we gave up.
Behind the scenes the team never stopped.
Developers pushing code through sleepless nights. Technical problems getting solved one by one. Everyone doing whatever it takes.
We hit a wall. We regrouped. We kept building.
As @ikadotxyz approaches mainnet, so do we.
We're in the final stretch, refining the product, locking in funding, and making sure ClearSig delivers what teams, DAOs, friends, families, and agents managing shared wallets have always been missing.
The solution is almost ready.
To everyone who has supported us since day one, you have no idea how much that has kept us going.
We're just getting started.
Ikafam. retweeted
Day 10.
@encrypt_xyz is another important part of where @Clearsig_xyz is going.
Policies are powerful, but many policy values are sensitive.
A team may not want every limit, recipient rule, time window, or agent constraint exposed
in plain text forever.
So we are integrating Encrypt as the privacy layer for policy data.
The current path is pre-alpha, so we are careful about boundaries:
ClearSig stores references and digests.
Plaintext policy material should not become permanent backend data.
The provider can evolve without forcing a rewrite of the wallet.
The long-term goal is simple:
teams should be able to enforce rules without making every rule value public.
Privacy and control should work together
Day 9.
A hidden challenge in multichain signing is that “ECDSA” does not mean every chain is identical.
Ethereum signs a different kind of payload from Bitcoin.
Zcash has different hashing needs.
Hyperliquid may share EVM-style signing, but it still needs its own execution context.
So @Clearsig_xyz cannot treat remote chains as a single generic bucket.
The backend has to prepare chain-native payloads.
The @solana program has to bind the right dWallet to the right chain kind.
The worker has to request the right Ika signature scheme.
The app has to show a human-readable review before any approval happens.
That is the engineering line we are walking:
generic enough to scale,
specific enough to be correct.
Ikafam. retweeted
Day 11.
@Clearsig_xyz is not just trying to make multisig prettier.
We are trying to make shared wallets operationally safer.
For a team, a wallet is not only a key.
It is a decision system.
Who can act?
Who must approve?
Which chains are enabled?
Which policy applies?
Which transaction is being signed?
Which remote-chain signature will be produced?
That is why the architecture has multiple layers:
@solana program for critical wallet state.
Rust backend for orchestration and indexing.
@ikadotxyz for remote-chain dWallet signing.
@encrypt_xyz or private policy.
The product feels simple only if the layers underneath are honest.
Day 10.
@encrypt_xyz is another important part of where @Clearsig_xyz is going.
Policies are powerful, but many policy values are sensitive.
A team may not want every limit, recipient rule, time window, or agent constraint exposed
in plain text forever.
So we are integrating Encrypt as the privacy layer for policy data.
The current path is pre-alpha, so we are careful about boundaries:
ClearSig stores references and digests.
Plaintext policy material should not become permanent backend data.
The provider can evolve without forcing a rewrite of the wallet.
The long-term goal is simple:
teams should be able to enforce rules without making every rule value public.
Privacy and control should work together
Ikafam. retweeted
One thing that's really caught my attention this week...
AI agents.
Everyone's talking about AI managing crypto, but one question kept bothering me:
How do you let an AI do useful work without giving it unlimited control over your funds?
One of the ideas I'm learning while building @Clearsig_xyz is that the answer isn't giving AI custody.
It's giving AI boundaries.
Imagine an agent that's only allowed to:
• Trade specific assets
• Stay within a spending limit
• Follow predefined policies
• Request actions that humans can clearly review
If it's within policy, it can execute.
If it isn't, it stops.
That's the kind of architecture that makes AI feel practical instead of risky.
What's even more interesting is seeing how the pieces come together:
• @solana provides the coordination layer.
• @ikadotxyz provides the programmable signing infrastructure.
• @encrypt_xyz brings confidential computation into the stack.
• @Clearsig_xyz ties it all together with policies, human-readable intents, and shared treasury management.
The more I learn, the more I realize this isn't about making AI more powerful.
It's about making AI accountable.
Day 3 of documenting what I'm learning while building @Clearsig_xyz.
One thing that's been clicking for me while building @Clearsig_xyz is how central @ikadotxyz is to the architecture.
At first, I thought Ika was "just" handling signatures.
The deeper I looked, the more I realized it's much more than that.
One of the ideas I find fascinating is that the same dWallet can control native addresses across multiple chains.
Not a bridge.
Not a wrapped version of your assets.
Native addresses.
That means ClearSig can focus on what it does best defining policies, coordinating approvals, and presenting human-readable intents, while @ikadotxyz provides the programmable signing layer that makes those decisions executable across different blockchains.
It's one of those architectural choices that seems simple on the surface, but changes how you think about building multi-chain applications.
I'm looking forward to learning even more about how the pieces fit together.
Day 3 of documenting what I'm learning while building @Clearsig_xyz.
Ikafam. retweeted
Bullish on @Clearsig_xyz
You can now understand exactly what you're signing on hot or cold wallets.
Ikafam. retweeted
The multisig industry has spent years asking the wrong question.
"How many people approved this transaction?"
3 of 5.
5 of 7.
7 of 12.
Great.
Now answer the question that actually matters:
Did any of them understand what they approved?
Because a transaction signed by 7 people can still drain a treasury.
A multisig doesn't automatically create understanding.
It creates consensus.
Those are not the same thing.
Today's treasury tools focus on who can sign.
ClearSig focuses on what they're signing.
Before funds move:
• Transactions become human-readable actions.
• Policies define what is allowed.
• Spending limits can be enforced.
• Approval requirements are transparent.
• Activity is auditable.
The goal isn't more signatures.
The goal is fewer mistakes.
Because the biggest threat to a treasury isn't always a hacker.
Sometimes it's a perfectly authorized transaction that nobody fully understood.
That's the problem we're here to solve.
Ikafam. retweeted
The industry keeps talking about AI agents managing capital.
Cool.
Now answer one question:
Why would anyone give an AI agent unrestricted access to treasury funds?
That's not innovation.
That's outsourced recklessness.
Agents should operate inside rules.
Inside limits
GM
Ikafam. retweeted
Most multisigs solved one problem:
"Who can sign?"
They never solved the more important one:
"What exactly are they signing?"
A transaction approved by 5 people can still be a terrible transaction.
More signatures ≠ more understanding.
Approvals should really mean somethin
Ikafam. retweeted
for those asking about @Clearsig_xyz and what's about, as the Product lead I will be expanding more of why ClearSig is built and why it's a must used multisig wallet you should embrace
we're privileged to be building something bigger than our current capacity.
CC: @Clearsig_xyz
Ikafam. retweeted
A treasury shouldn't depend on trust.
It should depend on rules. With @Clearsig_xyz , teams define policies before funds ever move:
• Spending limits
• Required approvals
• Role-based permissions
• Transparent approval history
People make decisions.
Policies enforce them.
most crypto security isn't broken because of hackers. it's broken because humans are forced to approve things they don't understand. gigning hex isn't security. it's gambling. @Clearsig_xyz replaces blind-signing with clear, human-readable transaction approvals.
Ikafam. retweeted
WTF is ClearSig???
ClearSig is basically a smarter shared wallet for crypto teams, families, DAOs, and even AI agents.
Think of it like a shared bank account, but you have clear rules built in it.
You can set policies (rules) like:
- Spend no more than $500 per week
- Require multiple approvals for large transactions
- Allow an AI agent to trade, but only within fixed limits
- Restrict funds to specific wallets or activities
The best part?
You don’t have to approve transactions blindly.
Before signing, ClearSig shows a simple, readable receipt explaining exactly what is about to happen.
For example:
“Send 5 SOL to the Operations vault.”
Here there is no confusing contract data, blind signing or agent running away with the treasury.
It also supports safer account recovery without depending entirely on one seed phrase.
In simple terms:
ClearSig = readable transactions + rule-based spending + multi-approval security.
A shared crypto wallet built for humans and agents to manage funds safely together.
It's still in it early development stage, but definitely one to watch.
Visit clearsig.xyz to try it out on Solana Devent.
Ikafam. retweeted
One treasury.
Multiple chains.
No bridges.
No wrapped assets.
No blind-signing.
ClearSig coordinates secure, policy-driven approvals across chains from a single interface, helping teams manage digital assets with confidence.
@Clearsig_xyz
