Eric Voskuil [ARCHIVE] on Nostr: 📅 Original date posted:2021-05-07 📝 Original message: > On May 7, 2021, at ...
📅 Original date posted:2021-05-07
📝 Original message:
https://github.com/libbitcoin/libbitcoin-system/wiki/Proof-of-Stake-Fallacy> On May 7, 2021, at 15:50, SatoshiSingh via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> Hello list,
>
> I am a lurker here and like many of you I worry about the energy usage of bitcoin mining. I understand a lot mining happens with renewable resources but the impact is still high.
>
> I want to get your opinion on implementing proof of stake for bitcoin mining in future. For now, proof of stake is still untested and not battle tested like proof of work. Though someday it will be.
>
> In the following years we'll be seeing proof of stake being implemented. Smaller networks can test PoS which is a luxury bitcoin can't afford. Here's how I see this the possibilities:
>
> 1 - Proof of stake isn't a good enough security mechanism
> 2 - Proof of state is a good security mechanism and works as intended
>
> IF PoS turns out to be good after battle testing, would you consider implementing it for Bitcoin? I understand this would invoke a lot of controversies and a hard fork that no one likes. But its important enough to consider a hard fork. What are your opinions provided PoS does work?
>
> Love from India.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
>
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210507/ed773f98/attachment.html>
Published at
2023-06-07 22:52:36Event JSON
{
"id": "86c75dc5285e9a623f1b767d72e08850d69183e8b023b855f80804bdcd393959",
"pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e",
"created_at": 1686178356,
"kind": 1,
"tags": [
[
"e",
"3924236b4a6804e5062f43250316165d7329dbe370a76aa07c1a86d1bcab9697",
"",
"root"
],
[
"e",
"26aa7dcd4e736acbc0d4235e61f8ae5bccd5894566d337677c9745a87a1048db",
"",
"reply"
],
[
"p",
"b09ebfd5448752d5fa475a36786fcf6fc425b86df97488204a8b41a72294acad"
]
],
"content": "📅 Original date posted:2021-05-07\n📝 Original message:https://github.com/libbitcoin/libbitcoin-system/wiki/Proof-of-Stake-Fallacy\n\n\u003e On May 7, 2021, at 15:50, SatoshiSingh via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e Hello list,\n\u003e \n\u003e I am a lurker here and like many of you I worry about the energy usage of bitcoin mining. I understand a lot mining happens with renewable resources but the impact is still high.\n\u003e \n\u003e I want to get your opinion on implementing proof of stake for bitcoin mining in future. For now, proof of stake is still untested and not battle tested like proof of work. Though someday it will be.\n\u003e \n\u003e In the following years we'll be seeing proof of stake being implemented. Smaller networks can test PoS which is a luxury bitcoin can't afford. Here's how I see this the possibilities:\n\u003e \n\u003e 1 - Proof of stake isn't a good enough security mechanism\n\u003e 2 - Proof of state is a good security mechanism and works as intended\n\u003e \n\u003e IF PoS turns out to be good after battle testing, would you consider implementing it for Bitcoin? I understand this would invoke a lot of controversies and a hard fork that no one likes. But its important enough to consider a hard fork. What are your opinions provided PoS does work?\n\u003e \n\u003e Love from India.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210507/ed773f98/attachment.html\u003e",
"sig": "d8f2ed2501725c421f9ffdcb3c071aec39798bafcf85ecdf909e45908c4552ee71345e7aa7cccb72c4e4963ab019fe740f209bee8e3648b8b37f284e1afbc494"
}