From: Andrew Melnychuk Oseen <amo.personal@protonmail•com>
To: Giuseppe B <beppeben2030@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Minimum fees
Date: Sat, 04 Mar 2023 06:21:44 +0000 [thread overview]
Message-ID: <LwVUuu83ndd7MUq-j3Rn-WFJgyLMHUtMnBw4GZY6zgryOcJ_ieZG7HQefZ003xltOrngAOMnG03fAWt3yeqdFcaV-5dN3er2CigtAQKmAMA=@protonmail.com> (raw)
In-Reply-To: <CABrXkXoq4x9aRuk0ZnfPmqE-TXZfROMuAMTwCO9VCcTnJ+snNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2994 bytes --]
From my limited knowledge in the space, and I've taken opinions of people I respect that are far more knowledgeable than me.
I don't know of any data of what happens at the point where the coinbase drops to below the fees on any chain. I don't think there has been one where that has happened. Perhaps there is a chain out there where it is fee's only? Perhaps that can provide insight.
Opinion: I think as bitcoin's capabilities grow, demand for it will as well. There are a lot of efforts to increase the amount of transactions that can fit into a block. I think the combination of limited block space and a reduced amount of bitcoin's entering the market is the right combination for the system to self sustain. I'm looking forward to seeing the result!
Sent with [Proton Mail](https://proton.me/) secure email.
------- Original Message -------
On Wednesday, March 1st, 2023 at 12:18 PM, Giuseppe B via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hello everyone,
>
> I'm relatively new here so what I'm proposing could have already been discussed, or may be flawed or inapplicable. I apologize for that.
>
> I was picturing a situation where block rewards are almost zero, and the base layer is mainly used as a settlement layer for relatively few large transactions, since the majority of smaller ones goes through LN.
>
> In such a case it may very well be that even if transaction amounts are very consistent, transaction fees end up being very small since there is enough space for everyone in a block. Users wouldn't mind paying higher fees as they know that that would increase the network security, however nobody wants to be the only one doing that. Miners would of course like being paid more. So everyone involved would prefer higher fees but they just stay low because that's the only rational individual choice.
>
> Therefore I was imagining the introduction of a new protocol rule, min_fees, that would work like this:
> - the miner that gets to mine a block appends a min_fee field to the block, specifying the minimum fees that need to be contained in the following block in order for it to be valid.
> - one can also mine an empty block and reset the min_fee, to avoid the chain getting stuck.
>
> min_fees could either represent the total fees of the following block, or the minimal fee for each single transaction, as a percentage of the value transacted. Both seem to have some merits and some potential drawbacks. Of course min_fees=0 would correspond to the current situation.
>
> It looks to me that this could have the potential to bring the equilibrium closer to a socially optimal one (as opposed to individually optimal), and to benefit the network security in the long term. Of course it's just a rough sketch and it would deserve a much deeper analysis. I was just interested in knowing if you think that the principle has some merit or if it's not even worth discussing it for some reason that I'm not considering.
>
> Cheers,
>
> Giuseppe.
[-- Attachment #2: Type: text/html, Size: 4638 bytes --]
next prev parent reply other threads:[~2023-03-04 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 20:18 Giuseppe B
2023-03-02 0:39 ` Nadav Ivgi
2023-03-03 5:07 ` Giuseppe B
2023-03-03 2:45 ` WMOURA
2023-03-03 5:19 ` Giuseppe B
2023-03-04 6:21 ` Andrew Melnychuk Oseen [this message]
2023-03-02 22:27 jk_14
2023-03-05 21:58 vjudeu
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='LwVUuu83ndd7MUq-j3Rn-WFJgyLMHUtMnBw4GZY6zgryOcJ_ieZG7HQefZ003xltOrngAOMnG03fAWt3yeqdFcaV-5dN3er2CigtAQKmAMA=@protonmail.com' \
--to=amo.personal@protonmail$(echo .)com \
--cc=beppeben2030@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