FRONTEND   
|
BACKEND   
|
BLOCKCHAIN   
|
OPS   
|
SECURITY   
|
I build across the full stack, from protocol logic and backend systems to frontend interfaces, operations, networking, and security. My public work already shows a strong Stellar, Soroban, Rust, and TypeScript lane, but that is not the whole picture. I also work confidently across React, Vue, Angular, Django, Node.js, DevOps pipelines, network engineering, and pentesting/security-minded delivery.
I care about software that can be defended from the outside:
- on-chain state, emitted events, and user-visible errors should tell the same story
- CI should go green for a real reason, not because the checks got dodged
- backend behavior should stay predictable when dependencies get ugly
- frontend flows should reconcile against real network state, not pretend success
- infrastructure and deployment paths should be observable and recoverable
- networks and application surfaces should be hardened, not trusted blindly
- docs should explain the observable contract, not hide behind implementation trivia
If a repository has unclear semantics, broken tests, weak operator visibility, or rough product edges, that is exactly the kind of surface I like tightening.
|
|
|
| Repository | Signal | Why it matters |
|---|---|---|
| stellar-suite | Soroban tooling | Contract development and management flows around Stellar-native builders |
| chioma | Real-world product UX | Housing and rental flows with Stellar-backed payment surfaces |
| fluid | Infrastructure | Gas abstraction, webhook trust, notifications, and operator-focused backend work |
| Alien-Gateway | Identity + privacy | Username-based crypto routing and contract-level behavior hardening |
| Fluxora-Contracts | Streaming semantics | Contract invariants, event correctness, top-up behavior, and CI repair |
| Fluxora-Backend | Service reliability | Health semantics, readiness surfaces, idempotency, and staging parity |
| stellar-goal-vault | Wallet execution | Freighter-powered pledge flows with on-chain reconciliation |
| Tradazone | Product polish | Richer user-facing payment and invoicing experiences |
I like codebases that need clarity, not ceremony.
- define the protocol or product behavior in observable terms
- tighten the auth and failure semantics until they are easy to reason about
- write or repair the tests that prove those semantics
- align docs with the actual behavior clients and operators will see
- keep the entire check matrix green instead of fixing one test at a time and hoping
What I optimize for:
- defensible behavior
- readable diffs
- green CI for the whole repo
- developer trust
- operator trust
- infrastructure trust
- security awareness
- production-readiness over demo-readiness
I am especially interested in work that spans multiple layers at once:
- Stellar-native products
- Soroban smart contracts
- full-stack web platforms
- React, Vue, Angular, and Django systems
- backend services with crisp reliability guarantees
- DevOps and deployment automation
- network and security-heavy environments
- frontend interfaces for complex financial or protocol flows
- CI and release quality in repos that actually need discipline
If the problem needs protocol thinking, product judgment, test rigor, and direct execution, I am in the right zone.
- direct communication
- pragmatic implementation
- sharp attention to acceptance criteria
- traces from CI failure back to root cause
- code and docs that are easy to review later
- no fake progress reports
I prefer work that is observable, explainable, and difficult to misread. That applies to contracts, services, tests, dashboards, and documentation alike.
