Cracked dev. Co-founder/CTO @geoponix/@kenuleafrica Senior frontend engineer @detawallet/@clearsig_XYZ
Nigeria
Joined January 2025
- Tweets2.6K
- Following674
- Followers673
- Likes4K
Rex.dev retweeted
Dear @MTNNG , it is with a heart filled with joy I use to inform you that you have until 11:59pm Monday, 31st of August to duly respond to my comprehensive well broken down mail with a duly comprehensive report and review 🤝
Rex.dev retweeted
Attended my second iDICE Founders Lab networking session at Startup Bauchi. Of course, it was insightful. At some point, I was already criticizing my startup idea. 😂
It's such a great place to be as a young founder.
Rex.dev retweeted
Locked in a great session tonight building Python data transformation pipelines!
Worked on:
✅ Handling missing/invalid data using try-except
✅ String normalization for cleaner queries
✅ Aggregating revenue & metrics across cleaned records
Rex.dev 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.
Rex.dev retweeted
Day 12.
@HyperliquidX is a good example of why @Clearsig_xyz needs a real multichain architecture.
It is not enough to say “we support EVM.”
Teams want to operate where liquidity, execution, and opportunity exist.
That means a shared wallet should be able to support @solana, @ethereum, @Bitcoin, @Zcash Hyperliquid, and future chains without rebuilding the product every time.
So we are building around registries and adapters:
chain registry in the app,
chain preparation in the Rust backend,
chain kind and binding state in the Solana program,
@ikadotxyz signing parameters per chain.
Adding a chain should be engineering work, not a product rewrite.
That is the bar we are setting at clearsig.
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.
Rex.dev retweeted
Multisigs solve who signs.
Incidents like this highlight the harder question:
What happens when something goes wrong?
Recovery, policies, approvals, and operational controls become just as important as the signatures themselves.
That's the direction we're building toward at @Clearsig_xyz.
Where sign occurs for ClearSig is crucial. Instead on frontend or backend, it's done onchain with Clear intents readable to users before they sign anything
This kind of sounds like an excuse for signing a bad link you receive on telegram from some dudes in North Korea from a hot wallet that holds admin keys 🤷♂️ those wallets? Those wallets should have friction and be a god-awful miserable experience to sign something. PS the Ledger Stax is pretty badass. First ledger product I actually used past the initial setup.
Rex.dev retweeted
.@Clearsig_xyz mobile App looking cleaner and clearer here.
@solanamobile we're coming.
@superteam
@SuperteamNG
@ikadotxyz
Rex.dev retweeted
"HOLD MY BEER" he said.
@solanamobile expects us soon.
.@Clearsig_xyz mobile App looking cleaner and clearer here.
@solanamobile we're coming.
@superteam
@SuperteamNG
@ikadotxyz
Rex.dev 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.
Rex.dev 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
Rex.dev retweeted
people keep asking what makes ClearSig different from every other multisig like @SafeLabs_ ?
well, to us. it's not just the clear signing,
it's what's running underneath it.
a technology decision most wallets never even considered but we deliberately & will still sticked to it.
every multisig wallet today stores your private key somewhere.
a server. a device. an encrypted file.
doesn't matter how well it's protected. it exists as a complete object.
& anything that exists can be found.
@Clearsig_xyz is built on @ikadotxyz 2PC-MPC architecture. @dWalletLabs & @encrypt_xyz. the choice was very easy for the team & picking @solana as our infrastructure layer.
with Ika, your private key is mathematically split the moment it's created.
no server holds it. no device holds it. no person holds it.
it has never existed & never will as one complete thing.
signatures are produced when both parties compute together.
not by combining the key first.
by collaborating on the answer without either side ever seeing the full picture.
like two people solving a puzzle where neither ever sees the other's half.
the result?
there is no honeypot.
no single machine to compromise.
no single insider to bribe.
no single breach that ends everything.
the attack that took down @Bybit_Official starts with finding a complete key.
with ClearSig, that starting point doesn't exist.
this isn't a security feature.
it's a structural guarantee for you & your team funds.
explore devnet: clearsig.xyz
Rex.dev 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
Rex.dev retweeted
Cleaner TL now, omooh we've been suffering all this while.
@nikitabier you just sabi your work now 🤝
Rex.dev retweeted
My $ANSEM contribution dashboard in one glimpse on Bullpen 🐂🀄
- 14 days of holding.
- 55 posts published.
- 5.4K impressions recorded.
I’ve been supporting The Black Bull with both conviction and content.
Now we keep charging, keep creating, and wait to see how the contribution gets rewarded.
$ANSEM season is still active, are you active???
GM CT,
Hope your X account and $ANSEM holding wallet are linked on Bullpen???
With Bullpenfi, you can trade any market onchain. On-ramp and off-ramp are done easily without any fee attached, all thanks to @blknoiz06 and his based team.
There's a campaign ongoing which you can benefit from, all you have to do is:
- Hold $ANSEM ✅
- Connect X ✅
- Post about $ANSEM loading 🔜⏳
While we wait for the impression counter to go live, you should start writing and posting to stay positioned around The Black Bull.
Join @BullpenFi now so don’t miss the $ANSEM airdrop.
my ref link in the comments...
