Oracler V2
Cross-chain web application- PERIOD
- 07.2025 — 11.2025
- ROLE
- Architecture & tech lead
- TEAM
- 3
- STACK
- Next.js · NestJS · PostgreSQL · Redis · Docker · CI/CD
- LINK
- oracler.co ↗
[ screenshot — oracler.co — swap screen ]
One unified experience to swap and send tokens across multiple chains — integrating third-party services while staying fast, stable and ready to scale in production.
What I did
- Led system architecture and set the technical direction for a production-ready cross-chain app.
- Owned the core swap & send flows with strict, accurate business-logic handling.
- Built CI/CD pipelines and the cloud deployment strategy for reliable releases and monitoring.
- Reviewed and guided the team to hold the bar on quality, performance and security.
01 Problem
Moving tokens across chains means juggling bridges, aggregators and wallets — each with its own flow, fees and failure modes.
02 Approach
One swap & send flow on top of third-party providers, a NestJS API with Redis caching, PostgreSQL for state, and CI/CD with monitoring for safe releases.
03 Result
A production cross-chain app, live at oracler.co. [add a metric if you can share one]
One adapter layer for every provider
Quotes and routes from each provider are normalized behind a single internal interface, so providers can be added or swapped without touching the core swap logic.