chibie.eth

Work setup challenge. Post your work setup Mine 👇

Excited to share that Evolution has joined Nuvion @ournuvion 🚀 When we started Evolution, we had a simple vision: make moving money across borders easier and more accessible for individuals and businesses, enabling them to go Global from wherever they were. We believed that accessing global financial services shouldn’t be complicated simply because of where you live or where your business operates. What started as a platform for exchanging digital assets grew into something much bigger. We built infrastructure that enabled people and businesses to hold multiple currencies, receive international payments, move money across borders, and access financial tools that were previously out of reach. Along the way, we served thousands of users, processed millions of dollars in transactions, and learned firsthand what it takes to build financial infrastructure in emerging markets. But more importantly, we saw just how much work remains to be done. As we continued building, one thing became increasingly clear: solving cross-border banking challenges at scale requires more than a great product. It requires strong financial infrastructure, regulatory reach, and the ability to serve businesses wherever they operate. That’s what makes this next chapter with Nuvion particularly exciting. Nuvion is building an AI Powered Global banking platform for ambitious businesses, bringing multicurrency accounts, international payments, FX, virtual cards, and stablecoin infrastructure together in one place. Our visions have always been closely aligned, and joining forces gives us the opportunity to pursue what we started at Evolution on a much larger scale. For me, this is an opportunity to take everything we’ve learned building Evolution and apply it to something with the infrastructure, reach, and ambition to serve businesses around the world. I’m especially excited that members of the Evolution team are continuing this journey with me at Nuvion. We’ve spent years building, solving difficult problems, and learning together. Now we get to bring that experience into a much bigger mission. To everyone who believed in Evolution, our early customers, investors, partners, community, and the incredible people who contributed to our journey: thank you. You trusted us when we were still figuring things out, challenged us to build better, and helped turn an idea into a real business. I’m incredibly proud of what we built, and even more excited about what comes next. Evolution was never just about building another fintech company. It was about making global banking accessible for the people and businesses who need it. That mission continues at Nuvion. The Job is just starting

Building Brimble is the hardest thing i've done in my life and to be honest I am kind of suprised to see it's still standing, it's so crazy because we don't support local builders enough and if it's in S.F it's the other way round 1) You get constantly compared to vercel/railway and it's sad because if you want to get people in this space to use it to you need to ship features to the quality they have already set (either same quality or you go higher) 2) After shipping almost the same quality, local users here still force you to make decisions by cutting cost of your product, just because you want them to use it and at the end of the day, you still get compared and you even have no choice. 3) I and abraham have been constantly bootstrapping the product for the last 4 years, so we only scale on demand. We don't have the luxury to throw money into compute unncessarily. 4) There were different iterations of the product just to get PMF, the directions changed about 2-3 times between the years. 5) oh fine, "enterprise" has the money. But at the same time, you need a good amount of money to get the licenses to support enterprise and at the same time, some enterprise will look down on you especially when it's just 2 engineers managing the product, ever since we got the idea in 2022. You do performance and security audits yourself, you need to be extremely stable (just with a team of 2 and after all that, you still get compared. It's very much fine, but nobody gives a damn) 6) Brimble literally has everything (databases, sandboxes, fullstack deployments, autoscaling, static outbound ips e.t.c). Strived to succeed 7) You are also trying to pitch to investors, in a case where some of them don't have a clue or the nuances involved in what you are building. The best everyone has to do is support local products, supporting local products even gives you as a user a ton of advantage. You control the type of features you want, the prices is very affordable for you, you'd get the maximum support you need without having to send emails or wait for 3 business days to get feedbacks. A few angels really believes in the vision and fingers crossed, really love it. But at the end of the day, it still seems you aren't good enough for people to use you. I'm extremely grateful for people that took all of these out of their mind to actually support us in terms of using the product end to end. Sharing reasonable feedbacks and also sticking around even when it had issues. If i have the opportunity to do this again, i would peacefully decline.

𝐍𝐄𝐖 𝐒𝐏𝐄𝐀𝐊𝐄𝐑 𝐀𝐋𝐄𝐑𝐓 🚨 𝐌𝐄𝐄𝐓 𝐂𝐇𝐈𝐁𝐔𝐎𝐓𝐔 𝐀𝐌𝐀𝐃𝐈, 𝐂𝐎-𝐅𝐎𝐔𝐍𝐃𝐄𝐑 & 𝐂𝐄𝐎 𝐎𝐅 𝐏𝐀𝐘𝐂𝐑𝐄𝐒𝐓. Chibuotu is building decentralized payment infrastructure for the stablecoin era through Paycrest, helping turn onchain innovation into real-world financial solutions. Previously, @stchibie worked with Gitcoin and ConsenSys, contributing to cross-chain funding tools that have directed over $50 million toward public goods. He also advocates for capital-efficient businesses and sustainable company building. This October, Chibuotu joins us as a speaker at 𝐁𝐥𝐨𝐜𝐤𝐟𝐞𝐬𝐭 𝐀𝐟𝐫𝐢𝐜𝐚 𝟐𝟎𝟐𝟔. #BlockfestAfrica #BlockfestAfrica2026 #TheNewTradeRoute

Turns out the future does have flying cars

Excited to introduce Bella 🐙 Most AI assistants are built for technical people who speak English and developers. We're building AI agents for everyone else, right where they already are: in chat. Bella lives in WhatsApp and Telegram. Send her a voice note or a message in your own language and she gets it done: reminders, your inbox, your calendar, pictures, writing help. She understands multiple languages and replies out loud in a native voice, whether you speak Swahili, Yoruba or Hindi, Portuguese or Mandarin. No app to download and nothing to learn. Just say hi. use it today - tuningforks.co/

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be? This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-. For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption. And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10. To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety. And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all. Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems. For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size). Concrete TLDR, my own personal views: * Hash-based > lattice-based, in those situations where hash-based is possible at all * For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ... * For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism. * If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**. * For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money" firefly.social/post/x/210783…

We've earned $46,900 in revenue in 4 days 👑 🟢 145,443 players online 👀 8,614,591 visits today 👥 1,807,618 total players 🌍 16,584,859 visits all time #LagosLife lagoslife.app

been down shipping. forgot to say: it took us over a year to reach $4m TPV. less than two months later, we crossed $5m all while maintaining 95%+ settlement success. now pushing toward $6m the curve is beginning to bend.

Introducing dots, powered by GPT-6 Astra. Remarkably capable, always-on agents built to handle everything.