From: James Lu <jamtlu@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Reducing block reward via soft fork
Date: Sat, 22 May 2021 21:00:19 -0400 [thread overview]
Message-ID: <CANQHGB1N4E9=cqrkxDiUH5hAHgzURAJv+S7Vkf8xWEMJ=+T_AQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Background
===
Reducing the block reward reduces the incentive to mine. It reduces the
maximum energy price at which mining is profitable, reducing the energy use.
Bitcoins have value because they are accepted by full node users, from
individual node operators, to exchanges and custodians like Coinbase.
Anything else and the Bitcoins don't exist and are worthless. Like all
currencies, Bitcoin has value because others recognize that they have value.
Idea
===
Reduce the block reward by adding fewer coins to the UTXO set per block.
This should be done gradually
Consensus layer
===
This is a soft fork, because it tightens the
Some Possible Weaknesses
===
- It will cost less than a nation-state of energy to reverse recent Bitcoin
transactions.
- Some miners may protest and lobby exchanges.
- By pushing mining towards the cheapest energy sources, centralization
increases towards Chinese miners.
- The Bitcoin network may split if consensus is not built before flag day.
However, given the current political headwinds and widespread public
discussion around Bitcoin's energy use, it may be socially possible to ask
individual users and major exchanges to install a version of Bitcoin with a
reduced block reward.
Alternatives
===
Instead of outright rejecting transactions (and the blocks that contain
them) that attempt to spend increased block rewards, treat them as no-ops.
[-- Attachment #2: Type: text/html, Size: 4538 bytes --]
next reply other threads:[~2021-05-23 1:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 1:00 James Lu [this message]
2021-05-23 10:42 ` Anton Ragin
[not found] ` <CANQHGB2pD57cZzcuTqr25Pg-Bvon_=G=_5901to2esrcumk-GA@mail.gmail.com>
2021-05-23 14:40 ` [bitcoin-dev] Fwd: " James Lu
2021-05-23 11:26 ` [bitcoin-dev] " ZmnSCPxj
2021-05-23 12:08 ` Karl
2021-05-23 13:35 ` ZmnSCPxj
2021-05-23 19:44 ` Karl
2021-05-24 20:28 ` Billy Tetrud
2021-05-24 21:55 ` Erik Aronesty
2021-05-25 0:55 ` Karl
2021-05-25 8:01 ` Billy Tetrud
2021-05-25 8:35 ` Jorge Timón
2021-05-25 8:53 ` Melvin Carvalho
2021-05-25 19:40 ` Billy Tetrud
2021-05-24 22:03 ` Phuoc Do
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='CANQHGB1N4E9=cqrkxDiUH5hAHgzURAJv+S7Vkf8xWEMJ=+T_AQ@mail.gmail.com' \
--to=jamtlu@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