
On-Chain Invoice Financing
Full working system - not yet load-tested
Invoice financing is slow, opaque, and intermediary-heavy - SMEs wait 30-90 days for cash while factoring stays paperwork-bound and hard to audit.
- #defi
- #move
- #next.js
- #rust
Selected work
Shipped work first, then early-stage concepts. Filter by maturity or tech stack.

Full working system - not yet load-tested
Invoice financing is slow, opaque, and intermediary-heavy - SMEs wait 30-90 days for cash while factoring stays paperwork-bound and hard to audit.

Full working system - not yet load-tested
Independently deployed static surfaces had no honest telemetry story - the AWS console is not observability, cookie analytics is the wrong privacy default, a static site has nothing for Prometheus to scrape, and "is the bill still cheap?" lived in another console.

Full working service - not yet load-tested
A hand-rolled static site could not keep up with typed collections, cross-cutting tags, SEO compliance, or a clean preview-vs-production release path.

Full working service - not yet load-tested
I needed a credible online presence and a freeCodeCamp-compliant portfolio without adopting a framework I could not yet justify - and I wanted the architecture decisions written down, not buried in tribal knowledge.

Partial system - core mechanism proven in code
Portfolio, blog, news digest, and quiz each needed the same material - content lived in multiple places, drifted apart, and publish was a manual ritual.

Partial system - core mechanism proven in code
Console-proven AWS hosting for four production domains still needed repeatable provisioning, environment isolation, and a release path that could promote the same four surfaces without long-lived AWS keys or rebuild-per-host chaos.

Partial service - core mechanism proven in code
Studying from personal notes meant a backend, an account, or a paid SaaS - with no algorithm swap and no reuse of the blog's content.

Partial system - core mechanism proven in code
Independently deployable static surfaces needed production HTTPS subdomains with CDN delivery, private origins, and deep-link behaviour that matched how the apps emit HTML - without waiting on CI.

Partial system - core mechanism proven in code
Multi-service stacks developed on localhost:PORT never exercise the HTTPS, CORS, cookie-scope, or cross-origin behaviour that production subdomains actually have.