From 539dfbe596cdd280f801aaaea949bbd025e71ad7 Mon Sep 17 00:00:00 2001 From: Seth For Privacy <40500387+sethforprivacy@users.noreply.github.com> Date: Mon, 15 Jul 2024 15:59:31 +0000 Subject: [PATCH] Direct readers to silentpayments.xyz for more info --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index b11eeaa..608f3c2 100644 --- a/index.html +++ b/index.html @@ -206,7 +206,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.

+

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!

Trust someone else to host a name for you? Check out twelve.cash

Make this site beautiful by editing it on Github

-- 2.39.5