Rex.dev (@Dev_Rexzy) header
Rex.dev (@Dev_Rexzy) profile picture

Cracked dev. Co-founder/CTO @geoponix/@kenuleafrica Senior frontend engineer @detawallet/@clearsig_XYZ

Nigeria
Joined January 2025
Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)Photo by Rex.dev (@Dev_Rexzy)
Rex.dev retweeted
#1 problem with vibe-coded apps: terrible UX.
85
56
15
804
47,221
I am Rex from Plateau State And u?
1
1
6
48
Rex.dev retweeted
ClearSigdotxyz.
2
4
14
424
Rex.dev retweeted
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
1
1
1
13
2,210
Hi, I'm 21:) Co-founder & a cracked dev from Nigeria 🇳🇬 Looking to connect with more people and like minds
hi, I'm 20:) founder & software dev from Nigeria🇳🇬 looking to connect with more people who like building cool stuff!
1
3
103
This video is the exact reason I don’t envy people
359
12,698
321
124,402
3,477,015
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 🤝
2,124
12,703
1,413
37,818
5,772,449
Hi, what are you working on tonight ? Me: I am working on @Clearsig_xyz tonight You?
6
142
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.
2
2
9
348
Hello, I am Rex I know you don't know me but… if you do, here's my personal page I am a software developer Let's connect and grow together…
This quoted post is unavailable.
1
1
6
299
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
1
1
19
This month is gonna be great 💯
1
6
91
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.
2
5
1
10
448
The only reason it looks like you're working hard is because everyone around you is lazy... Change your circle and you'll see how lazy of a human being you are.
1
78
A moving man will always meet his luck ¡!
1
1
5
93
Insane 🔥
BREAKING: Grok 4.5 leads VulcanBench’s new coding benchmark. 🔥 Grok scored 91.3%, solving 21 of 23 real-world software tasks across five languages, beating Claude Fable 5 and GPT-5.6 Sol while also owning the cost-efficiency frontier. Grok keeps winning. 🏆
2
56
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.
1
4
1
10
710