SOFTWARE ENGINEER & BUILDER / LAGOS, NG

Commerce.
Payments.
Bitcoin.

I’m Omoyemi Arigbanla, or yemmyharry.
I turn complex systems into products people can use. Go backends, payment flows, Bitcoin tools, and the interfaces that connect them.

  • Go
  • Rust
  • TypeScript
  • AI-assisted engineering
Building at Clooza Founder, Ipilẹ Btrust Builder
UNDER THE HOODINTERACTIVE SYSTEM SKETCH

A request.
A whole system.

01 / ENTRYCheckout
02 / ORCHESTRATIONGo payment service
GO
STATEDatabase
SETTLEMENTPayment rails

A successful charge is only the beginning. Validation, state changes, and repeat events all need deliberate handling.

Try the payment event demo
FROM THE INTERFACE TO THE INFRASTRUCTURESCROLL TO EXPLORE

01 / SELECTED WORK

Built with purpose.
Owned end to end.

Commerce, payments, and Bitcoin.
A closer look at the problems I work on
and the decisions behind the code.

clooza✳SYSTEM OVERVIEW
One platform. Many moving parts.
COMMERCE ENGINE

Built for
the business of creating.

Payments Subscriptions Ticketing Media
Products connected by a Go backend
PRODUCT ENGINEERINGGO · REACT · PAYMENT INTEGRATIONS
01 / CLOOZAPROFESSIONAL WORK

The infrastructure
behind creative commerce.

Full-stack and backend engineering for a platform bringing commerce, ticketing, and media together.

  • Multi-provider payment integrations and event handling
  • Subscription billing, discounts, and messaging credits
  • Real-time services and media processing pipelines
GoReactWebSocketsPayments
Visit Clooza
ipilẹ↟PAYMENT EXPERIENCE
Web
WhatsApp
Telegram
Everyday payments.
Built on Bitcoin.
BITCOIN + LIGHTNING
FOUNDER & LEAD ENGINEERGO · REACT · POSTGRESQL · LIGHTNING
02 / IPILẸ WALLETFOUNDER PROJECT

Bitcoin, closer
to everyday life.

A Bitcoin and Lightning wallet built around familiar web and chat experiences, with commerce in mind.

  • Product thinking through to backend implementation
  • Lightning payments, LNURL, and ledger workflows
  • Web and conversational payment interfaces
GoReactPostgreSQLLightning
Visit Ipilẹ
03 / BITCOIN NETWORK MONITOR

From node data
to useful answers.

Go backend contributions spanning node RPC integration, transaction retrieval, and network statistics.

01 node.rpc block & transaction data02 network.stats hashrate calculations03 api.responses useful network insight
Source code
ON THE WORKBENCHIN DEVELOPMENT

Kurier

Exploring resilient transport for Bitcoin transactions and payment messages across constrained connections.

An independent open-source transport SDK in development. Low-bandwidth channels, smaller payloads, and resilience are the focus.

02 / A LITTLE UNDER THE HOOD

One payment.
More than one event.

Webhooks can arrive late, repeat, or arrive out of order.
Explore how payment state stays consistent
when delivery gets messy.

BROWSER-ONLY SIMULATION

When payments don’t
follow the happy path.

Choose a scenario and follow the event log. Each starts a new sample payment; replay repeats the latest event without recording another payment.

Illustrative local example with simulated event versions and a 3-second delivery delay. No real payments or backend requests.

payment-events.logIDLE
LATEST PAYMENT · NONE

Choose a scenario to see how the payment is handled.

00:00READYWaiting for a sample event…
EVENTS RECEIVED0
PAYMENTS RECORDED0
DUPLICATES SKIPPED0

03 / OUT IN THE OPEN

Building on Bitcoin.
Contributing back.

More on GitHub

Selected merged contributions to the tools and projects other builders depend on.

04 / THE PERSON BEHIND THE CODE

Curious about the details.
Responsible for the whole.

I’m Omoyemi John Arigbanla, a software engineer based in Lagos. I’ve been programming since 2018, building across backend services, full-stack products, and Bitcoin infrastructure.

My work connects the details that users rarely see: payment state, subscription rules, real-time updates, and the services behind a useful interface. I like taking a problem from the first product question through to the code that makes it work.

Go is central to my backend work. Rust is part of my Bitcoin toolkit and learning practice. Through Btrust Builders, I also mentor engineers working through Mastering Bitcoin, Rust for Bitcoiners, and Learning Bitcoin from the Command Line.

How I approach the work
01 / SYSTEMS

Behind the interface.

APIs, payment integrations, subscription workflows, and real-time services.

GoPostgreSQLRedis
02 / PRODUCT

The whole experience.

Connect backend rules to clear, usable web and conversational interfaces.

ReactTypeScriptWebSockets
03 / BITCOIN

Closer to the protocol.

Wallet workflows, Lightning integrations, open source, and teaching the fundamentals.

RustBitcoinLightning
04 / WORKFLOW

Build with agents.

Bring AI into research, implementation, and review, with clear scope and verifiable results.

Agentic workflowsCode review

The path so far

Download résumé
2026 — PRESENTFounder & Lead EngineerIpilẹ Wallet
2024 — PRESENTFull-Stack & Backend EngineerClooza
2024 — PRESENTBuilder & ChaperoneBtrust Builders
Earlier engineering experience
2023 — 2024Backend Developer · GoTrigan
2022Software Developer · Go & ReactPerformanta
2021 — 2022Backend Engineer · GoDecagon
2020 — 2021Backend Developer · Node.jsGenesys Tech Hub

05 / HOW I BUILD

More capable tools.
Deliberate engineering.

An agentic workflow, built around clear intent,
small changes, and evidence that the work holds up.

AI-ASSISTED ENGINEERING

Use agents to explore possibilities, work through implementation, and challenge assumptions. Keep architecture, correctness, and the final decision in the engineer’s hands.

  1. Frame the problem.

    Start with the user, the existing system, and what a successful change needs to do. Give the agent useful context and a bounded task.

    Intent → clear scope
  2. Build in small steps.

    Explore approaches, develop a focused implementation, and keep changes easy to inspect. Use tools where they help move the work forward.

    Context → working change
  3. Test the edges.

    Check failure paths and assumptions. Replay an event, inspect the state, and compare the result with the intended behavior.

    Try the payment lab
  4. Own the result.

    Review the diff, understand the tradeoffs, and make the release decision. AI can contribute code; engineering judgment carries it into a product.

    Evidence → reviewed delivery

Explore the systems thinking behind the work.

Back to selected work

06 / NOTES FROM THE WORKBENCH

Learning in public.

All writing

OPEN TO THE RIGHT OPPORTUNITY

Good products
need thoughtful
engineering.

Building a product that needs solid backend engineering, a thoughtful payment experience, or a faster path from idea to implementation? Let’s talk.

Backend & full-stack rolesFintech & BitcoinAI-assisted product developmentOpen-source collaborations
Connect on LinkedIn

Start a conversation

Prefer a direct introduction? You can also reach me on LinkedIn.

ENGINEERING CASE STUDY

HAVE A SIMILAR CHALLENGE?