Child of God||
Football Wonderkid πͺ ||
Unn Student ||
Computer Science Major ||
Community Manager @SuiTeamSwift β‘||
SMM @Chainmove1
Manchester United π΄
Always a nice time in the presence of aspiring and existing web3 talents,
Impactful talks from @Kamtochukwu0 and @0xAfroTechBoss , as well as @eze_ransom .
Proper Meetup π
I'll be sharing a bit of what I learnt.
A thread.π§΅
From a craving to a financial revolution! Today, we celebrate the ultimate transaction that changed the world forever.
β10,000 $BTC for two pizzas in 2010. Would you have made the trade?
βHappy Bitcoin Pizza Day.
storytime.
three days ago i had nothing but a blank next.js repo and a half cold coffee from @thegarageng_ . This morning i and @ezechiziterem submitted the first parametric drought insurance product built on Stellar, and i'm still slightly in disbelief that it actually works.
so here's the story.
@TrustlessWork ran a four day hackathon with @boundless_xyz . the brief was simple, ship one specific product on their escrow primitives, no generic platforms allowed. i'd been reading about Lemonade automating crop insurance on Avalanche and Etherisc doing the same thing on Ethereum. nobody had done it for African smallholders on Stellar. so that's the one i grabbed.
the actual problem is the part that wouldn't let me sleep. picture a woman in Kano growing sorghum on one and a half hectares. one bad rainy season and her family loses a whole year of income. she cannot afford traditional crop insurance. even if she could, the claim sits on a desk in Lagos for ninety days and never makes it to her village. an entire continent of farmers running their lives on weather they have zero protection against. that is the gap.
so we built Nimbus.
how it works is almost embarrassingly simple. every morning at 6am UTC a cron hits an endpoint. that endpoint pulls cumulative rainfall for every active farm's exact GPS coordinates from Open-Meteo (free, no API key, real historical satellite data). if the season's total stays under threshold, the oracle signs a Trustless Work escrow approval server side, then the release, and USDC moves to the farmer's custodial wallet. five seconds. no human. no claim form. no adjuster. no paperwork she cannot read.
the entire insurance department is roughly eleven lines of typescript.
const { totalMm } = await fetchSeasonRainfall(lat, lon, seasonStart);
if (totalMm < farmer.drought_threshold_mm) {
const approveXdr = await approveMilestone(contractId);
await submitToStellar(signXDR(approveXdr, PLATFORM_SECRET));
const releaseXdr = await releaseFunds(contractId);
const tx = await submitToStellar(signXDR(releaseXdr, PLATFORM_SECRET));
await markPayout(https://t.co/Q0rmOUphBf, totalMm, tx.hash);
await sendSMS(https://t.co/O2xIzuwyWs, payoutMessage(farmer, totalMm, tx.hash));
}
every part of that flow is auditable. anyone with the contract id can open https://t.co/WuPmmWfE51 and watch the escrow state in real time. you can click any payout's tx hash and verify it on Stellar Expert. zero trust required, all of it on chain.
the demo i just walked judges through:
Amina Hassan in Kano, Fatima Musa in Katsina, Emeka Okonkwo in Abuja. three real coordinates pulling real rainfall. Katsina got 22mm against a 50mm threshold. one click on simulate and the policy fires, the escrow approves, USDC moves, Fatima's wallet ticks up. that's the demo. that's also the product.
a few things i did not expect to learn this week.
one. the Receiver role in a Trustless Work single release escrow can be the only role NOT held by the platform. that one design decision means the platform can never steal the funds. it can only release them, and the destination is locked to the farmer. parametric insurance becomes trust minimised almost by accident. you cannot fake that kind of primitive composition.
two. Open-Meteo is quietly the best free API on the internet. global coverage, no key, historical archive going back decades, deterministic outputs. you could build half the climate fintech in africa on top of it and nobody would notice.
three. the "oracle problem" crypto twitter agonises about disappears the moment your condition is a deterministic public dataset. parametric design beats oracle networks for an entire class of products. this is not a hot take, this is just math.
four. ai will absolutely help you ship a three day mvp if you bring the taste. but only you know which of the four trust questions actually matters to a farmer in Kano. (it is the speed of the payout. it is always the speed.)
things shipped this week:
a landing page that answers all four judging questions inline. an enrollment wizard with a leaflet map for the GPS pin.
a farmer dashboard with daily rainfall plotted against threshold. multi farm accounts so one farmer can enroll many plots across many seasons.
20 USDC of demo balance for paying premiums. an admin dashboard with live oracle controls and a simulate button. a coverage pool builder for NGOs and climate funds. a Trustless Work Escrow Viewer link on every contract row so judges can verify state live.
sign in via local session, settings page, custodial wallet export gated by phone confirm, 404 page, runtime error boundary, opengraph card, animated svg favicon. and a full demo mode where the entire app runs in memory with zero external services, so anyone cloning the repo can play with it in thirty seconds.
i hit deploy at 3am this early morning for the last commits of code and @ezechiziterem made the demo video and submitted. and live at @theblock_hive in Nsukka we're on stage with it. submission ships noon.
if you build for africa you already know this, but the boring infrastructure decisions are the ones that compound. parametric beats discretionary. on chain beats off chain. five seconds beats ninety days. one click beats a forty page form. these are not opinions.
when rain fails, Nimbus pays.
(reply if you want the repo link, dropping it once i flip the visibility.)
your doctor gets 7 minutes with you. your body has 30 years of context.
so i alongside @ezechiziterem built voxhealth β> a medical record that listens.
you speak your symptoms. @ElevenLabs transcribes. @TryNoahAI flags patterns. your ledger signs the entry on-device. @solana anchors the proof.
a doctor scans your qr. the grant verifies on-chain. elevenlabs reads your last 30 days back to them in a clinical voice. then access expires. automatically.
the real unlock was making it agentic.
i didn't want an app with buttons. i wanted one brain deciding what to do next >>> transcribe? analyze? seal? page a caregiver?
so i wrote a HealthAgent runtime. every sponsor solana, elevenlabs, noahai, ledger, virtuals, https://t.co/RmOujhkdA7, solana mobile; registers as a tool. name, schema, status, invoke fn.
two planners ship: a deterministic walker for dev, and a noahai-driven one that POSTs the rolling history + tool catalog and lets the model pick the next move.
flip an env var β the tool goes live. don't β it stays mocked. the orb shows the live count in real time. one seam, sixteen tools.
the war stories lmao.
solana anchor was the boss fight. four instructions, three PDA types, sequence-indexed entries. on-chain you only store the arweave CID + a 64-byte ed25519 sig from the ledger over (cid β patient β sequence). every byte mattered. one wrong derivation and the whole timeline desyncs.
then web3.js dep hell. lost a night to peer-range purgatory just to make
@coral-xyz/anchor
and
@solana/web3.js
agree on what a PublicKey was.
then the wallet bridge: phantom on desktop, MWA in the solana mobile dApp store browser, mock signer if neither β and the active signer has to be re-registered into the agent so the next solana.* call uses the live path. that little hand-off is what makes ten integrations feel like one machine.
30% of medical errors come from incomplete patient histories.
voxhealth: voice in. hardware sealing. on-chain settlement. time-bounded doctor access.
your voice. your keys. your record.
β³ link: https://t.co/6KM7QhkEdV
thank you @dev3pack for helping me bring this idea to life
elf is not a github replacement
it's a collaboration membrane
let me show you exactly how it works π§΅
COMMITS AS COMMUNICATION
when you log a commit in elf you write two things:
the type (feat, fix, content, auditβ¦)
a plain-english "why" β not for git, but for michael
example:
fix(0g): correct chain id 16601 β 16602
why: the 0G galileo testnet changed their chain id β all on-chain writes were failing silently
michael reads the "why."
i write the "what." same commit.
FORK REQUESTS WITHOUT A TERMINAL
non-technical teammates can approve or reject fork/branch creation requests through elf
under the hood β @KeeperHub executes it with guaranteed delivery, retry logic, and an immutable audit trail
the dev doesn't wait. the product manager doesn't need to touch github. both win.
THE SHELF AGENT
the autonomous monitor that watches your workspace
if a project goes 7+ days without a commit β it drafts a status notification, logs it on-chain via our deployed @0G_Labs contract, and writes the audit to 0G Storage Log
contract deployed on Galileo testnet: 0x220bfc37cf1ce6707b98a5e905375c1dbc4b0c2a
~21k gas per run. fully verifiable.
CONTRIBUTOR PAYMENTS
every project has a per-project treasury (fresh EOA, AES-256-GCM encrypted at rest, never exposed to client)
USDC transfers settled on Base @Uniswap Trading API for token swaps (USDC β contributor's preferred token) payment proof on-chain, not in a spreadsheet
first time i've seen a hackathon project actually wire custodial wallets properly. we did.
COWORK
real-time AI chat inside every project @AnthropicAI Claude streaming with tool use β> it can read your commits, treasury, project state multi-party via @Gensyn AXL encrypted P2P mesh (so it's not just you and a chatbot, it's your whole team + the agent in one room)
elf is the room. github is the filing cabinet.
New roads to take, new goals to chase.
This month, we celebrate the hands that keep everything moving.
Your dedication drives every journey, and your effort makes the difference.
Happy New Month.π§‘
ChainMove has made impressive progress In just 110 days of full operation, the company has generated over 1 million+ Naira in revenue after balancing her account on vehicle maintenance, driver payment and taxes as shown below :
https://t.co/1bD6HXmCvq
Happy Easter.
A season of sacrifice, hope, and new beginnings.
May this time bring peace, clarity, and renewed strength.
From all of us at OminiSolution.
On this Good Friday, we remember the sacrifice that changed the world.
At ChainMove, we remain committed to moving lives forward, safely and reliably.
#GoodFriday#ChainMove
People still think Nigerian Web3 devs just do:
> Telegram moderation
> "GM" tweets
> Airdrop hunting
Meanwhile I just shipped a portfolio that literally asks "who are you?" and gives you a COMPLETELY different experience based on your answer.
Unpopular opinion: If your developer portfolio is a React template with a hero section, an about me, a project grid, and a contact form, you don't have a portfolio. You have a PDF with extra steps πππ
Here's what mine does:
VC? Here's a blockchain explorer with your proof-of-work ledger.
CTO? Boot into a working terminal. Type ls projects/ and see 27 shipped projects. Type git log for 4 years of milestones. Type matrix and watch green rain. Run sudo hire me.
Protocol team? A 3D solar system; each planet is a blockchain I've built on. Click a planet. Watch it zoom. Projects orbit around it.
Recruiter? Full scrollable page with particle canvas hero.
Event? 3D holographic ID card you can download and print.
6 views. 27 projects. 7 chains. Zero templates.
I built DeFi protocols on Polkadot. AI platforms on 0G. Smart contracts on Stellar. E-commerce on Shopify. Full-stack platforms for real clients. A VS Code extension for Solidity debugging.
Frontend. Backend. Smart contracts. Deployment. The full stack. From Nsukka, Nigeria.
"But that's over-engineered" brother, have you SEEN the things people over-engineer for a hackathon they'll abandon in 2 weeks?
At least this one is live lmao
But sure. "Nigerian devs just moderate Telegram."
Build in public or stay quiet.
Tap in: https://t.co/L97kJO8ziO
The future of dev portfolios is adaptive. The static era is dead. Argue with your Linktree.
Which view is craziest? β