š
Original date posted:2020-01-27
š Original message:
Hey Subhra ā In order to have faith that the channel announced by the nodes is actually locked on the Bitcoin mainchain we need to have the outpoint (`txid` and `vout`) of the funding transaction. If we do not verify that the funding transaction has been confirmed, nodes can cheat us that a particular transaction is confirmed when it is not the case. As a result we require that nodes announce this information along with the public keys and the signatures of the public keys that was used to lock the funding transaction.
This information is broadcasted in the `channel_announcement` message in the `short_channel_id` field which includes the block number, transaction number and vout. Since Bitcoin does not allow confidential transactions, we can query the blockchain and find out the channel capacity even when the amounts are never explicitly mentioned.
Ugam
From: Lightning-dev <lightning-dev-bounces at lists.linuxfoundation.org> On Behalf Of Subhra Mazumdar
Sent: Monday, January 27, 2020 12:45 PM
To: lightning-dev at lists.linuxfoundation.org
Subject: [Lightning-dev] Not revealing the channel capacity during opening of channel in lightning network
Dear All,
What can be the potential problem if a channel is opened whereby the channel capacity is not revealed publicly but just a range proof of the attribute (capacity >0 and capacity < value) is provided ? Will it pose a problem during routing of transaction ? What are the pros and cons ?
I think that revealing channel capacity make the channels susceptible to channel exhaustion attack or a particular node might be targeted for node isolation attack ?
--
Yours sincerely,
Subhra Mazumdar.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20200127/cf9b0f81/attachment-0001.html>;
Ugam Kamat [ARCHIVE] /
npub1fwā¦2z20k
2023-06-09 12:58:14
in reply to nevent1qā¦r8um
Author Public Key
npub1fw9jwk4jmln0ypqe25y8xrg09elwteedpcrdl69g6nzd9yqw44es52z20kPublished at
2023-06-09 12:58:14Event JSON
{
"id": "bacf0b1f8fe4e77b3c766f8c19faf7a28984670632a0cac7d624a36d5ebed026",
"pubkey": "4b8b275ab2dfe6f204195508730d0f2e7ee5e72d0e06dfe8a8d4c4d2900ead73",
"created_at": 1686315494,
"kind": 1,
"tags": [
[
"e",
"d0c00323a09eb4da07465985f3eb7cafe8f64c287953e0e921fafc89b71ea038",
"",
"root"
],
[
"e",
"4d1e553b05bb7aae5be0a6d9bdd3984250929e385f9cc4f1f8b3fdf91ea32c50",
"",
"reply"
],
[
"p",
"84dde5d7bce077e7cd64c91dc102677e13acc29126ce3f889bb9d2b2f81b200a"
]
],
"content": "š
Original date posted:2020-01-27\nš Original message:\nHey Subhra ā In order to have faith that the channel announced by the nodes is actually locked on the Bitcoin mainchain we need to have the outpoint (`txid` and `vout`) of the funding transaction. If we do not verify that the funding transaction has been confirmed, nodes can cheat us that a particular transaction is confirmed when it is not the case. As a result we require that nodes announce this information along with the public keys and the signatures of the public keys that was used to lock the funding transaction.\n\n \n\nThis information is broadcasted in the `channel_announcement` message in the `short_channel_id` field which includes the block number, transaction number and vout. Since Bitcoin does not allow confidential transactions, we can query the blockchain and find out the channel capacity even when the amounts are never explicitly mentioned. \n\n \n\n \n\nUgam\n\n \n\nFrom: Lightning-dev \u003clightning-dev-bounces at lists.linuxfoundation.org\u003e On Behalf Of Subhra Mazumdar\nSent: Monday, January 27, 2020 12:45 PM\nTo: lightning-dev at lists.linuxfoundation.org\nSubject: [Lightning-dev] Not revealing the channel capacity during opening of channel in lightning network\n\n \n\nDear All,\n\n What can be the potential problem if a channel is opened whereby the channel capacity is not revealed publicly but just a range proof of the attribute (capacity \u003e0 and capacity \u003c value) is provided ? Will it pose a problem during routing of transaction ? What are the pros and cons ?\n\nI think that revealing channel capacity make the channels susceptible to channel exhaustion attack or a particular node might be targeted for node isolation attack ? \n\n\n-- \n\nYours sincerely,\nSubhra Mazumdar.\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20200127/cf9b0f81/attachment-0001.html\u003e",
"sig": "92d1a1884604fe7447c91194bb7a2741e74bf59bfd4e4bf3b9aaf99035a412cd5dbd2c9876b5e60eda31697bda23b024a043ecb13e40fa11b3504aaa1a670368"
}