3.2 payment receipt
Discussion
3.3 reputation event commit
3.4 peer attestation
all events are signed locally and sent to any number of Nostr relays
4. reputation scoring
the wallet computes a five-vector reputation vector:
each updated via deterministic client rules:
final aggregate reputation is:
weights are public, transparent and updatable via Bitcoin Crown governance
5. bitcoin module
supports:
lightning
LNURL
Keysend
Bolt11 payments
L402 credential-bound payments
on-chain
P2WPKH
P2TR
PSBT signatures
optional coin-control
spend event
every spend can optionally emit a zk-contribution proof:
commit is published to Nostr → anchored to Bitcoin Crown Ledger → verified globally.
6. ZK proof layer
the app uses three ZK primitives:
1. ZK Contribution Proof (ZKCP)
proves contributions without disclosing amount
2. ZK Reputation Membership
proves reputation category membership:
ZK{ R_total ≥ R_threshold }
3. ZK Attestation Validity
verifies an attestation came from a legitimate participant without revealing identity
all proofs are client-side, producing only commitments for Nostr broadcast.
7. minimal protocol flow
7.1 send bitcoin
ASCII:
7.2 receive bitcoin
7.3 reputation update
8. security model
immutability
Nostr proofs commit to:
these commit hashes anchor into the Bitcoin Crown Ledger → Bitcoin finality.
privacy
all event data is ZK-masked. Raw values never leave the device.
sybil resistance
Uses BSRL heuristics:
no custody risk
keys never leave device. no servers store funds.
9. reference implementation (minimal code)
fully functional skeleton in TypeScript for a Nostr + Bitcoin wallet:
this is the minimum working version for:
✔ sending BTC
✔ generating ZK proofs
✔ publishing reputation events over Nostr
10. conclusion
this client defines the minimal trustless interaction layer between:
Bitcoin payments
Nostr messaging
the Bitcoin Crown Fiscal Protocol
the Bitcoin Social Reputation Layer