Add a balance column to the transactions view #935

issue rebroad opened this issue on March 12, 2012
  1. rebroad commented at 7:42 PM on March 12, 2012: contributor

    Transactions shows amounts in and out, but I think it would be useful to have a column showing the balance history after each transaction.

  2. ghost commented at 7:58 AM on December 4, 2012: none

    Hmmmm. I will look into this. Will update you on this in a min or so.

  3. laanwj commented at 6:34 PM on March 30, 2013: member

    Discussion from IRC today, in case anyone wants to pick this up:

    <wumpus> wasn't the problem that transactions don't have a fixed order?
    <bitnumus> no dates stored in blockchain ?
    <Luke-Jr> wumpus: they do now
    <wumpus> you're not exactly the first to propose this
    <Luke-Jr> sortof
    <wumpus> Luke-Jr: ok, cool, so now it should be possible then
    <sipa> wumpus: even if not, only non-confirmed transactions' internal order can change
    <sipa> and only the top-N can be reverted
    <Luke-Jr> sipa: only if the user does a salvagewallet
    <Luke-Jr> doesn't do*
    <sipa> Luke-Jr: what if you have 2 non-confirmed ones, and the latest of them makes it into a block flbefore the other?
    <Luke-Jr> sipa: the order remains the same
    <wumpus> but indeed, as soon as the transactions are in the block chain they have a fixed order
    <wumpus> barring reorganizations etc
    <Luke-Jr> wumpus: not necessarily the order used by the client
    --> andytoshi (~username@gateway/tor-sasl/andytoshi) is #bitcoin-dev binnengekomen
    <sipa> Luke-Jr: what if the other is doublespent?
    <Luke-Jr> sipa: double spending is not supported at all by the client..
    <python-n00b> How much Keys do the Bitcoin-qt software support?
    <sipa> wumpus: thebonly real accounting is making a ledger of changes, rather than actual bitcoin transactions
    <andytoshi> python-n00b: finite but unbounded
    <python-n00b> for example 1000000000 adress??
    <andytoshi> python-n00b: the software supports it, but it may be very slow
    <sipa> wumpus: i.e. add a +N ledger entry the moment you get 6 confirms on a transaction, and do a counteracting -N one if it gets reorged
    <andytoshi> i'm not sure if there are any benchmarks published..
    <sipa> python-n00b: 10000's is certainly doable
    --> talengix (~talengix@188.175.24.2) is #bitcoin-dev binnengekomen
    --> safra (~dani@212.7.208.132) is #bitcoin-dev binnengekomen
    <wumpus> sipa: indeed, so the ledger would be a separate thing from the transaction list
    <wumpus> and would have to be stored in the wallet separately
    <sipa> indeed
    <sipa> but it would be guaranteed to be append-only
    <wumpus> bitnumus: so, now you understand why it's non-trivial
    <wumpus> it's far from simply adding a column
    <python-n00b> oh
    
  4. laanwj added the label Wallet on Aug 12, 2014
  5. laanwj commented at 10:04 AM on September 25, 2014: member

    Closing this; would be better to implement this in one of the SPV wallets that are actually used by people.

  6. laanwj closed this on Sep 25, 2014

  7. suprnurd referenced this in commit 2967aa61a1 on Dec 5, 2017
  8. ptschip referenced this in commit cd88c9697b on Jan 25, 2018
  9. 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-21 15:16 UTC

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