bip353 draft

[securitybrahh]

Hi, I hacked up a rough draft for bip353 support, I will need to make a PR on the firmware side as well,

But first I wanted to know if the maintainers and developers are okay for implementation of bip353, silent payment and bolt12 lightning offer?

This is a very rough draft, you will ofcourse merge when I have tested it thouroughly on my colcard and the implemenation is complete.

But as I said, first, I needed some confirmation that I can do it, because I don't want to work on it if you guys will refuse the PR in the future.

References:

https://x.com/TheBlueMatt/status/1945603864666743240?s=20

https://bips.dev/353/

https://bitcoin.design/guide/how-it-works/human-readable-addresses/

https://sethforprivacy.com/guides/setting-up-a-bitcoin-username/

https://satsto.me/

lightning/bolts#1180

Software Wallet Support:

Electrum: Will make an external plugin

sparrowwallet/sparrow#1667

[nvk]

DNS is a permissioned, censorable namespace. Your payment identity lives at the mercy of your domain registrar and ICANN. Domains get seized routinely — Tornado Cash, Garantex, etc. A payment standard that can be revoked by a registrar or court order is a poor fit for Bitcoin.
DNSSEC trust chain terminates at ICANN/IANA, a US-government-adjacent organization (root KSK managed by PTI under ICANN, ZSK operated by Verisign). The entire security model depends on trusting this root. That’s a hard sell for a product whose whole point is removing third-party trust.
DNSSEC proof validation on constrained hardware adds complexity. While BIP353’s PSBT field means the COLDCARD wouldn’t need to do DNS resolution itself, it would still need to validate the full DNSSEC proof chain (RSA signatures, chain of trust to root). That’s meaningful code surface for a feature with questionable benefit over existing approaches (QR codes, NFC, PSBTs).

Silent Payments (BIP352) solves the reuse problem without DNS. The address rotation concern that BIP353 tries to address is handled more cleanly by SP, which we’re already evaluating.

We’d rather invest firmware effort into protocols that don’t introduce new trusted third parties.

[securitybrahh]

Silent Payments (BIP352) solves the reuse problem without DNS. The address rotation concern that BIP353 tries to address is handled more cleanly by SP, which we’re already evaluating

Let me know if you got any chats running where you are discussing or any open PR/Issues I can help with.

I am working on electrum plugin for SP here:

https://github.com/securitybrahh/silentpayments-electrum

[scgbckbone]

External PR against EDGE firmware branch Coldcard/firmware#587