1. 18 Sep, 2016 1 commit
  2. 15 Sep, 2016 2 commits
  3. 09 Sep, 2016 2 commits
  4. 25 Aug, 2016 1 commit
  5. 08 Jun, 2016 4 commits
  6. 04 Nov, 2015 1 commit
  7. 11 Oct, 2015 1 commit
  8. 22 Jul, 2015 3 commits
  9. 28 Aug, 2014 1 commit
  10. 25 Aug, 2014 1 commit
  11. 20 Jul, 2014 1 commit
  12. 21 May, 2014 1 commit
  13. 12 May, 2014 1 commit
  14. 07 May, 2014 1 commit
  15. 30 Apr, 2014 2 commits
  16. 24 Apr, 2014 1 commit
  17. 23 Apr, 2014 1 commit
  18. 18 Apr, 2014 1 commit
    • Wladimir J. van der Laan's avatar
      Solve chainActive-related locking issues · 66dbf49f
      Wladimir J. van der Laan authored
      - In wallet and GUI code LOCK cs_main as well as cs_wallet when
        necessary
      - In main.cpp SendMessages move the TRY_LOCK(cs_main) up, to encompass the call
        to IsInitialBlockDownload.
      - Make ActivateBestChain, AddToBlockIndex, IsInitialBlockDownload,
        InitBlockIndex acquire the cs_main lock
      
      Fixes #3997
      66dbf49f
  19. 17 Apr, 2014 1 commit
  20. 06 Apr, 2014 1 commit
  21. 29 Mar, 2014 1 commit
    • Wladimir J. van der Laan's avatar
      Fix `-printblocktree` output · d6870d29
      Wladimir J. van der Laan authored
      PrintBlockTree output was broken starting from e010af70.
      Everything appears on one line.
      
      PrintWallet() added the newline after a block, but this functionality
      was removed and no newline was added.
      
      Seemingly, no one noticed. Add a newline after the block information
      to fix this.
      d6870d29
  22. 11 Mar, 2014 2 commits
  23. 10 Mar, 2014 1 commit
    • Mike Hearn's avatar
      Make mining fee policy match relay fee policy. · 08751f73
      Mike Hearn authored
      This resolves a case in which a mismatch could be used to bloat up the
      mempool by sending transactions that pay enough fee to relay, but not
      to be mined, with the default policies.
      08751f73
  24. 26 Feb, 2014 1 commit
    • Gavin Andresen's avatar
      Remove CWalletTx::vfSpent · 335d0c34
      Gavin Andresen authored
      Use the spent outpoint multimap to figure out which wallet transaction
      outputs are unspent, instead of a vfSpent array that is saved
      to disk.
      335d0c34
  25. 24 Feb, 2014 1 commit
    • Wladimir J. van der Laan's avatar
      Get rid of C99 PRI?64 usage in source files · 87fa85e8
      Wladimir J. van der Laan authored
      Amend to d5f1e727. It turns out that BerkelyDB was including inttypes.h
      indirectly, so we cannot fix this with just macros.
      
      Trivial commit: apply the following script to all .cpp and .h files:
      
          # Middle
          sed -i 's/"PRIx64"/x/g' "$1"
          sed -i 's/"PRIu64"/u/g' "$1"
          sed -i 's/"PRId64"/d/g' "$1"
          # Initial
          sed -i 's/PRIx64"/"x/g' "$1"
          sed -i 's/PRIu64"/"u/g' "$1"
          sed -i 's/PRId64"/"d/g' "$1"
          # Trailing
          sed -i 's/"PRIx64/x"/g' "$1"
          sed -i 's/"PRIu64/u"/g' "$1"
          sed -i 's/"PRId64/d"/g' "$1"
      
      After this commit, `git grep` for PRI.64 should turn up nothing except
      the defines in util.h.
      87fa85e8
  26. 22 Feb, 2014 1 commit
    • Wladimir J. van der Laan's avatar
      Don't use PRIx64 formatting derives from inttypes.h · 3618c435
      Wladimir J. van der Laan authored
      As the tinyformat-based formatting system (introduced in b77dfdc9) is
      type-safe, no special format characters are needed to specify sizes.
      
      Tinyformat can support (ignore) the C99 prefixes such as "ll" but
      chokes on MSVC's inttypes.h defines prefixes such as "I64X". So don't
      include inttypes.h and define our own for compatibility.
      
      (an alternative would be to sweep the entire codebase using sed -i to
      get rid of the size specifiers but this has less diff impact)
      3618c435
  27. 20 Feb, 2014 1 commit
  28. 14 Feb, 2014 1 commit
    • Gavin Andresen's avatar
      Handle "conflicted" transactions properly · 64e9a19b
      Gavin Andresen authored
      Extend CMerkleTx::GetDepthInMainChain with the concept of
      a "conflicted" transaction-- a transaction generated by the wallet
      that is not in the main chain or in the mempool, and, therefore,
      will likely never be confirmed.
      
      GetDepthInMainChain() now returns -1 for conflicted transactions
      (0 for unconfirmed-but-in-the-mempool, and >1 for confirmed).
      
      This makes getbalance, getbalance '*', and listunspent all agree when there are
      mutated transactions in the wallet.
      
      Before:
       listunspent: one 49BTC output
       getbalance: 96 BTC (change counted twice)
       getbalance '*': 46 BTC (spends counted twice)
      
      After: all agree, 49 BTC available to spend.
      64e9a19b
  29. 13 Feb, 2014 1 commit
  30. 11 Feb, 2014 1 commit
  31. 10 Feb, 2014 1 commit