Qt: Show transaction size in transaction details window #8672

pull hsjoberg wants to merge 2 commits into bitcoin:master from hsjoberg:qttxsizeindetails changing 3 files +13 −0
  1. hsjoberg commented at 8:38 PM on September 6, 2016: contributor

    Fixes #8125

  2. Adding method GetTotalSize() to CTransaction
    GetTotalSize() returns the total transaction size (including witness) in
    bytes.
    fdf82fba31
  3. qt: Adding transaction size to transaction details window c015634400
  4. sipa commented at 8:42 PM on September 6, 2016: member

    Wouldn't it be more useful to show the transaction weight? That's what matters for fee estimates etc.

  5. luke-jr commented at 8:52 PM on September 6, 2016: member

    I suggest size + feerate-based-on-weight.

  6. hsjoberg commented at 8:56 PM on September 6, 2016: contributor

    @sipa Valid point, I guess I could add that as well. I'm not sure how to make this easy to understand for the user though.

  7. fanquake added the label GUI on Sep 7, 2016
  8. jonasschnelli commented at 6:19 AM on September 7, 2016: contributor

    I agree with @luke-jr: size + ferrate-based-on-weight

  9. sipa commented at 6:25 AM on September 7, 2016: member

    Which size? We have:

    • Base size
    • Total size (base + witness)
    • Virtual size (base + witness/4)
    • Weight (4*base + witness)

    My assumption was that after segwit, only vsize would matter. For old transactions it is identical to total and base size, and for others it remains proportional to fees with that.

  10. jonasschnelli commented at 6:36 AM on September 7, 2016: contributor

    Depends what users will do with the size information. But IMO size should be the "total size" (base + witness). I guess the size has usefulness besides fee calculation.

  11. sipa commented at 6:37 AM on September 7, 2016: member

    I agree it may be useful, but total size isn't the first a user should see

    • it's not relevant for fee calculation, propagation time, priority, or block space usage.
  12. jonasschnelli commented at 6:42 AM on September 7, 2016: contributor

    I agree that the virtual size does make more sense to display. We just need to clearly distinct between size (concrete hard size of a data structure) and virtual size (including other variables and attached to a bigger context).

    I'm also not opposed to display multiple size types (at least base, total and virtual).

  13. laanwj commented at 7:09 AM on September 8, 2016: member

    Which size? We have:

    • Base size
    • Total size (base + witness)
    • Virtual size (base + witness/4)
    • Weight (4*base + witness)

    I think the "easy to implement" tag was a bit deceptive in this case :) #8125 had no discussion about what size at all, I think everyone assumed it to be the size of gettransaction hex.

    anyhow, utACK: Let's call it "Total size" and let people add other sizes later if they want.

  14. hsjoberg commented at 8:19 AM on September 8, 2016: contributor

    @laanwj Indeed, what seemed like an easy task blew up completely. I can continue adding other types of sizes if we decide which ones to add.

    anyhow, utACK: Let's call it "Total size" and let people add other sizes later if they want.

    Will fix.

  15. MarcoFalke commented at 10:59 PM on September 9, 2016: member
  16. laanwj commented at 9:12 AM on September 13, 2016: member

    @marcofalke These are two logically separate commits, one adds the function, the other adds the information to the transaction description HTML, I don't think squashing is necessary.

    ACK after the 'size'→ 'total size' disambiguation.

  17. fanquake commented at 9:01 AM on September 16, 2016: member

    It's pretty self explanatory, but here are some OS X screenshots. transaction transaction2

  18. MarcoFalke commented at 9:22 AM on September 16, 2016: member

    utACK c015634

  19. paveljanik commented at 10:12 AM on September 16, 2016: contributor
  20. jonasschnelli merged this on Sep 20, 2016
  21. jonasschnelli closed this on Sep 20, 2016

  22. jonasschnelli referenced this in commit 6052d50910 on Sep 20, 2016
  23. jonasschnelli commented at 1:35 PM on September 20, 2016: contributor
  24. luke-jr referenced this in commit 73cd55204a on Oct 20, 2016
  25. luke-jr referenced this in commit 98381f1592 on Oct 20, 2016
  26. hsjoberg deleted the branch on Mar 28, 2017
  27. codablock referenced this in commit a7623c884d on Sep 7, 2017
  28. UdjinM6 referenced this in commit 9707ca5cea on Sep 9, 2017
  29. 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-14 21:15 UTC

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