📅 Original date posted:2015-09-01
📝 Original message:
Anthony Towns schreef op di 01-09-2015 om 17:56 [+1000]:
> On 1 September 2015 at 17:07, CJP <cjp at ultimatestunts.nl> wrote:
>
> Anthony Towns schreef op di 01-09-2015 om 07:08 [+1000]:
> > On 31 August 2015 at 04:01, CJP <cjp at ultimatestunts.nl>
> wrote:
> > > A - b - c - D - e - F - g - H
> No. H just tells A he can route this particular transaction to
> D. A
> doesn't know H.
>
>
> That doesn't make sense to me -- if A doesn't know H, how can H tell
> A anything?
Sorry, that must have been confusing.
The way I see it (and the way it's implemented in Amiko Pay), payer and
payee (A and H in the scenario) have a direct communication link between
each other (temporary, for the duration of the payment), to coordinate
the payment. They exchange things like the hash of R, the to-be-paid
amount and the address of the meeting point (D).
Currently, it's a normal TCP connection, so they know each others' IP
address, but I guess that, even without changes to the Amiko Pay code,
you could run Amiko Pay as a TOR hidden service (payer connects to
payee, so payee has to be the hidden service). Or they could meet each
other physically (without knowing each other), and communicate over a
temporary link (WiFi, Bluetooth or something else).
There is no technical reason why they should know each others' identity,
IP address or any routable address on the Lightning / Amiko network.
I guess your further questions followed from this issue. Is it all clear
now?
CJP
>
CJP [ARCHIVE] /
npub13q…cuzdm
2023-06-09 12:44:18
in reply to nevent1q…4rvh
Author Public Key
npub13q863scgpsaanrjhfn7dd4h48lgnupgkcs828arzj4pckrq8hh6s4cuzdmPublished at
2023-06-09 12:44:18Event JSON
{
"id": "efd391ce5721a8e22d2c29aa763afe48db75e18640ad3219073bc6a9c7f67e32",
"pubkey": "880fa8c3080c3bd98e574cfcd6d6f53fd13e0516c40ea3f46295438b0c07bdf5",
"created_at": 1686314658,
"kind": 1,
"tags": [
[
"e",
"428192df74a2b1222798f1b35346001f531f739da9c977185afdc53f6ee5537c",
"",
"root"
],
[
"e",
"4884431d3554e44e09d636d9ee55298cc0ff79898e6c11d9217d85a755cb596b",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2015-09-01\n📝 Original message:\nAnthony Towns schreef op di 01-09-2015 om 17:56 [+1000]:\n\u003e On 1 September 2015 at 17:07, CJP \u003ccjp at ultimatestunts.nl\u003e wrote:\n\u003e \n\u003e Anthony Towns schreef op di 01-09-2015 om 07:08 [+1000]:\n\u003e \u003e On 31 August 2015 at 04:01, CJP \u003ccjp at ultimatestunts.nl\u003e\n\u003e wrote:\n\u003e \u003e \u003e A - b - c - D - e - F - g - H\n\u003e No. H just tells A he can route this particular transaction to\n\u003e D. A\n\u003e doesn't know H.\n\u003e \n\u003e \n\u003e That doesn't make sense to me -- if A doesn't know H, how can H tell\n\u003e A anything?\n\nSorry, that must have been confusing.\n\nThe way I see it (and the way it's implemented in Amiko Pay), payer and\npayee (A and H in the scenario) have a direct communication link between\neach other (temporary, for the duration of the payment), to coordinate\nthe payment. They exchange things like the hash of R, the to-be-paid\namount and the address of the meeting point (D).\n\nCurrently, it's a normal TCP connection, so they know each others' IP\naddress, but I guess that, even without changes to the Amiko Pay code,\nyou could run Amiko Pay as a TOR hidden service (payer connects to\npayee, so payee has to be the hidden service). Or they could meet each\nother physically (without knowing each other), and communicate over a\ntemporary link (WiFi, Bluetooth or something else).\n\nThere is no technical reason why they should know each others' identity,\nIP address or any routable address on the Lightning / Amiko network.\n\nI guess your further questions followed from this issue. Is it all clear\nnow?\n\nCJP\n\n\u003e",
"sig": "9015e75f3dbddd1dca4b73b91eade6c65344352898bfee4fda1b4d1d952132c86daecef2bed233fec2ae833c519bf80b3113a8868d2f1d21e9deff3b591bd8c2"
}