Hassan Dosunmu · Zaygal
I build systems that hold up when you check them.
Agent harnesses, backend systems, integrations, automation, and protocol-level engineering. Every project below is backed by a live deployment, a reproducible benchmark, or a public commit, and I state the limits of each one rather than rounding up.
Track recordSix merged pull requests in repositories I do not own, a batch payments contract settled on Arc mainnet, and operational platforms running in production. Every claim on this site links to something you can open and check for yourself.
What I Build
The interesting work is in the system, not the screen.
Agent Engineering
Agent harnesses, tool permission models, trace-driven optimisation, and verifiers that grade the work independently of the agent that produced it.
MCP Servers & Integrations
Model Context Protocol servers and typed clients for third-party APIs, built around the settlement and error semantics the schema actually defines.
Backend Systems
Role-based platforms, real-time dashboards, data validation against source records, and payment flows that settle for real.
Protocol Engineering
Specifications written before the code, cryptographic session design, and transports that work on constrained or unreliable networks.
Automation
Multi-step pipelines with human approval gates, deduplication, and the monitoring needed to keep them honest over time.
Developer Tooling
CI harnesses, reproducible benchmarks, and small tools other engineers can run without installing anything.
How I Work
I would rather show the evidence than the adjective.
Before
- Benchmarks that only pass on the author's laptop
- Privacy claims with no written threat model
- Batch payments with no proof of who actually paid
- Agent costs nobody can attribute to a cause
- Deployments described but never verified
After
- Numbers produced by CI on every single push
- Limits written down beside the claim they qualify
- On-chain receipts a recipient can verify alone
- Trace-level attribution of where the cost went
- Deployment state stated exactly, including not deployed
Featured Project
CopaLog
A five-role operational platform that replaced fragmented reporting with a centralized, real-time system.
Live in production
More Projects
Ouroboros
Self-Optimising Agent Harness
Manifest
Batch Payments on Arc
Zaycomm
Mesh Communication Protocol
Envelope
Verifiable Payroll
Technocore Agent Tools
Identity Verification Tooling
VoYN Content Pipeline
Workflow Automation
CareerLiftNG
SaaS Product
Liberty Border Roleplay
Community Site
Havn
Rental Platform
Open Source
Six pull requests merged into other people's repositories.
Reviewers who do not know me accepted these changes on their own projects. Each one is a small, specific fix, and every link below goes straight to the merged pull request.
remember the mute across a reconnect
The GPT Live plugin lost the user's muted state when the transport reconnected, so a muted participant came back audible. Fixed by carrying the mute across the reconnect rather than resetting it.
allow opting out of the local EOT weights in the preload
The IPC preload bundled end-of-turn weights with no way to decline them. Added an opt-out for deployments that supply their own.
ask git whether .vscode/mcp.json is ignored
The setup wizard passed --no-index when asking git about the ignore state, which tells git to disregard its own index, so an already-tracked file was reported as ignored. A tracked file is never ignored whatever .gitignore says, so the wizard could call the path safe while git status still showed a seed-phrase file as committable. Removed the flag so the query answers the question actually being asked.
keep the tail bound when a short line precedes a huge line
The streaming preview bounds the text it re-wraps on every token update, by searching backwards for a newline. That search had no lower bound, so a short line followed by a minified bundle snapped the start back past the entire bound. Measured 1,310 ms per update against 5.8 ms for the already-fixed case. The bound is now preserved.
add the Privy embedded wallet adapter
Contributed a wallet adapter so applications using Privy as an embedded wallet can use the kit's deposit infrastructure.
add etherpk
Added a project entry to the community startup list.
About
I'm Hassan Dosunmu, and I build the systems behind the interface.
I am self-taught, and I learned by shipping rather than by studying: a five-role operations platform running in production, a mesh protocol specified across ten RFCs before a line of code, an agent harness whose benchmark is measured in CI, and a batch payments contract that has settled a real transaction on Arc.
I work mostly in TypeScript, Python and Solidity, and the part I care about most is the part that is easiest to fake: whether the thing actually does what it claims. So I state the limits of each project next to the result, and I link to the evidence rather than describing it.
Working With Me
How I work, and why it is checkable.
I write the specification before the code.
Zaycomm's protocol was designed across ten RFCs before implementation began. A design defect is far cheaper to fix than a codebase.
I measure, then I claim.
Ouroboros' token figures are produced by CI on every push, so they cannot quietly drift away from reality.
I state what a project does not do.
Envelope lists the things it cannot prove, including that it is not fully private payroll. That list is what makes the rest believable.
I keep the change space small.
The Ouroboros optimiser is deliberately not a code rewriter. Changes are small, declared, auditable, and each one cites its evidence.
Nothing grades its own homework.
Where the result matters, an independent verifier re-runs the task's own objective grader from a clean tree.
I ship to real systems.
Settled on Arc mainnet, in production at copalog.vercel.app, and merged into six repositories I do not own.
Technology
Have a system that needs building?
Tell me what it has to do, and I will tell you what it takes, how we would prove it works, and what it will not do.
Get in touch