Phase 2 — Dual-mode receiving and sweeping bridge - Dual en…

Phase 2 — Dual-mode receiving and sweeping bridge
- Dual endpoints:
- BRC100-native requests: expose context-rich payment requests (with the context string or handle the handshake so the payer can derive the same context key on their side if needed by the protocol).
- Legacy fallback: present a standard BSV address (or paymail) for non-BRC100 senders.
- Sweeper service (automated): when a legacy payment lands, immediately sweep to a BKDS-controlled UTXO that corresponds to the intended context, tagging the move in your wallet DB.
- Guardrails: enforce min-confirmation or use your risk engine for 0-conf sweeps; set fee/size limits; avoid combining unrelated contexts in a single sweep.
- UX: clearly label deposits as "Legacy (bridged)" vs "BRC100-native" to help support and reconciliation.