search

novitski / bitcoinj

Automatically exported from code.google.com/p/bitcoinj
Apache License 2.0
0 stars 0 forks source link

Refactor wallet to not use Transaction objects directly (or to use derived Transactions) #500

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The wallet currently works with and stores raw Transaction objects. This has a 
number of disadvantages. Refactor it to track the tx hash, relevant outputs 
only, and then we can store additional data like user-provided notes more 
easily. 

Note that for trezor support we will still need the ability to keep raw 
transaction bytes around, at least for a while. However not all wallets care 
about trezor support.

At the same time we might want to add in a Payment abstraction, to handle the 
cases where a single logical payment involves multiple transactions (like when 
storing dependencies and/or for merge avoidance in future).

Original issue reported on code.google.com by hearn@google.com on 14 Dec 2013 at 11:18