📅 Original date posted:2020-05-05
📝 Original message:On Tuesday 05 May 2020 10:17:37 Antoine Riard via bitcoin-dev wrote:
> Trust-minimization of Bitcoin security model has always relied first and
> above on running a full-node. This current paradigm may be shifted by LN
> where fast, affordable, confidential, censorship-resistant payment services
> may attract a lot of adoption without users running a full-node.
No, it cannot be shifted. This would compromise Bitcoin itself, which for
security depends on the assumption that a supermajority of the economy is
verifying their incoming transactions using their own full node.
The past few years has seen severe regressions in this area, to the point
where Bitcoin's future seems quite bleak. Without serious improvements to the
full node ratio, Bitcoin is likely to fail.
Therefore, all efforts to improve the "full node-less" experience are harmful,
and should be actively avoided. BIP 157 improves privacy of fn-less usage,
while providing no real benefits to full node users (compared to more
efficient protocols like Stratum/Electrum).
For this reason, myself and a few others oppose merging support for BIP 157 in
Core.
> Assuming a user adoption path where a full-node is required to benefit for
> LN may deprive a lot of users, especially those who are already denied a
> real financial infrastructure access.
If Bitcoin can't do it, then Bitcoin can't do it.
Bitcoin can't solve *any* problem if it becomes insecure itself.
Luke
P.S. See also
https://medium.com/@nicolasdorier/why-i-dont-celebrate-neutrino-206bafa5fda0
https://medium.com/@nicolasdorier/neutrino-is-dangerous-for-my-self-sovereignty-18fac5bcdc25
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 18:24:17
in reply to nevent1q…ct6g
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 18:24:17Event JSON
{
"id": "e260b589dd916ba379f193c041a04379dc35be25c626e43271df3f83a7765d91",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686162257,
"kind": 1,
"tags": [
[
"e",
"ad4c2484bf2128c112b713501597a58961019dbede510d5eff04fed3caae6695",
"",
"root"
],
[
"e",
"461bca2d22b8cfdca3a78b7ef71c7d1c9286ffc7cb57670d7a922b9b63b0c3ef",
"",
"reply"
],
[
"p",
"6485bc56963b51c9043d0855cca9f78fcbd0ce135a195c3f969e18ca54a0d551"
]
],
"content": "📅 Original date posted:2020-05-05\n📝 Original message:On Tuesday 05 May 2020 10:17:37 Antoine Riard via bitcoin-dev wrote:\n\u003e Trust-minimization of Bitcoin security model has always relied first and\n\u003e above on running a full-node. This current paradigm may be shifted by LN\n\u003e where fast, affordable, confidential, censorship-resistant payment services\n\u003e may attract a lot of adoption without users running a full-node.\n\nNo, it cannot be shifted. This would compromise Bitcoin itself, which for \nsecurity depends on the assumption that a supermajority of the economy is \nverifying their incoming transactions using their own full node.\n\nThe past few years has seen severe regressions in this area, to the point \nwhere Bitcoin's future seems quite bleak. Without serious improvements to the \nfull node ratio, Bitcoin is likely to fail.\n\nTherefore, all efforts to improve the \"full node-less\" experience are harmful, \nand should be actively avoided. BIP 157 improves privacy of fn-less usage, \nwhile providing no real benefits to full node users (compared to more \nefficient protocols like Stratum/Electrum).\n\nFor this reason, myself and a few others oppose merging support for BIP 157 in \nCore.\n\n\u003e Assuming a user adoption path where a full-node is required to benefit for\n\u003e LN may deprive a lot of users, especially those who are already denied a\n\u003e real financial infrastructure access.\n\nIf Bitcoin can't do it, then Bitcoin can't do it.\nBitcoin can't solve *any* problem if it becomes insecure itself.\n\nLuke\n\nP.S. See also\nhttps://medium.com/@nicolasdorier/why-i-dont-celebrate-neutrino-206bafa5fda0\nhttps://medium.com/@nicolasdorier/neutrino-is-dangerous-for-my-self-sovereignty-18fac5bcdc25",
"sig": "4a316dbc58ebc6e5521ed80608824c6fab6ea427426ddfe9b47f99b59abb0b2d98fb90ef1f220999e146d2cf9b13cfb93e10b078493ceedffafd9bf360722651"
}