From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Junhyuk Jun Lee <xodn348@gmail.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [Research] Bitcoin After Block Rewards: preventing miner deviation as the block rewards approaches zero
Date: Tue, 14 Jul 2026 00:58:42 +0200 [thread overview]
Message-ID: <CAKaEYh+t_sPhQaNL91_Pmwc9HdVqQjzXKMDUy_YpsaLCrJ1zhw@mail.gmail.com> (raw)
In-Reply-To: <CAEOyoSPQt=TTN-JOVxmCk9UvD1MMHwoHPSvm34Zf2gv8RjcxNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2671 bytes --]
ne 12. 7. 2026 v 0:09 odesílatel Junhyuk Jun Lee <xodn348@gmail.com> napsal:
> Hi, list.
>
> *I'd like to share a paper on Bitcoin security in the fee-only regime,
> after block rewards reach zero. *
>
> This paper analyzes at what point deviating from honest mining becomes the
> rational strategy and how to prevent massive deviation for
> profit-maximizing miners using Base Fee, Fee Floor, and adaptive block
> size rules .
>
> *Results:*
>
> 1. We define a threshold (G_t) that signals when deviation becomes
> rational in a fee-only regime.
> 2. In simulation, deviation becomes rational at fee differentials as low
> as 0.17% of transaction fees when the block reward reaches zero by
> continuous halving.
> 3. We evaluate three mitigations and their effect on the deviation
> threshold: base fees, fee floors, and adaptive block sizing.
>
> *Paper: https://arxiv.org/abs/2606.05503
> <https://arxiv.org/abs/2606.05503>*
>
At what halving epoch does your model predict deviation becomes materially
significant in practice?
For example, could this begin around 2040, when the subsidy falls to
roughly 0.195 BTC per block, or only much later?
>
>
> Related discussion on Delving Bitcoin, including recent fee-equilibrium
> modeling that approaches the same regime from the revenue side:
>
> https://delvingbitcoin.org/t/research-bitcoin-after-block-rewards-preventing-miners-deviation-when-the-bitcoin-rewards-is-zero/2626
> https://delvingbitcoin.org/t/addressing-the-diminishing-block-subsidy/2640
>
> Feedback on the model and its assumptions is welcome and whether the
> mitigations are realistic as soft forks.
>
> Best,
> Junhyuk Lee
>
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/CAEOyoSPQt%3DTTN-JOVxmCk9UvD1MMHwoHPSvm34Zf2gv8RjcxNg%40mail.gmail.com
> <https://groups.google.com/d/msgid/bitcoindev/CAEOyoSPQt%3DTTN-JOVxmCk9UvD1MMHwoHPSvm34Zf2gv8RjcxNg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAKaEYh%2Bt_sPhQaNL91_Pmwc9HdVqQjzXKMDUy_YpsaLCrJ1zhw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3975 bytes --]
prev parent reply other threads:[~2026-07-13 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 22:08 [bitcoindev] [Research] Bitcoin After Block Rewards: preventing miner deviation as the block rewards approaches zero Junhyuk Jun Lee
2026-07-13 22:58 ` Melvin Carvalho [this message]
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=CAKaEYh+t_sPhQaNL91_Pmwc9HdVqQjzXKMDUy_YpsaLCrJ1zhw@mail.gmail.com \
--to=melvincarvalho@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=xodn348@gmail.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