Esustellar is an open-source platform that brings informal savings groups (Esusu / Ajo / Rotating Savings) to the Stellar blockchain.
It helps communities save money together transparently, securely, and without relying on a single trusted organizer.
Millions of people use informal savings groups, but these systems rely entirely on trust:
- Organizers can disappear with funds
- No transparency into contributions
- No verifiable payout history
- Disputes are hard to resolve
EsuStellar uses the Stellar network to:
- Provide transparent, on-chain record-keeping for savings groups
- Automate payout rotation based on deterministic join order
- Enable peer accountability through public contribution tracking
- Reduce reliance on a single trusted organizer via smart contract logic
Note: Real token custody (locked escrow), dispute resolution, and configurable admin controls are planned for future releases. The current MVP records contributions and payouts on-chain but does not yet escrow funds within the contract.
- Create a savings group
- Join a group
- Fixed contribution amount
- Monthly contributions
- Rotating payout to members
- Transparent on-chain records
- Blockchain: Stellar (Testnet)
- Smart Contracts: Soroban
- Frontend: React / Next.js
- Wallet: Stellar Wallets (Freighter/lobster/lumen)
- Monorepo: npm / Turborepo
EsuStellar uses two Soroban smart contracts that work together:
The core contract that manages savings group lifecycle:
create_group— Admin creates a new group with contribution amount, member count, frequency, and start datejoin_group— Members join an open group. When the group is full, it transitions to Active and round 1 beginscontribute— Members contribute their fixed amount each round. When all members have contributed, payout is triggered automaticallydistribute_payout(internal) — Rotates payout to the next eligible member based on join order. Advances to the next round
A discovery/index layer for on-chain group metadata:
register_group— After creating a savings group, the admin registers it in the registry for frontend discoveryadd_member— Tracks which users belong to which groupsupdate_group_info— Re-syncs metadata when group state changes
1. Admin → savings::create_group(group_id, ...)
2. Members → savings::join_group(group_id) [repeat until full]
3. Admin → registry::register_group(contract_address, group_id, ...)
4. Members → savings::contribute(group_id) [each round]
5. Auto → savings::distribute_payout (triggered when all paid)
6. Repeat steps 4-5 for each round
Note: Registration is optional but recommended for frontend discovery. The savings contract operates independently of the registry.
esustellar/
├── apps/
│ └── web/ # Frontend application
├── contracts/
│ ├── savings/ # Soroban savings contract
│ └── registry/ # Soroban registry contract
├── environments/
│ └── testnet/ # Testnet deployment workspace
├── packages/
│ └── shared/ # Shared types & utils
├── docs/ # Architecture & specs
├── .github/
│ └── ISSUE_TEMPLATE/
└── README.md
- Loki & Grafana: Centralised log aggregation is pre-configured via Docker Compose (
docker-compose.yml) and Kubernetes (k8s/monitoring/). - Validation: Run
npm run validate-monitoringto verify log aggregation configurations. - Documentation: See docs/logging.md.
- Post-Deploy Smoke Tests:
npm run smoke-test(automatically invoked after./deploy.sh). - Export & Archive Contract Event Logs:
npm run export-events(exports events tologs/contract-events.jsonl). - Deployment Guide: See docs/deployment.md.
EsuStellar is open-source and beginner-friendly.
- Look for issues tagged
good first issue - Follow the contribution guide (coming soon)
- Open discussions for ideas and improvements
MIT License