[continued]
3 We use a 2 tier lookup format. The first lookup returns a list of
currencies or payment types supported by the Wallet Name. The second
lookup goes to a record specific to that currency type to get the
address to go to. We believe this to be a more scalable solution in a
Thomas,
I think this is interesting and has some good thoughts behind it. For
clarity, are you recommending that the _oa2 portion of the domain name be
hidden as a way to make it easier to delegate just wallet names from a
zone?
On Thu, Jul 23, 2015 at 6:07 AM, Thomas Voegtlin via
[CONTINUED]
Additionally, we just released another open source API server to help
with the other half of the lookup problem. Its in its infancy, and
we are certainly taking feedback on it at this time. It is called
Addressimo https://github.com/netkicorp/addressimo and will serve
unique
[continued]
3 We use a 2 tier lookup format. The first lookup returns a list of
currencies or payment types supported by the Wallet Name. The second
lookup goes to a record specific to that currency type to get the
address to go to. We believe this to be a more scalable solution in a
On Tue, Jun 21, 2016 at 3:13 PM, Peter Todd via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Mon, Jun 20, 2016 at 05:33:32PM +, Erik Aronesty via bitcoin-dev
> wrote:
>
> > - missing an optional client supplied identification
>
> Note that "client supplied identification"
On Thu, Jun 23, 2016 at 1:46 PM, s7r via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>
>
> Any kind of built-in AML/KYC tools in Bitcoin is bad, and might draw
> expectations from _all_ users from authorities. Companies or individuals
> who want and/or need AML/KYC can find ways
is not a defense when served with a police
> notice for disclosing data.
>
> You have to think not only about the end result, but also about how
> these mechanisms can be used for intimidating users or leveraging
> technologies.
>
> Justin Newton via bitcoin-dev:
> > O
The following draft BIP proposes an update to the Payment Protocol.
Motivation:
The motivation for defining this extension to the BIP70 Payment Protocol is
to allow 2 parties to exchange payment information in a permissioned and
encrypted way such that wallet address communication can become a
https://www.walletnames.com
Based on a standard that can support blockchain based or traditional ICANN
DNS.
On Fri, Dec 1, 2017 at 6:20 AM, mandar mulherkar via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> I am new, so apologies if this has been asked before.
>
>
