finalis-mint So far it's just a concept with a basic setup. The code and ideas are available for everyone. I'm looking for various opinions and help.
This is a simple standalone Chaumian mint boundary service meant for local development and integration.
The service operates independently of consensus. It uses JSON contracts outlined in:
[*] the HTTP handlers found in server.py
[*] the finalized-state lightserver surface detailed in LIVE_PROTOCOL.md
It’s just a basic framework, definitely not for production use:
[*] file-based state
[*] deterministic RSA blind-signing designed for development/testing
[*] persistent issuance ledger
[*] endpoints for reserve and accounting summary
[*] inventory/fragmentation reporting for reserve wallets
[*] coin selection policy for max-input and reserve alerts
[*] automatic redemption handling using a configured reserve wallet
[*] lightserver-based redemption finalization (pending -> broadcast -> finalized/rejected)
[*] HMAC-signed admin requests for operators
[*] persistent job queue for notifier delivery
[*] optional single-worker lock for draining the queue
[*] notifier secret references handled through a pluggable secret backend
[*] signed reserve attestations and audit exports
[*] no federation
[*] no multi-operator quorum custody
Endpoints
[*] POST /deposits/register
[*] POST /issuance/blind
[*] POST /redemptions/create
[*] POST /redemptions/approve_broadcast
[*] POST /reserves/consolidate
[*] POST /redemptions/status
[*] POST /redemptions/update
[*] POST /policy/redemptions
[*] GET /healthz
[*] GET /mint/key
[*] GET /reserves
Simple standalone Chaumian mint boundary service
0 replies 79 views