public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'hodlinator' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Re: Draft BIP: Well-Known Bitcoin Identity Endpoint
Date: Mon, 2 Jun 2025 11:20:06 -0700 (PDT)	[thread overview]
Message-ID: <e1455c9f-2954-4208-bb1b-5e55027d9d6dn@googlegroups.com> (raw)
In-Reply-To: <dc2e77df-24cc-40e0-bd6b-54b8f8bac60en@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1616 bytes --]

(Reading further down in your proposal I see you do acknowledge BIP 353 and 
the arguments laid out there, sorry for the noise).

On Monday, June 2, 2025 at 3:54:05 PM UTC+2 hodlinator wrote:

> Hi AvivB,
>
> Something similar has been discussed here in BIP 353: 
> https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki#dns-rather-than-http-based-solutions
>
> Cheers,
> Hodlinator
>
> On Monday, May 26, 2025 at 2:52:02 PM UTC+2 Aviv Bar-el wrote:
>
>> Hi all,
>>
>> I'd like to propose a new BIP titled "Well-Known Bitcoin Identity 
>> Endpoint."
>> The goal is to improve the user experience for sending on-chain Bitcoin 
>> payments by allowing wallets to resolve a Lightning Address into associated 
>> on-chain addresses and additional metadata.
>>
>> The idea is to define a simple, HTTPS-based standard for retrieving 
>> payment and contact information via a .well-known endpoint,
>> generalizing the approach used by Lightning Address to support more 
>> payment types and identity metadata.
>>
>> You can find the draft BIP here: 
>> https://github.com/aviv57/paysats/blob/main/bip/BIPXXX.MD
>>
>> I’d appreciate any feedback or suggestions.
>>
>> Thanks,
>> AvivB
>>
>

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/e1455c9f-2954-4208-bb1b-5e55027d9d6dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3045 bytes --]

  reply	other threads:[~2025-06-02 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 12:50 [bitcoindev] Draft BIP: Well-Known Bitcoin Identity Endpoint Aviv Bar-el
2025-06-02 12:40 ` [bitcoindev] " 'hodlinator' via Bitcoin Development Mailing List
2025-06-02 18:20   ` 'hodlinator' via Bitcoin Development Mailing List [this message]
2025-06-02 19:32 ` [bitcoindev] " Murch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1455c9f-2954-4208-bb1b-5e55027d9d6dn@googlegroups.com \
    --to=bitcoindev@googlegroups.com \
    --cc=github_alias@proton.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox