From: Luke Dashjr <luke@dashjr•org>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Mandatory Inclusion of Old Transactions in Blocks
Date: Sat, 28 Dec 2024 11:22:49 -0500 [thread overview]
Message-ID: <f1a0153b-3142-4e01-a68e-92c458762b89@dashjr.org> (raw)
In-Reply-To: <fa4a8cd3-778c-4793-8dd4-5662475b6601n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 3606 bytes --]
This is not technically sound, so ineligible to be a BIP. There is no
consensus on unconfirmed transactions. There is also no date associated
with transactions.
On 12/28/24 10:54 AM, developer wrote:
> Status: Draft
> Type: Standards Track
> Created: December 27, 2024
> Abstract
>
> This proposal mandates miners to include at least 0.1% of transactions
> in their blocks from the oldest transactions by date, even if they
> have low fees. This mechanism helps prevent mining centralization and
> censorship, encouraging miners not to exclude certain transactions.
> Motivation
>
> The increasing centralization of Bitcoin mining and potential
> regulations that may require miners to censor or exclude certain
> transactions pose a threat to the Bitcoin network. Mandating the
> inclusion of a small percentage of old transactions, even with low
> fees, ensures that no single miner can censor block contents without
> sacrificing their own rewards.
> Specification
>
> Mandatory Inclusion of Old even if with Low-Fee Transactions
> Each miner is required to include at least 0.1% of the total
> transactions in a block from the oldest transactions in the mempool,
> even if their fees are below the current market average.
> These transactions must be added to blocks regardless of their
> fees, prioritizing their age.
>
> Block Validation
> Bitcoin network nodes will validate blocks only if they
> contain the required percentage of old transactions.
> If a block fails to meet this criterion, it will be deemed
> invalid and rejected by the network.
>
> Incentives
> Miners are incentivized to include these transactions to
> ensure their blocks are valid and to avoid losing block rewards.
>
> Advantages
>
> Censorship Resistance: Miners cannot censor transactions without
> forfeiting their rewards.
> Greater Inclusivity: Old and low-fee transactions are assured of
> being confirmed.
> Decentralization Prevention: Reducing the potential for
> centralized censorship keeps the Bitcoin network decentralized.
>
> Considerations
>
> Impact on the Mempool: The mempool may become more dynamic and
> up-to-date with fewer old, stagnant transactions.
> Resource Management: Miners will need to adjust their systems to
> automatically identify and include relevant transactions.
>
> Conclusion
>
> Implementing this BIP will help maintain the integrity and
> decentralization of the Bitcoin network, preventing censorship and
> ensuring all transactions have a fair chance of confirmation. --
> 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/fa4a8cd3-778c-4793-8dd4-5662475b6601n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/fa4a8cd3-778c-4793-8dd4-5662475b6601n%40googlegroups.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/f1a0153b-3142-4e01-a68e-92c458762b89%40dashjr.org.
[-- Attachment #2: Type: text/html, Size: 4784 bytes --]
next prev parent reply other threads:[~2024-12-28 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 15:54 developer
2024-12-28 16:15 ` Michael Cassano
2024-12-28 18:48 ` Ethan Heilman
2024-12-29 16:35 ` developer
2024-12-28 16:22 ` Luke Dashjr [this message]
2024-12-28 16:23 ` [bitcoindev] " Owen Kemeys
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=f1a0153b-3142-4e01-a68e-92c458762b89@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoindev@googlegroups.com \
/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