Work / Ferrum Network / 2022 — 2024
MultiSwap Alpha
A cross-chain swap system that unifies token exchange across multiple blockchain networks into a single infrastructure layer — engineered and taken to production at Ferrum Network.
Problem
Cross-chain exchange usually means a pile of bridges, DEX routers, and operational glue. The user-facing product only works if one infrastructure layer can quote, route, and settle across heterogeneous networks without pretending they share a VM.
Context
Core Ferrum interoperability work. Public repositories related to MultiSwap / FIBER are forks of upstream Ferrum org code; the published contribution is architecture, integration, and production backend on top of those systems.
Role
Senior blockchain engineer. Led R&D and delivery on the swap/bridge infrastructure layer.
Architecture
MultiSwap is documented publicly as Fiber Engine (orchestration and checks), Fiber Router (isolation of fund-manager interaction), and Fund Manager (foundry asset custody and settlement). Backend orchestration covers APIs, scheduling, and cross-chain checks.
Responsibilities
- Architect the unified swap infrastructure layer across networks.
- Engineer the integration layer for cross-chain communication and asset transfer.
- Ship and operate production backend orchestration around the Fiber engine.
Decisions
- Treat routing, fund custody, and orchestration as separate trust surfaces rather than a single contract that talks to the world.
- Keep public GitHub evidence honest: upstream Ferrum code is forked; claim architecture and production backend, not sole authorship of every contract.
Outcome
Shipped to production as one of four Ferrum bridge/swap systems. Public docs and related repositories remain inspectable.
Stack
Solidity · TypeScript · Node.js · Web3 · Hardhat · Microservices
Evidence
- Contributor on ferrumnet/MultiSwap.
- Public FIBER-Engine-Backend orchestration repository.
- Ferrum MultiSwap documentation.