Full-stack & blockchain developer

I build software that moves money and saves people work.

I’m Akinola Adejoke, a full-stack and blockchain developer. I design and build software for Bitcoin Layer-2s, on-chain agents, and the institutions that depend on it. Most of it is deployed and open, and every claim below links to something you can check yourself.

Most of my work is a working product with a URL: an app people can open, a payment that actually settles, a database that remembers correctly. I care about the parts that are easy to skip, and about whether someone outside this field can use what I ship without a manual.
Full-stack and protocol engineering across Bitcoin L2s (Stacks/Clarity, SatVM), EVM (Solidity/Foundry), Starknet (Cairo), Monad, Base, Solana and Canton. TypeScript end to end; smart contracts, backends, and the interface that sits on top of them.
See the workRésumé
Not a developer? Start in Plain, every term is explained.
109
automated tests
in the flagship credit protocol
13
live demos
each one loads, checked from this page
13
open-source projects
each one linked to its repository

The toolkit

01 Selected work

Less talk. More building.

Four builds, and what each one is actually for. Every one has a live demo or a repository you can read.

Showing 5 of 5 projects.

Protocol & full-stack engineer01 / 05

Borrow against your Bitcoin without ever handing it over. You lock Bitcoin into a vault that stays under your control. No company holds it.

TypeScriptNext.jsSatVM
Product & full-stack engineer02 / 05

A university exam calendar that can't quietly go out of date. One searchable calendar for sessions, semesters, exams, registration and breaks, with the registry that creates them.

Next.js 16React Server ComponentsTypeScript
Systems & agent engineering03 / 05

An agent that keeps watch over the hours when the price feeds fall asleep. Reads the live market price, the official feed and the timestamp on it, every 60 seconds.

TypeScriptBaseAerodrome
Lead systems & AI engineer04 / 05

Send money by saying it out loud. The person receiving it never has to read anything. You say what you want, "send fifty dollars to my sister Ana for groceries", in English or Spanish.

TypeScriptNext.jsElevenLabs
Product engineer05 / 05

A support wall that pays the creator in full, in the currencies people actually hold. A visitor leaves a short note with a tip, paid in NIM or through Nimiq Pay, and the creator receives the whole amount.

Nimiq PayEd25519TypeScript
Smaller builds and experiments are in the lab below.Browse the lab

02 What I do

Three things, done properly.

I would rather be genuinely useful in three areas than name-check fifteen technologies. These are the problems I have solved end to end, including the unglamorous parts.

No jargon without a definition.

Web apps people actually finish using

Interfaces, auth, roles, payments, notifications, audit trails. Shipped end to end, not a prototype that stops at the login screen.

Acadex / exam scheduling · DrawBound / credit

Smart contracts and the rails around them

Bitcoin L2, EVM, Starknet and Canton. The contract, the indexer, the relayer, the dashboard: the boring parts that make it real.

DrawBound / L2 credit · PegWatch / agent risk

AI that is accountable for what it does

Agents that act on-chain, explain themselves, and are built so a human can inspect the audit trail afterwards.

TonPilot / plain-language wallet · HashPilot / mining terminal

03 How it works

A process you can hold me to.

Four steps. No jargon, no mystery, and a written record of the decisions at each one.

  1. Find the real problem

    Most briefs describe a symptom. I go looking for the actual failure, who it hurts, how often, and what it costs them today.

  2. Decide what must be true

    Before writing code I write down the rules the system cannot break, and what the user sees at each step. If I can't state it, I haven't understood it yet.

  3. Build it properly

    Typed end to end, tests around the risky parts, honest about which data is real and which is illustrative.

    Typed, tested, and deployed on infrastructure you can inspect.
  4. Show the evidence

    A live URL, a test run, a screenshot. Anyone can claim to have built something; I'd rather you check than take my word.

In practice steps 1 and 2 overlap, and step 3 is where the schedule slips. I would rather tell you that now than promise a date I cannot keep.

04 The lab

Things I built to learn.

Smaller experiments, each one solving a question I could not answer any other way. Most are hackathon entries and weekend builds.

Showing 9 of 9 lab projects.

Live

Proof of Rest

Lock a stake to start a work session. Stop on time and reclaim it; run over and lose part. The cool-down is enforced by the contract.

Monad PlaygroundSolidityMonad
Live

Staxiq

Where should your Bitcoin sit? A yield view for Bitcoin DeFi on Stacks, scored by an open rubric that admits when its numbers disagree with DefiLlama.

ClarityStacks
Live

ExpatShip

Cross-border shipping for people moving country: instant duty-inclusive quote, generated customs invoice, live route map. It labels what is computed and what is sample data.

ReactViteSupabase
Live

Deadman Vault

A proof-of-life treasury. Check in on schedule and your funds stay put; stop and they move to the people you chose.

StacksClarity
Live

HashPilot

A mining terminal that reads chain state and gives a straight answer: claim now, or wait. Plus a three-move playbook for your risk profile.

Next.jsAvalanche
Live

TonPilot

A Telegram bot where you describe what you want done with your wallet in plain language, and it does it. No dashboard, no dApp.

TypeScriptTON
Source only

SatsLoom

A merchant payment product on Bitcoin signet that issues real BOLT11 invoices on its own Lightning node and credits a payment only when the node reveals a preimage that hashes to the invoice's payment hash. Settlement is real; the simulation surface is labelled as simulation in every response envelope.

Lightning rail · signetTypeScriptFastifyLND
Live

StashFlow

Goal-based savings where the goal is the point: name an amount, watch it fill up, earn yield the whole time.

Next.js 16LI.FI
Live

ELARSAGE GADGETS

A gadget shop for a real storefront in Computer Village, Ikeja. Guests browse and check out without an account, the order reaches the shop on WhatsApp, and a printable receipt with the device IMEI waits behind the admin.

Client build · live shopNext.js 16TypeScriptPrisma

05 The person

Not a straight line. That’s the point.

I started as a full-stack and blockchain developer. Now I'm a first-year radiography student. The distance between those two is smaller than it looks: both are about understanding a system properly and refusing to guess.

In software, the hard part was never the code. It was knowing what the person on the other end actually needed, and building for them rather than for the stack. In radiography it means reading an image that could be anything, and being honest about what you can and cannot see.

Every project here exists because something was harder than it needed to be.

An exam calendar that took a department a week to build and could quietly go out of date. A withdrawal threshold that stranded small balances. A remittance flow that assumed the person receiving the money could read a wallet address. A support wall that took a cut of the money it was meant to pass through.

That is the whole instinct: find the friction, understand it properly, remove it, and hand someone a thing that just works. If a problem needs a spreadsheet and a process change rather than an app, that is the answer too.

  1. Software
    Where it started

    Full-stack and blockchain development, from the fundamentals through to shipping complete applications with real users and real money involved.

  2. Web3 & AI
    The pace

    A Dev3Pack fellowship, then hackathons across Stacks, TON, Monad and Base. Blank canvas to deployed prototype in 48–72 hours, repeatedly. This is where most of the work on this page comes from.

  3. Radiography
    Now, first year

    Medical imaging: precision physics, invisible systems, and the moment someone depends on your reading of them. It sharpens the engineering rather than competing with it.

Different fields, same instinct: take something complicated, understand it honestly, and make it usable by someone who has never heard of it.

WHERE I WORK
Two fields, one instinct.
First-year radiography studentFull-stack & blockchain developerOpen to contracts and teams
Akinola Adejoke
Open to product & engineering work

06 Questions

Everything else, answered.

The questions I get most, plus every piece of jargon on this page, defined in one sentence each. No account required, no email gate.

Ask something else

Questions

8
Are you available for new work?

Yes, for product and engineering work: a contract, a protocol, a product that needs shipping, or a team that needs a technical lead. I reply to everything that looks like a real problem, usually within a day or two.

Do you work with non-technical teams?

That is most of the work. A clinic, a school, a small fund: I care about the problem and who it hurts, not which framework we land on. If a problem needs a spreadsheet and a process change rather than an app, I will say so.

What does a project usually cost?

It depends entirely on scope, so I quote after the first conversation rather than posting a fake range. Small, well-defined builds are quick to price. Anything touching money, auth, or data integrity needs real time in the estimate, and I would rather quote honestly and adjust than quote cheap and disappear.

Can you work with an existing codebase?

Often, and it is my preferred kind of work. I start by reading the code and running it, then write down what I found before changing anything. You get that write-up whether or not we continue.

Do you offer a technical audit?

Yes. A fixed-scope review of a contract, a system, or a codebase, delivered as a prioritised findings document you can act on or hand to someone else. If the honest answer is that your project is fine, that is what the report says.

How do you handle AI in your work?

I use it as a tool and I say so. Anything an agent does on a user's behalf is built to be auditable afterwards, and I will tell you which parts were generated and which parts are my own decisions. I do not ship model output I have not read.

What if the project does not work?

Then we find out early, which is the entire point of the process on this page. You keep everything I produce, the code is yours, and you get an honest account of what failed and why.

What is your timezone?

West Africa Time, UTC+1. That overlaps comfortably with Europe in the morning and US Eastern in the afternoon, so a few hours of overlap is easy to arrange.

Glossary

13
Bitcoin L2

A second layer built on top of Bitcoin. Faster and cheaper than Bitcoin itself, but the transactions still settle back onto Bitcoin.

Smart contract

A program deployed to a blockchain that holds money or rules and runs on its own. Nobody can quietly change it afterwards.

DeFi

Decentralised finance: lending, trading and savings apps that run without a bank or broker in the middle.

Self-custodial

You hold the keys. Nobody else can move your money, including whoever built the app.

Testnet

A practice copy of a blockchain. Real code, fake money, free to break. Where most of these projects run.

Oracle

A service that brings outside data, a price, say, on to a blockchain, which cannot reach the internet by itself.

Cross-chain

Moving value between two different blockchains.

Settlement

The moment money actually lands and can no longer be reversed.

Collateral

Something you lock up as a promise that you will pay it back.

Agent

A program that takes actions on someone's behalf, rather than only answering questions.

MCP

Model Context Protocol: an open standard that lets an AI assistant connect to other tools and data sources.

WASM

WebAssembly: running a real computer program inside a web browser, so a developer needs nothing installed.

Tokenised

An asset like a share, represented as a token that can be traded on a blockchain.

07 Contact

Have a project? Let’s make it real.

Open to product and engineering work, a contract, a protocol, a product that needs shipping, or a team that needs a technical lead. I reply to everything that looks like a real problem.

Reply usually within 48 hours

Let's build something useful.

Tell me what you’re trying to build.

A paragraph is plenty. What the problem is, who has it, and roughly when you need it. I will reply with honest next steps, even if that is not me.

No newsletter, no CRM, no tracking. The message goes to one inbox: mine.