Chaindustry
Full-Stack Engineer & Team Lead
Task-to-earn platform · Since 2024 · Live
Chaindustry pays users for completing online micro-tasks. I owned the frontend architecture end to end, from the component system and state layer through API integration and deployment, and led a team of six engineers through sprint planning and code review. The hard part was not the task feed; it was keeping a real-time, heavily-interactive dashboard fast while six people shipped into it every week.
The problem
Users need to see task availability, completion state, and reward balances update live, without the interface stalling as the number of concurrent tasks grows.
Architecture
- Client
- Next.js and TypeScript. Shared component system consumed by six engineers; responsive from small phones through desktop.
- State
- Redux Toolkit with RTK Query. Auto-generated hooks and a normalised cache meant repeat views of the task feed and leaderboard cost no extra requests.
- API
- REST against a Node.js backend, plus a third-party bridge API for converting earned tokens to USDT.
- Data
- MongoDB.
- Auth
- JWT with managed session lifetime and protected routes.
Decisions
The dashboard re-rendered on every reward tick
Reward balances update frequently, and the initial implementation propagated each update through the whole task list. Memoising list rows and moving to RTK Query's cache-first reads cut redundant requests and re-renders, taking roughly 30% off page load.
Six engineers, one interface
Rather than review styling in pull requests, the component system made the correct thing the easy thing. Sprint planning and architecture review handled the rest, and the codebase stayed consistent without a style police step.
Payouts had to leave the platform
Earned tokens are only useful if they convert. Integrating a third-party bridge/swap API for token → USDT kept the conversion out of our own custody while still reading as one flow to the user.
Outcomes
- ~30% faster page load after memoisation and request-pattern work
- Led six engineers through sprint planning, architecture review, and code review
- Token → USDT conversion shipped via third-party bridge integration
Built with
- Next.js
- TypeScript
- Redux Toolkit
- RTK Query
- Node.js
- MongoDB
- Tailwind CSS
- JWT
Screens
