Need fee estimation migration for 0.15 #10418

issue TheBlueMatt opened this issue on May 17, 2017
  1. TheBlueMatt commented at 8:23 PM on May 17, 2017: member

    #10199 has some basic deserialization code still in place for old fee estimations to support reading 0.14-formatted fee estimates so that they can be at least utilized to populate some basic fee results until the new buckets fill up. We'd need to implement such a scheme for 0.15. @morcos.

  2. fanquake added this to the milestone 0.15.0 on May 17, 2017
  3. fanquake added the label TX fees and policy on May 17, 2017
  4. morcos commented at 7:34 PM on July 6, 2017: member

    This isn't going to happen. Would have been a nice addition, but not critical. Let's let it go

  5. laanwj commented at 6:02 PM on July 13, 2017: member

    Closing, if it's not going to happen for 0.15, it makes no sense to do later on.

  6. laanwj closed this on Jul 13, 2017

  7. MarcoFalke 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