An exchange that could run from static files
We distributed the application through IPFS (Interplanetary File System) as static files. Server-side rendering and an application-owned middleware service could not be prerequisites for using the exchange. Blockchain nodes and indexing services supplied data, while the browser managed the connected account, live updates, and the progress of transactions.
That made the boundaries between the exchange, wallet, and bridge important. Early in development, I moved connection management into a shared layer so their APIs could operate in parallel through the same blockchain connection. Opening, closing, and restarting that connection became a separate responsibility from performing a swap or reading a balance.
As the API grew, I reorganized it into modules for assets, swaps, liquidity, rewards, and referrals. Each module handled its own operations while reusing the same account, signing, fee estimation, and transaction submission logic. I also added runnable examples so developers could exercise those operations without going through the exchange interface.
The bridge showed why this structure was useful. A transfer could involve a transaction on one chain, approval signatures, and a contract call on another. I implemented the bridge API’s transfer operations, status handling, and asset conversions. The interface needed to explain which stage had completed and what still needed to happen, with shared account and transaction handling underneath.


