Payments on the Stellar network happen in the blink of an eye. This is how we watch them happen — in real time, with charts that don't lie and a backend that doesn't sleep. 🛰️
Think of it as mission control for cross-border payments: we ingest the ledger, crunch the numbers, and hand you a dashboard that actually tells you something.
| Piece | What it does | Built with |
|---|---|---|
⚙️ backend/ |
Chews through Stellar ledger data and serves it back up hot | Rust |
🖥️ frontend/ |
The dashboard you actually look at | Next.js |
📜 contracts/ |
On-chain logic, for when off-chain isn't trustless enough | Soroban |
| 🗄️ Database | Where all those numbers go to rest | PostgreSQL |
1. Wake up a Postgres instance
docker run --name stellar-postgres -e POSTGRES_PASSWORD=password -e POSTGRES_DB=stellar_insights -p 5432:5432 -d postgres:142. Fire up the backend 🔥
cd backend
cp .env.example .env
# fill in DATABASE_URL, STELLAR_RPC_URL, etc. — the backend will yell at you if you forget
cargo run3. Bring the dashboard to life 🎨
cd frontend
pnpm install
pnpm devOpen it up, watch the numbers move. That's it — you're now watching the Stellar network breathe. 🫁
scripts/check_folder_size.sh— the bouncer that stops any folder from sneaking past 200MB.github/workflows/enforce-folder-size.yml— same bouncer, but for CI
backend/ ⚙️ Rust services — the engine room
frontend/ 🖥️ Next.js dashboard — the pretty part
mobile/ 📱 React Native app — Stellar Insights in your pocket
contracts/ 📜 Soroban contracts — trust, but verify on-chain
docs/ 📚 Everything we wrote down so you don't have to ask
- Repo history has been trimmed down so cloning doesn't take a coffee break.
- Big binaries live in
git lfs, not in yourgit log. - For the deep-dive stuff — architecture, deployment, "why did we do it this way" — check
docs/and the READMEs living inside each folder.
Made with 🦀, ☕, and an unreasonable love for clean ledgers.