The idea
TontineKit helps organizers keep track of savings-circle members, contribution schedules, entries, and round close-outs in one place. We began with a problem hypothesis: reconciling who contributed, what remains outstanding, and how a round closed can be difficult to explain when records are scattered.
We have not yet interviewed local organizers, so we do not claim this problem or the app’s impact is validated. The fictional sample workspace in the demo illustrates the workflow; its names and amounts are not real user data or evidence of adoption.
What we built
Organizers can create circles, manage members and payout order, record flexible contributions, review activity and analytics, import a ledger, and reconcile a round. The app also includes member views for schedules and contribution records, along with confirmation, dispute, and correction history.
Bitcoin is an optional part of the payout workflow. An organizer can connect a wallet through Sats Connect and approve a Bitcoin Signet transfer. The transaction ID and its Signet receipt status can be linked to a closed-round record and checked against a public Signet explorer.
The XOF ledger and Bitcoin transaction remain separate. A Signet transaction shows activity on Bitcoin’s test network; it does not prove that an XOF contribution or mobile-money payment settled. Signet coins have no real-world value, and TontineKit does not hold or convert funds.
How we built it
The web app uses React and TypeScript. Firebase Authentication handles sign-in; a Cloudflare Workers API verifies user identity and scopes requests; Neon Postgres stores circle records. Sats Connect requests wallet approval for Signet transfers, and the Worker checks transaction receipts using a public Signet explorer.
What we learned
A useful record needs to distinguish what an organizer entered, what a member confirmed, and what was verified on Signet. Combining those labels would make the ledger less trustworthy. Wallet support and explorer indexing can also vary, so the app must show pending or unavailable states without claiming a transaction succeeded.
Challenges and next steps
The main challenge was connecting an optional Bitcoin transaction to a circle’s payout record without implying that Bitcoin settled the XOF pool. The wallet controls its keys and asks the organizer to review the recipient, amount, and network fee; TontineKit never asks for a recovery phrase.
Next, we want to validate the workflow with circle organizers and members. A pilot should measure round-reconciliation time, missing or duplicate entries, correction frequency, and usability on slower connections. Those results should guide changes before we make claims about impact.
Built With
- bitcoin
- bitcoin-signet
- cloudflare
- firebase-authentication
- neon-postgres
- react
- sats-connect
- typescript