From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Billy Tetrud <billy.tetrud@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proof of reserves - recording
Date: Mon, 05 Jul 2021 23:26:23 +0000 [thread overview]
Message-ID: <cLK-RFlIdmwOvuKag-cOImIVCltq97EWfT-mFpPFa5wJfbAgptlKFhmgt4WQNw2pYVt-sGCCCTtHi1s0Vdwwimun_fUdvrDeOOPnlFjYDdA=@protonmail.com> (raw)
In-Reply-To: <CAGpPWDbTyxMRxX4NM8C3H5+d5+H2PLcnVg_8hw8=TsBgOxLtLA@mail.gmail.com>
Good morning Billy,
> I wonder if there would be some way to include the ability to prove balances held on the lightning network, but I suspect that isn't generally possible.
Thinking about this in terms of economic logic:
Every channel is anchored onchain, and that anchor (the funding txout) is proof of the existence, and size, of the channel.
The two participants in the channel can sign a plaintext containing their node pubkeys and how much each owns.
One of the participants should provably be the custodian.
* If the counterparty is a true third party, it has no incentive to lie about its money.
* Especially if the counterparty is *another* custodian who wants proof-of-reserves, it has every incentive to overreport, but then the first party will refuse to sign.
It has a disincentive to underreport, and would itself refuse to sign a dishonest report that assigns more funds to the first party.
The only case that would be acceptable to both custodians would be to honestly report their holdings in the Lightning channel.
* If the counterparty is a sockpuppet of the custodian, then the entire channel is owned by the custodian and it would be fairly dumb of he custodian to claim to have less funds than the entire channel.
Perhaps a more practical problem is that Lightning channel states change fairly quickly, and there are possible race conditions, due to network latency (remember, both nodes need to sign, meaning both of them need to communicate with each other, thus hit by network latency and other race conditions) where a custodian Lightning node is unable to "freeze" a snapshot of its current state and make an atomic proof-of-reserves of *all* channels.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2021-07-05 23:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 18:24 Billy Tetrud
2021-07-05 23:26 ` ZmnSCPxj [this message]
2021-07-05 23:32 ` Eric Voskuil
2021-07-06 0:09 ` ZmnSCPxj
2021-07-06 1:34 ` Billy Tetrud
2021-07-06 4:54 ` ZmnSCPxj
2021-07-06 5:09 ` Eric Voskuil
2021-07-06 6:02 ` Billy Tetrud
2021-07-06 7:37 ` Eric Voskuil
2021-07-06 16:39 ` Erik Aronesty
2021-07-06 18:40 ` eric
2021-07-07 6:18 ` Billy Tetrud
2021-07-09 14:55 ` Eric Voskuil
2021-07-09 17:43 ` Billy Tetrud
2021-07-09 18:32 ` Eric Voskuil
2021-07-09 22:02 ` Billy Tetrud
2021-07-09 23:18 ` Eric Voskuil
2021-07-09 23:50 ` ZmnSCPxj
2021-07-10 0:49 ` eric
2021-07-10 1:26 ` ZmnSCPxj
2021-07-10 1:49 ` eric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cLK-RFlIdmwOvuKag-cOImIVCltq97EWfT-mFpPFa5wJfbAgptlKFhmgt4WQNw2pYVt-sGCCCTtHi1s0Vdwwimun_fUdvrDeOOPnlFjYDdA=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox