Blockchain & Web3 Engineering.
Self-custodial wallets, trading platforms, and audited Solidity smart contracts — shipped to mainnet for clients moving real value. We write contracts safe by construction, coordinate the third-party audit, and operate what we ship after launch.
What shows up in your repo.
Agent graph
Typed nodes, tool schemas, retry and fallback policy. Versioned like code.
agents/*.ts · dag.yamlEval harness
Golden sets, LLM-as-judge, regression runs on every PR.
evals/*.jsonl · ci.ymlObservability
Traces, token costs, hallucination rates, drift alarms. Wired to your stack.
otel · datadog · honeycombRunbook
What to do when a tool 500s, when latency spikes, when eval red-lines.
docs/runbook.mdCrypto systems that hold real value in production.
We have delivered full systems for clients in the market — self-custodial wallets and trading platforms, not demos. The discipline that makes that safe is the same one we bring everywhere: measure, audit, ship, operate.
Solidity & smart contracts
Production smart contracts in Solidity — token standards, vaults, staking, and protocol logic — written to be audited, gas-aware, and upgrade-safe.
Self-custodial wallets
Wallets where keys never leave the user: HD key derivation, secure signing, seed backup and recovery, hardware-wallet and WalletConnect support across EVM chains.
Trading platforms
Order routing, custody, settlement, and market data for crypto trading — built for the latency, reconciliation, and audit trail that moving funds demands.
On-chain integration
Indexers, event listeners, and typed contract bindings that connect your app to the chain reliably — with reorg handling and idempotent settlement.
Checks-effects-interactions, by default.
// Withdraw: state is updated before the external call (no reentrancy).function withdraw(uint256 amount) external nonReentrant { require(balances[msg.sender] >= amount, "insufficient"); balances[msg.sender] -= amount; // effects first emit Withdraw(msg.sender, amount); (bool ok, ) = msg.sender.call{value: amount}(""); // interaction require(ok, "transfer failed");}Audited, self-custodial, and operated after launch.
A pricing engine, rebuilt in six weeks.
One representative case. Read the full editorial walkthrough, including the deploy log and latency chart.
Rebuilding a pricing engine in six weeks.
Series C fintech · monolith → 4 services + gateway · 42 TB ledger migrated · zero downtime.
READ THE CASE →Six things finance + eng teams want answered.
Production systems. We have delivered full platforms for clients in the market — self-custodial wallets and crypto trading platforms that move real value — not testnet demos.
Yes. We write production Solidity — token standards, vaults, staking, and protocol logic — using safe patterns (checks-effects-interactions, reentrancy guards, access control) and a test suite that runs against forked mainnet state.
The user holds their own keys; we never take custody. We implement HD key derivation, secure signing, seed backup and recovery, and hardware-wallet / WalletConnect support, so your users control their funds end to end.
Yes — order routing, custody, settlement, market data, and the reconciliation and audit trail that handling funds requires. We treat it as financial infrastructure, not a front-end skin.
EVM chains and the major L2s by default. If your protocol targets a non-EVM chain, we will tell you up front whether we are the right fit.
Safe-by-construction patterns, full test coverage including fork tests, internal review, and coordination with a third-party audit before mainnet. Security review is part of the build, not an afterthought — the same discipline as our security audits practice.