From: Oleg Andreev <oleganza@gmail•com>
To: Thomas Zander <thomas@thomaszander•se>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Răspuns: Personal opinion on the fee market from a worried local trader
Date: Fri, 31 Jul 2015 14:32:53 +0200 [thread overview]
Message-ID: <2B69B87D-CAF8-4817-B637-34E91E0A07FD@gmail.com> (raw)
In-Reply-To: <1706574.Be1RBGpNr6@coldstorage>
> On 31 Jul 2015, at 11:56, Thomas Zander via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> On Friday 31. July 2015 03.21.07 Jorge Timón via bitcoin-dev wrote:
>> If I was a miner and you want me to include your transaction for free,
>> you're asking me to give you money
>
> What?
>
> Ask yourself; why do miners include transactions at all? What it the incentive
> if there really is only less than 0.8% of income to be derived from fees?
>
> Miners don't get payed by fees. They won't need to get payed by fees for
> decades to come. Maybe you want to re-do your math, it seems off.
Fees should be compared not with the total revenue, but with the profit margin. If a miner invested/spends 24 BTC per block and earns 0.25 in fees, then his total profit is 1.25 BTC per block and fees comprise a whopping 20% of the profit.
Today I think profit margins are quite high, so fees do not matter much. But it's not hard to imagine that in just a couple of years BTC may appreciate a lot more, attract more investors and even bigger foundries to, say, print chips and mine right at the foundry, thus driving profit margins lower. Fees will begin to matter regardless of the total subsidy.
Just some hypothetical calculation.
Lets say in 2015 one block costs 5 BTC and fees bring 0.25 BTC. Profit is thus 20.25 BTC and fees comprise 1.2% of that amount.
Lets say in late 2016 halving happens, BTC appreciates and resulting competition drives up the cost to 6 BTC (yes, BTC itself is more expensive, but so is the profit too, so increased competition must drive down the profit margin). Now the block brings 6.75 BTC in profit. Fees, if unchanged now make 4% of the total profit.
If all goes well, in mid 2020 another halving happens (6.25 BTC/block) and even if the BTC-denominated cost stays the same miner now will earn 0.25 BTC profit from subsidy and fees now can account for 100% of that amount.
Of course it's a very rough estimate and most likely to be far from reality, but it shows how fees can begin to matter rather quickly under pressure of separate factors: halving and growing valuation and mining competition.
next prev parent reply other threads:[~2015-07-31 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADZB0_ZgDMhVgCUh2PTAPDL7k_W8QGt_HLYdkwv_qQ5xEMn8HA@mail.gmail.com>
2015-07-29 14:09 ` Vali Zero
2015-07-29 17:47 ` Raystonn .
2015-07-29 22:54 ` s7r
2015-07-30 3:41 ` Ryan Butler
2015-07-30 4:00 ` Adam Back
2015-07-30 4:05 ` Adam Back
2015-07-30 4:48 ` Ryan Butler
2015-07-30 13:14 ` Tom Harding
2015-07-30 14:25 ` Dave Hudson
2015-07-30 14:57 ` Tom Harding
2015-07-30 18:14 ` Jorge Timón
2015-07-30 18:16 ` Jorge Timón
2015-07-30 20:53 ` Tom Harding
2015-07-31 1:21 ` Jorge Timón
2015-07-31 1:29 ` Jorge Timón
2015-07-31 9:56 ` Thomas Zander
2015-07-31 12:32 ` Oleg Andreev [this message]
2015-07-31 15:24 ` Jorge Timón
2015-07-30 12:45 ` Ivan Brightly
2015-07-30 4:07 ` Jean-Paul Kogelman
2015-07-30 9:52 ` odinn
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=2B69B87D-CAF8-4817-B637-34E91E0A07FD@gmail.com \
--to=oleganza@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=thomas@thomaszander$(echo .)se \
/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