Durable transaction fee model #4146

issue ghost opened this issue on May 7, 2014
  1. ghost commented at 6:06 PM on May 7, 2014: none

    Considering the fact that Bitcoin market prices are now mature enough to be streaming on a Bloomberg terminal doesn't it make sense to create a cash market price driven fee model so this never has to be revisited in the future?

    Empowering each node with this insight would also assist future directions for the GUI where people invariably will want to send/receive/report in fiat terms. If the fiat price is already used by all nodes to facilitate transaction fee handling, an additional getfiatpx call could be added to the RPC interface.

  2. laanwj added the label TX fees on May 9, 2014
  3. ghost commented at 11:06 PM on August 26, 2014: none

    What if we had the TX fee go down by a decimal place every reward-halving? That might be a fairly accurate way to lower it.

  4. christophebiocca commented at 11:23 PM on August 26, 2014: none

    The fee isn't controlled by the software. It is decided by every miner's inclusion policy. Nodes are now estimating what the prevalent fees are based on actual block inclusion delays to avoid having hardcoded fees at all. The relevant development effort is at #3959 and #4250.

  5. ghost commented at 11:28 PM on August 26, 2014: none

    Ah, my bad. Thanks for explaining. I like where this is going with both of those commits merged. Will be interesting to see how that plays out.

  6. gmaxwell closed this on Aug 28, 2014

  7. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 09:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me