W3C home > Mailing lists > Public > public-interledger@w3.org > March 2016

Re: Thoughts on Discovery

From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Wed, 30 Mar 2016 14:51:08 +0200
Message-ID: <CA+eFz_LH+90aB-xZEzBKWdoggGnxbckYk95cGzrpt-HobJvDZg@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Xavier Vas <xavier@tr80.com>, Interledger Community Group <public-interledger@w3.org>
So you're suggesting that the answer to resolving an account identifier
(URI) to a ledger URL is to query every known ledger and find out if the
account exists in that ledger?

I'm not sure that's scales very well.

On 30 March 2016 at 12:55, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

>
>
> On 30 March 2016 at 10:02, Adrian Hope-Bailie <adrian@hopebailie.com>
> wrote:
>
>>
>>
>> On Tuesday, March 29, 2016, Melvin Carvalho <melvincarvalho@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On 29 March 2016 at 21:47, Adrian Hope-Bailie <adrian@hopebailie.com>
>>> wrote:
>>>
>>>> What is a super-ledger? It sounds like you're suggesting that the whole
>>>> world should all just use a single ledger which seems pretty hard to scale
>>>
>>>
>>> I mentioned it in another thread.  A super ledger is a ledger where
>>> every entry is a URI.  Just as URIs are sometimes called "super keys".  All
>>> of the ledgers Im working with are are super ledgers.
>>>
>>
>> How does the URI resolve to the address of the super-ledger?
>>
>> Do I need to query every super ledger to find the account I'm looking for?
>>
>
> Yes exactly.  There can be many super ledgers.  Hence the need for inter
> ledger transactions.  If a URI is in two different super ledgers it can
> then act as a connector.
>
>
>>
>>
>>>
>>>
>>>>
>>>>
>>>> On Tuesday, March 29, 2016, Melvin Carvalho <melvincarvalho@gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On 29 March 2016 at 16:47, Adrian Hope-Bailie <adrian@hopebailie.com>
>>>>> wrote:
>>>>>
>>>>>> On 29 March 2016 at 16:32, Melvin Carvalho <melvincarvalho@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 29 March 2016 at 15:48, Adrian Hope-Bailie <adrian@hopebailie.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> This is a higher level function.
>>>>>>>> I.e. I give you some identifier for my account like
>>>>>>>> adrian@mywalletprovider.com and you have a well-defined protocol
>>>>>>>> to resolve the address of my ledger from that.
>>>>>>>>
>>>>>>>
>>>>>>> Have a look what happens when I hover over the link you pasted
>>>>>>> (image attached)
>>>>>>>
>>>>>>> firefox automatically translates it into mailto:
>>>>>>>
>>>>>>> this denotes an email address using a URI
>>>>>>>
>>>>>>>
>>>>>> Right, because in the context of an email program it makes sense to
>>>>>> normalize that to a mailto: URI.
>>>>>>
>>>>>>
>>>>>>> so how do you send money to an email address, this becomes a trivial
>>>>>>> problem with a super ledger, you just send it to the URI
>>>>>>>
>>>>>>
>>>>>> How? I'm not following how I would send money to a mailto: URI?
>>>>>>
>>>>>
>>>>> In a super ledger every entry is a URI, so you just have the mailto:
>>>>> address as the recipient.  Problem solved.
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Following which you will do path finding to my ledger.
>>>>>>>>
>>>>>>>> If ILP is TCP/IP then we're trying to figure out a good way to do
>>>>>>>> DNS :)
>>>>>>>>
>>>>>>>> On 29 March 2016 at 15:26, Xavier Vas <xavier@tr80.com> wrote:
>>>>>>>>
>>>>>>>>> Adrian,
>>>>>>>>>
>>>>>>>>> Sorry, I'm confused, how's this discussion separate from our
>>>>>>>>> discussions
>>>>>>>>> on path finding and routing? How exactly do you define "discovery"
>>>>>>>>> vs.
>>>>>>>>> "path finding"?
>>>>>>>>>
>>>>>>>>> Xav
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Sent from a mobile device, please excuse any typos
>>>>
>>>
>>>
>>
>> --
>> Sent from a mobile device, please excuse any typos
>>
>
>
Received on Wednesday, 30 March 2016 12:51:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 12:51:54 UTC