Software & Data Engineering @ Flash · Bitcoin under-the-hood mechanics & fintech
I design money-movement systems: on/off ramps, Lightning settlement, ledgers, and the failure modes that appear when rails disagree.
Backend and systems engineer at Flash, working at the intersection of fintech and Bitcoin infrastructure. The default problem is orchestration: converting local money into Bitcoin (and back), reconciling partners who are slow or silent, and keeping a ledger true when banks, Mobile Money, and Lightning nodes disagree. Earlier I built payment and ERP systems in West Africa, so regulation, payroll data, and operator runbooks are architecture constraints, not afterthoughts. Adjacent to the job: the mathematics behind LLMs and modern AI — probability, optimization, and representation — because those tools will sit next to money systems whether we like it or not.
Most relevant roles for fintech and Bitcoin architecture — not a full CV.
Bitcoin/local-currency exchange, Mobile Money to Lightning on/off-ramp in under five seconds, data tracking, automated asset management, and continuous provisioning from live transaction metrics. Architecture reviews aimed at surviving unreliable external providers. Zero failed transactions on the exchange path.
Opinionated Bitcoin wallet for the Caribbean. Cash-out notifications for Jamaican users, bank top-up and settle into Bitcoin / Flash Cash, ACH inbound for freelancers, plus CLI/cron runbooks and reconciliation when partners are slow.
30+ documentation pieces on Bitcoin tools, privacy, on-chain, Lightning, miners, and nodes. Growth training: protocol as infrastructure, not slogans.
Bitcoin under-the-hood mechanics: CLI extraction, key derivation, Python wallet, UTXO, spend paths, miner candidate blocks. Lightning: channel CLI, connections, multi-hop payments, route construction. Later: LDK-Node Python binding tests and Lightning offensive heuristics.
Odoo modules, payroll, and reporting for Benin and Togo under local regulation. Relevant because money systems inherit HR, tax, and audit data long before a payment is clicked.
Impact: Local-currency to Lightning settlement in under five seconds, with a zero-failed-transaction operating record on the exchange path.
State machine for deposit, conversion, spend, and withdraw across Mobile Money and Lightning. Partner latency is treated as a first-class failure mode, not an exception.
Impact: Freelancers can receive a USD wire into a bank account that converts to spendable dollar-stable value, payable to any Lightning address.
Backend for inbound international bank transfer, conversion, and global Lightning spend. The hard part is settlement truth across bank cutoffs and Lightning immediacy.
Impact: Operators can continue when partners are slow: explicit runbooks, retries, and ledger-vs-processor diffs instead of silent stuck states.
Reconciliation jobs and dashboards for cash-out, top-up, and settle. Designed for the case where the processor, the wallet, and the bank statement disagree.
Impact: Builders in Benin and Senegal shipped wallets and payments on infra.usebreezee.xyz during hackathons; the stack was open-sourced so others can fork the plumbing.
Strip the friction of wiring Bitcoin/Lightning into a product: less boilerplate, fewer edge cases, more time shipping. Listed on the African Bitcoin Ecosystem Map.
Socratic seminars and workshops on Bitcoin: protocol, tooling, and builder practice in Cotonou.
Ran the bootcamp in Benin, Burkina Faso, and Burundi. Mission: explain Bitcoin and Lightning mechanisms, then help builders ship solutions on Lightning.
Bitcoin under-the-hood mechanics: CLI, key derivation, Python wallet, UTXO, spend paths, miner candidate blocks. Lightning: channel CLI, multi-hop payments, route construction. Later: LDK-Node Python binding tests and Lightning offensive heuristics.