From: "aliashraf.btc At protonmail" <aliashraf.btc@protonmail.com>
To: Peter <dizzle@pointbiz.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Surprisingly, Tail Emission Is Not Inflationary
Date: Fri, 19 Aug 2022 17:21:03 +0000 [thread overview]
Message-ID: <xcXwPxo9HRhMxQw9KIiDEfb6f4p6rY-24v3JUVHH2fkS7IcTK1Qe_7Hw4nJbGwdf6Guh0kS_nlPF-kzCVeS2MAioQmdjzpkGJibzyMj2JY0=@protonmail.com> (raw)
In-Reply-To: <abd33vsLrsQ7z5vJjz9h1V-3iEHJW1os1HyiO6QO5PNA8kahcPZ_2BUNuU7i4gyFRT2peLu0NXNrWv5X3RGGR6cvqijishTcb1qvo3YPeSU=@pointbiz.com>
[-- Attachment #1: Type: text/plain, Size: 5130 bytes --]
Hi Peter, everyone
This issue has been discussed thoroughly in bitcointalk, general discussions are more suited to forums, I believe, still ....
First and foremost, it is more than obvious that bitcoin block subsidy algorithm is a total disaster, not just for the zero subsidy security consequences, but also for the overly rewarding scheme that favors (few) first-runners against (masses of) people who join later, a policy that looks to be a cheap marketing trick rather than a decent strategic monetary, system design, no matter how natural it is presumed nowadays, after being implemented by Bitcoin.
For now, the brilliance of the idea behind Bitcoin and the enthusiasm have compensated for its bizzar, upside-down inflation policy, in practice as newcomers have been paying the price to lucky first-runners and adopting anyway.
Is it happening for low block subsidy? Is it going to be solved somehow? I don't think so.
With subsidy still being the major (like 90%) portion of the block reward, there is an equalizer factor pushing equilibrium by paying security costs on behalf of current coin owners.Note that every single new bitcoin paid as subsidy is actually paid by the rest of the wallets proportional to their balance.
Other than its direct contribution to security, once understood as a ballance-based taxing scheme, it is a crucial mechanism for re-distribution of wealth because to compensate for their costs, unlike speculators (who are among the worst adopters of Bitcoin, and unfortunately the most influencers), miners are used to dumping their coins, providing more fair opportunities for people to join.
So, halving and the hard cap, put both adoption and security as risk, It is why, unlike "believers", I'm deeply concerned about a future with low block subsidy because it puts both security and adoption in an awkward situation.
Additionally, It is not considered an engineering practice by any measure to speculate about the security of a system that we abundantly recommend to friends, family for joining.
We need proofs, security proof, ease of adaptation proof, etc.,
Fantasies are not proofs, having faith in a magical incentive mechanism that fixes everything is not an argument, let alone being a proof.
Incentives are irrelevant, rules, schemes, projects, and so fort, matter. There are always incentives in games, but rules are in charge of determining the fate.
Without rules, there is no game, flawed schemes and rules move the game behind its equilibrium to fail eventually.
I've not to mention the unfeasibility of tempering Bitcoin's basic consensus rules, Bitcoin rules are not subject to change specially when it comes to something that is widely considered a basic characteristic, a Schelling point, and so forth.
So, it is the paradoxical situation: we are exposed to, on one hand, it is a deficiency and on the other hand it is inevitable because is critically hard-code to Bitcoin, advertised more than any feature as its identity.
But it is our job, isn't it? Dealing with the impossible and taking care of it, but I think before reaching to that point we have to settle the basics.:
- There is a problem with long term security and adoption consequences.
- It is built deeply to bitcoin consensus rules, and considered a critical
- It is not going to disappear magically, neither it will be addressed by whales, etc.
- The 21M cap, halving, and generally, Bitcoin consensus, is not subject to change.
Don't panic, it is not exactly a catch-22 situation. Tip:
It is always possible to help a system without aggressive intervention, either by smart tweaks or by supporting it using other system(s).
Cheers, Ali Ashraf
------- Original Message -------
On Tuesday, August 16th, 2022 at 8:35 PM, Peter via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi Jaroslaw,
> In the Prisoner's Dilemma the prisoners cannot communicate. In Bitcoin large holders are able to communicate with each other. Also, prisoners need not make an all or nothing decision in Bitcoin. Miners can join and leave the network freely over time. You can change your decision based on the decision of others.
>
> The Bitcoin design is such that security is volatile but the issuance of blocks is timely and evened out to a 10 minutes average even after the reward is exhausted.
>
> The existing incentive that miners earn money for including transactions is enough to motivate human nature. Transaction initiators have an incentive to mine and run full nodes for personal interest.
>
>>Noone will waste his renewable energy on unprofitable Antminer while he/she can sell this energy for the market price.
>
> The law in most jurisdictions prevents the resale of spare electricity unless an expensive license is obtained (and in most cases no license is available as the government maintains a monopoly). Mining with waste electricity is reducing losses. Another incentive to motivate human nature.
>
> Bitcoin holders can be enfranchised into any new system. So, no need for bike shedding the original design which is a Schelling Point.
>
> Regards
>
> Peter Kroll
>
> pointbiz/ BTCCuracao
[-- Attachment #2: Type: text/html, Size: 8030 bytes --]
next prev parent reply other threads:[~2022-08-19 17:21 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 16:05 [bitcoin-dev] Surprisingly, Tail Emission Is Not Inflationary Peter
2022-08-19 17:21 ` aliashraf.btc At protonmail [this message]
2022-08-20 15:30 ` Billy Tetrud
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 5:34 vjudeu
2022-08-18 20:22 jk_14
2022-08-17 13:43 jk_14
2022-08-18 15:29 ` Breno Brito
2022-08-18 15:44 ` Billy Tetrud
2022-08-18 20:49 ` Erik Aronesty
2022-08-17 8:54 jk_14
2022-08-15 21:46 jk_14
2022-08-17 11:10 ` Erik Aronesty
2022-07-26 20:01 jk_14
2022-07-19 18:36 Peter
2022-07-20 14:35 ` Eric Voskuil
2022-07-10 17:42 Eric Voskuil
[not found] <mailman.80287.1657405305.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-07-10 7:44 ` John Tromp
2022-07-09 22:21 Peter
2022-07-09 20:54 Eric Voskuil
2022-07-09 21:59 ` ZmnSCPxj
2022-07-10 14:17 ` alicexbt
2022-07-10 16:38 ` alicexbt
2022-07-10 17:29 ` Peter Todd
2022-07-10 17:27 ` Peter Todd
2022-07-10 18:12 ` vjudeu
2022-07-18 11:34 ` David A. Harding
2022-07-18 19:14 ` Erik Aronesty
2022-07-18 21:48 ` Eric Voskuil
2022-07-25 15:04 ` Erik Aronesty
2022-07-26 15:44 ` jk_14
2022-07-26 17:05 ` Erik Aronesty
2022-07-09 20:53 Eric Voskuil
2022-07-09 14:57 John Tromp
2022-07-09 15:13 ` Peter Todd
2022-07-11 18:44 ` Dave Scotese
2022-07-09 12:46 Peter Todd
2022-07-09 14:26 ` Eric Voskuil
2022-07-09 15:15 ` Peter Todd
2022-07-09 15:24 ` Eric Voskuil
2022-07-09 15:31 ` Peter Todd
2022-07-09 17:43 ` naman naman
2022-07-09 17:48 ` Peter Todd
2022-07-10 6:54 ` naman naman
2022-07-10 2:10 ` Tobin Harding
2022-07-10 7:08 ` vjudeu
2022-07-11 18:25 ` Larry Ruane
2022-07-10 10:18 ` Jacob Eliosoff
2022-07-11 2:32 ` Anthony Towns
2022-07-11 6:15 ` Stefan Richter
2022-07-11 10:42 ` Giuseppe B
2022-07-11 12:56 ` Erik Aronesty
2022-07-11 23:57 ` Anthony Towns
2022-07-13 18:29 ` Zac Greenwood
2022-07-11 16:59 ` Peter Todd
2022-07-11 17:44 ` Bram Cohen
2022-07-13 14:06 ` Alfred Hodler
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='xcXwPxo9HRhMxQw9KIiDEfb6f4p6rY-24v3JUVHH2fkS7IcTK1Qe_7Hw4nJbGwdf6Guh0kS_nlPF-kzCVeS2MAioQmdjzpkGJibzyMj2JY0=@protonmail.com' \
--to=aliashraf.btc@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=dizzle@pointbiz.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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