Protocol interfaces, contracts, indexers, relayers, dashboards, governance tools, and QA workflows built around real onchain failure modes.
An end-to-end lending product build focused on readable position state, safer transaction flows, and protocol data that product teams could trust.
Wallet-aware lending flows
Indexed position dashboards
Transaction-state QA coverage
Open any case for the problem, scope, contribution, evidence, delivery path, and stack.
A controlled tokenization workflow tying compliance-aware contract behavior to issuer operations and investor state.
Compliance token layer
KYC-gated transfer logic
Issuer admin operations
Cross-chain swap infrastructure with contracts, relayer services, and SDK surfaces for product integration.
EVM swap contracts
Destination-chain relayer service
JavaScript SDK integration path
Production-oriented DeFi trading work across frontends, smart-contract research, and secure server-side wallet handling.
0x and dYdX integration research
Trading feature POCs
Widget and live-codebase support
Governance tooling that made proposal, delegation, and voting state visible to both protocol operators and non-technical stakeholders.
Governor contract extensions
Delegation flows
Proposal and voting-state explorer
A broad production hardening engagement spanning TypeScript migration, token automation, backend services, monitoring, and operational commands.
TypeScript frontend migration
ERC-20 automation services
Sentry and balance monitoring
Bridge infrastructure for NFT teleports between Ethereum and EOSIO, designed to recover cleanly after downtime.
Ethereum transfer detection
EOSIO transfer execution
Downtime recovery behavior
Nervos Layer 2 migration and wallet-flow work for a Web3 gaming-adjacent product with bridge and NFT display requirements.
Nervos and Godwoken migration
Metamask purchase flow
Bridge and NFT display updates
Named projects link to public-safe detail pages. Sensitive engagements stay anonymized without flattening the technical substance.
Each case follows the same frame: problem, contribution, scope, evidence, delivery path, and stack.
Use the cases to compare your own protocol, integration, or QA surface before sending a brief.
Share the protocol shape and we will map the relevant architecture, contracts, backend, frontend, and QA risks before the first sprint.
