simpleTracker

This project explores an exchange onramp and offramp mechanism built using a state channels hub-and-spoke model, combined with a browser-based frontend. The goal is to enable users to deposit and withdraw tokens to and from their preferred exchanges instantly, without waiting for on-chain confirmations for every action.

At the core of the design is a central hub that maintains state channel connections with users (spokes). Users open a channel with the hub once, after which multiple off-chain balance updates can occur rapidly and at low cost. Only the final state needs to be settled on-chain, significantly reducing fees and latency.

The frontend focuses on simplicity and accessibility, allowing users to interact with the system without deep blockchain knowledge. While the current version is an early prototype and some flows are incomplete, the architecture is intentionally designed to be extensible. Future iterations will include stronger settlement guarantees, better exchange integrations, multi-chain support, and a more robust UX around deposits, withdrawals, and channel lifecycle management.

The project is built using a modern web-first architecture. The frontend uses Next.js with TypeScript and Tailwind CSS, providing a scalable and developer-friendly foundation. API routes are used as a backend layer to handle external integrations and abstract protocol complexity from the UI.

On the blockchain side, the system is conceptually designed around a state channels hub-and-spoke model, where users interact with a central hub to perform off-chain balance updates. This model reduces on-chain interactions while preserving the ability to settle disputes on-chain when needed.

External APIs (such as blockchain data and pricing services) are integrated to provide real-time information like gas prices and network context. Error handling and validation were intentionally explored early, which exposed several edge cases that will inform future iterations.

The most hacky and notable part is the emphasis on building the correct architecture first, even when features are incomplete. The project prioritizes a clean separation of concerns between UI, API logic, and protocol design, making it easier to iterate and evolve the system beyond the hackathon into a more production-ready exchange onramp/offramp solution.