📅 Original date posted:2018-11-12
📝 Original message:
On Wed, Nov 7, 2018 at 10:17 PM Anthony Towns <aj at erisian.com.au> wrote:
> On Wed, Nov 07, 2018 at 06:40:13PM -0800, Jim Posen wrote:
> > can simply close the channel. So if I'm charging for liquidity, I'd
> actually
> > want to charge for the amount (in mSAT/BTC) times time.
>
> So perhaps you could make a market here by establishing a channel saying
> that
>
> "I'll pay 32 msat per 500 satoshi per hour for the first 3 days"
>
> When you open the channel with 500,000 satoshi donated by the other guy,
> you're then obliged to transfer 32 satoshi every hour to the other guy
> for three days (so a total of 14c or so).
>
> If the channel fails beforehand, they don't get paid; if you stop
> paying you can still theoretically do a mutual close.
>
I think that this can also be gamed by a second, cooperating node that
sends payments through the channel to meet the rate and capture the fees
for the first. You can make this less likely by charging higher
transmission fees that make such an attack infeasible, and it's less
'damaging' than an immediate close in that there's still open capacity
available for some time, at least until the 'bogus' payments have drained
the capacity that you solicited in the first place.
> Maybe a complicated addition to the protocol though?
>
> Cheers,
> aj
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20181112/f34b2bd2/attachment.html>;
lisa neigut [ARCHIVE] /
npub1sp…s64t2
2023-06-09 12:52:19
in reply to nevent1q…wfvr
Author Public Key
npub1sprhp66c693av0c0n9had046hcdcckp2th25fnmphwstc5e4wg9qxs64t2Published at
2023-06-09 12:52:19Event JSON
{
"id": "278c8100c4362a93e9b3c978c5709635e0fe6fccb8b392b713c564df2539137e",
"pubkey": "804770eb58d163d63f0f996fd6bebabe1b8c582a5dd544cf61bba0bc5335720a",
"created_at": 1686315139,
"kind": 1,
"tags": [
[
"e",
"b6ccc150acd5efd7187e483388f4e01f13712f8edbcfde9936a99efec7233753",
"",
"root"
],
[
"e",
"c2ba9f3c0e4512ce1119622ede3cce621cbbf9fe0db876fdddb1a4d38d6d4e21",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2018-11-12\n📝 Original message:\nOn Wed, Nov 7, 2018 at 10:17 PM Anthony Towns \u003caj at erisian.com.au\u003e wrote:\n\n\u003e On Wed, Nov 07, 2018 at 06:40:13PM -0800, Jim Posen wrote:\n\u003e \u003e can simply close the channel. So if I'm charging for liquidity, I'd\n\u003e actually\n\u003e \u003e want to charge for the amount (in mSAT/BTC) times time.\n\u003e\n\u003e So perhaps you could make a market here by establishing a channel saying\n\u003e that\n\u003e\n\u003e \"I'll pay 32 msat per 500 satoshi per hour for the first 3 days\"\n\u003e\n\u003e When you open the channel with 500,000 satoshi donated by the other guy,\n\u003e you're then obliged to transfer 32 satoshi every hour to the other guy\n\u003e for three days (so a total of 14c or so).\n\u003e\n\u003e If the channel fails beforehand, they don't get paid; if you stop\n\u003e paying you can still theoretically do a mutual close.\n\u003e\n\nI think that this can also be gamed by a second, cooperating node that\nsends payments through the channel to meet the rate and capture the fees\nfor the first. You can make this less likely by charging higher\ntransmission fees that make such an attack infeasible, and it's less\n'damaging' than an immediate close in that there's still open capacity\navailable for some time, at least until the 'bogus' payments have drained\nthe capacity that you solicited in the first place.\n\n\n\u003e Maybe a complicated addition to the protocol though?\n\u003e\n\u003e Cheers,\n\u003e aj\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20181112/f34b2bd2/attachment.html\u003e",
"sig": "40cb278a44482c6a1d8b88b0889a420387bc121635c153ea49c80c0cdd211759f85e1a065fb1a90b37a8a2a28444b96872de026b4a3c4da46ae3d090c57c8ca3"
}