1. 17 Dec, 2018 1 commit
  2. 13 Dec, 2018 1 commit
  3. 30 Nov, 2018 1 commit
  4. 08 Nov, 2018 2 commits
  5. 05 Nov, 2018 3 commits
  6. 25 Oct, 2018 1 commit
  7. 18 Oct, 2018 1 commit
  8. 12 Oct, 2018 1 commit
  9. 11 Oct, 2018 1 commit
  10. 03 Oct, 2018 1 commit
  11. 02 Oct, 2018 1 commit
  12. 01 Oct, 2018 1 commit
  13. 27 Sep, 2018 1 commit
  14. 19 Sep, 2018 1 commit
  15. 11 Sep, 2018 3 commits
  16. 04 Sep, 2018 1 commit
  17. 29 Aug, 2018 3 commits
  18. 28 Aug, 2018 1 commit
  19. 27 Aug, 2018 1 commit
  20. 27 Jul, 2018 3 commits
  21. 23 Jul, 2018 1 commit
  22. 20 Jul, 2018 2 commits
  23. 18 Jul, 2018 1 commit
  24. 17 Jul, 2018 1 commit
    • Luke Champine's avatar
      split SpendableOutputs into two methods · 16d44375
      Luke Champine authored
      Tracking outputs is fundamentally different from being able to
      spend them. Splitting out the UnlockConditions() method makes it
      trivial to add bucketUnlockConditions to the wallet.db later.
      16d44375
  25. 16 Jul, 2018 1 commit
  26. 12 Jul, 2018 1 commit
    • Luke Champine's avatar
      overhaul SignTransaction · f174e413
      Luke Champine authored
      In a nutshell, SignTransaction now does less work: it requires the
      user to fill out the UnlockConditions and TransactionSignatures of
      the transaction, whereas before it would fill them in itself. This
      is a better approach because it makes the most common operation --
      signing all the inputs that the wallet controls -- dead simple. And
      requiring the user to fill out the unlock conditions isn't a big
      deal, because they can get those from /wallet/unspent. Lastly, if
      the user is responsible for filling out the TransactionSignature
      fields, they can control precisely what gets signed.
      f174e413
  27. 10 Jul, 2018 1 commit
  28. 09 Jul, 2018 1 commit
  29. 03 Jul, 2018 2 commits