From 5423171a22146dde4ca44ab014dd88113f8e4f5f Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Sat, 13 Jul 2024 15:27:57 +0000 Subject: [PATCH] Add a brief snippet on what BIP 353 does and sample address --- index.html | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/index.html b/index.html index 1b49b2b..68665d6 100644 --- a/index.html +++ b/index.html @@ -97,6 +97,10 @@ color: grey; font-size: 11pt; } + .mono { + font-family: mono; + font-size-adjust: 0.5; + } .small-print { color: white; font-size: 11pt; @@ -175,6 +179,7 @@
+

BIP 353 resolves DNS TXT records into bitcoin: URIs. Any standard (reusable) bitcoin: URI should work, for example a URI with a BOLT 12 offer (starting with lno), a Silent Payments Address (starting with sp), and an on-chain address may look like bitcoin:1OnChain?lno=lno1lightningoffer&sp=sp1qsilentpayment

Note that most BIP 353 names rely on BOLT 12 or Silent Payments and as both are relatively new, wallet support isn't yet universal.

While you're absolutely trusting this site to not provide you with backdoored code, names are fully validated locally on your machine using DNSSEC. Thus, no matter what server you use to resolve the name, the worst they can do is log who you're paying or tell you they're not payable. They can never give you the wrong address!

Make this site beautiful by editing it on Github

-- 2.39.5