SettleProof helps businesses know when a crypto payment is safe to act on without trusting one RPC provider.
Submit the expected payment. SettleProof checks multiple RPC providers and handles provider disagreement with quorum rules before your system acts on the payment.
- A stale RPC response can make a paid customer look unpaid.
- A bad provider response can make an unpaid invoice look paid.
- Manual block explorer checks do not scale for support, ops, or compliance.
- Custodial processors reduce this burden by taking control of funds.
- Accepts verification tasks over an API.
- Checks the same expected payment across multiple RPC providers.
- Confirms only when enough providers agree on the same on-chain event.
- Keeps an evidence trail for reconciliation and audit.
Callback delivery is the next MVP gap.
SettleProof fits teams that accept crypto directly and need a reliable payment-status signal before they ship goods, unlock access, credit an account, or close an invoice.
Good early users:
- SaaS and e-commerce teams accepting stablecoin payments.
- Payment processors and fintech infrastructure teams.
- Exchanges, wallets, and custodians that need redundant transaction checks.
- DAO and treasury operators that need settlement evidence.
This project is being productized from a hackathon demo. The MVP priority is not a broad payment gateway. The priority is one product promise:
SettleProof should not mark a payment confirmed from a single source of truth.
Implemented first:
- REST endpoint for submitting payment-verification tasks.
- SQLite-backed task and status-history persistence.
- Verification reads pending SQLite tasks instead of mock invoice JSON.
- Multi-RPC quorum checks for ERC20 transfer settlement.
Remaining MVP work:
- Callback delivery when task status changes.
- Local devnet integration tests that simulate multiple RPC providers.