Book a call
I have built systems like yours, from RPC at 140k+ RPS to a live card-programme chain, and I know which early decisions will cost you a year later.
A raise closed, a CTO gap, a launch or listing ahead.
Architecture ownership, technical hiring, board and investor technical reporting, launch and listing readiness. Two days a week adds running the technical roadmap with the team.
The day, or two, is spread over the week as the work needs it. I do not count hours; I am there when it matters. Named artefacts every month, 30-day notice.
A term sheet, exclusivity, an announced acquisition.
A two-page decision brief first, then the investment-committee memo, the evidence annex and the cost to remediate in engineer-weeks and money. Ten business days; a red-flag read in five.
Fixed fee, fixed date. Repositories, entities and questions agreed in writing before the start. Not a penetration test, not a formal audit.
One decision that will be expensive to reverse: the chain, the custody model, the launch plan.
One decision area: evidence review, the options, a written recommendation and a debrief with the people who have to live with it.
A fixed two-week sprint. Implementation is separate and walled.
Thirty minutes to agree what needs doing and what it has to achieve.
A fixed fee, the named artefacts, the dates and the access I need before the start.
A retainer runs through the week; a review or a diligence runs inside its fixed dates.
The month's artefacts, the brief and the memo, or the recommendation, and a debrief.
I led the delivery, end to end, of an L2 chain that is live, with the application layer behind a non-custodial debit card programme, its indexer, oracles and account abstraction, built for MiCA alignment.
I designed a smart proxy system, with a cache layer and rate limiting, that served 140k+ requests per second in production for a browser wallet and a DEX aggregator.
I led the department that ran the infrastructure behind $1B+ locked in staking.
I led a shared prover used across several ZK protocols and L2 ecosystems, with GPU and CPU autoscaling on spot capacity.
I designed and led the complete app-kit framework for fintech and digital transformation, and took the RWA, stablecoin and payments kits into client delivery.
As fractional CTO I designed the infrastructure that carried a decentralised AI network through its token generation event and exchange listing.
With Uddug, which I co-founded, I built the platforms behind NFT launches that raised $100M+ in total: two collections raised $10M+ and $2M+ at launch, and an art platform carried a renowned painter’s series.
I co-founded Uddug and grew it to 15 people; Gateway.fm acquired it in 2024 and I ran two departments there. Along the way: a live card-programme chain, RPC at 140k+ requests per second, $1B+ in staking, a token launch through to its listing, and NFT projects that raised $100M+. In 2026 I started again: Felag, an engineering studio, and this practice.
Tell me what needs doing. The first step is a 30-minute call.
I have built systems like yours, from RPC at 140k+ RPS to a live card-programme chain, and I know which early decisions will cost you a year later.
A raise closed, a CTO gap, a launch or listing ahead.
Architecture ownership, technical hiring, board and investor technical reporting, launch and listing readiness. Two days a week adds running the technical roadmap with the team.
The day, or two, is spread over the week as the work needs it. I do not count hours; I am there when it matters. Named artefacts every month, 30-day notice.
A term sheet, exclusivity, an announced acquisition.
A two-page decision brief first, then the investment-committee memo, the evidence annex and the cost to remediate in engineer-weeks and money. Ten business days; a red-flag read in five.
Fixed fee, fixed date. Repositories, entities and questions agreed in writing before the start. Not a penetration test, not a formal audit.
One decision that will be expensive to reverse: the chain, the custody model, the launch plan.
One decision area: evidence review, the options, a written recommendation and a debrief with the people who have to live with it.
A fixed two-week sprint. Implementation is separate and walled.
Thirty minutes to agree what needs doing and what it has to achieve.
A fixed fee, the named artefacts, the dates and the access I need before the start.
A retainer runs through the week; a review or a diligence runs inside its fixed dates.
The month's artefacts, the brief and the memo, or the recommendation, and a debrief.
I led the delivery, end to end, of an L2 chain that is live, with the application layer behind a non-custodial debit card programme, its indexer, oracles and account abstraction, built for MiCA alignment.
I designed a smart proxy system, with a cache layer and rate limiting, that served 140k+ requests per second in production for a browser wallet and a DEX aggregator.
I led the department that ran the infrastructure behind $1B+ locked in staking.
I led a shared prover used across several ZK protocols and L2 ecosystems, with GPU and CPU autoscaling on spot capacity.
I designed and led the complete app-kit framework for fintech and digital transformation, and took the RWA, stablecoin and payments kits into client delivery.
As fractional CTO I designed the infrastructure that carried a decentralised AI network through its token generation event and exchange listing.
With Uddug, which I co-founded, I built the platforms behind NFT launches that raised $100M+ in total: two collections raised $10M+ and $2M+ at launch, and an art platform carried a renowned painter’s series.
I co-founded Uddug and grew it to 15 people; Gateway.fm acquired it in 2024 and I ran two departments there. Along the way: a live card-programme chain, RPC at 140k+ requests per second, $1B+ in staking, a token launch through to its listing, and NFT projects that raised $100M+. In 2026 I started again: Felag, an engineering studio, and this practice.
Tell me what needs doing. The first step is a 30-minute call.
