Usman Adamu OthmanImam

<img src="https://capsule-render.vercel.app/api?type=waving&color=0:0f2027,50:203a43,100:2c5364&height=190&section=header&text=Othman%20Imam&fontSize=52&fontColor=ffffff&fontAlignY=38&desc=Smart%20[...]

◈ Overview

I design and ship software where correctness is non-negotiable: on-chain contracts that move value, and backend services that keep organizational data consistent. My approach is simple, and it[...]

Specify it. Implement it. Document it. Prove it with tests.

Most of my recent work is open-source contribution to production-grade projects, where every merge has to survive code review, CI, and maintainers who care about quality.

◈ Focus Areas

Domain	What I do
Smart Contracts	Rust contracts on Stellar's Soroban: escrow-style job flows, bidding, deliverables, state machines
Contract Engineering	Structured event emission, explicit error handling, snapshot-tested behavior, Rustdoc-level documentation
Backend Services	Modular feature work (e.g. company-level settings and configuration modules) in TypeScript codebases
Open Source	Scoped, review-ready PRs that close real issues, with docs and tests included

◈ Selected Contributions

`DXmakers/lance`

A decentralized freelance job marketplace (JobRegistry contract)

A full job lifecycle, implemented function by function:

submit_bid: bid submission with validation, error handling and event logging (#219)
accept_bid: bid validation, events, docs and tests
submit_deliverable: Rustdoc documentation, a typed DeliverableSubmittedEvent, updated test snapshots and contract docs (#220)

`DistinctCodes/AssetsUp`

Asset management platform

Settings module: system-wide configuration managed at the company level (#265)
Reviewed and approved by maintainers

Contributions are delivered through structured open-source programs, where each PR is tied to a tracked issue.

◈ How I Work

  ISSUE ──▶ DESIGN ──▶ IMPLEMENT ──▶ DOCUMENT ──▶ TEST ──▶ MERGE
    │          │           │             │          │         │
  scoped   edge cases   typed events   Rustdoc   snapshots  reviewed
  to one   & failure    over ad-hoc    + docs/    + 90%+     by
  concern  modes first  tuples         guides     coverage   maintainers

Principles I hold myself to

Typed over ad-hoc. Structured events and explicit errors beat tuples and panics.
Docs ship with code. If a function is public, it is documented in the same PR.
Tests are the spec. Behavior changes must show up in the snapshots.
Small, reviewable diffs. One issue, one PR, one clear story.

◈ Toolbox

◈ Activity

<img height="165" src="https://github-readme-stats.vercel.app/api?username=OthmanImam&show_icons=true&hide_border=true&bg_color=0f2027&title_color=5eead4&icon_color=5eead4&text_color=cbd5e1&count[...] <img height="165" src="https://github-readme-stats.vercel.app/api/top-langs/?username=OthmanImam&layout=compact&hide_border=true&bg_color=0f2027&title_color=5eead4&text_color=cbd5e1" alt="Top lan[...]

<img src="https://github-readme-streak-stats.herokuapp.com/?user=OthmanImam&theme=transparent&hide_border=true&stroke=5eead4&ring=5eead4&fire=5eead4&currStreakLabel=cbd5e1&sideLabels=cbd5e1&currS[...]

Contribution graph

<img src="https://github-readme-activity-graph.vercel.app/graph?username=OthmanImam&bg_color=0f2027&color=5eead4&line=2c5364&point=ffffff&area=true&hide_border=true" alt="Contribution graph" widt[...]

◈ Let's Connect

I'm open to contract-based smart contract work, backend roles, and meaningful open-source collaboration.

_{"Ship less, but ship it right."}

Navigation Menu