The blockchain that provides the digital content namespace for the LBRY protocol
1d23c74361
Fix two bugs that can happen if you copy your wallet to another machine and perform transactions on both. First, ReacceptWalletTransactions would notice if the other wallet spent coins, and would correctly mark the receiving transaction spent. However, it did not add the spending transaction to the wallet. Now it does. Second, account balances could get out of sync with 'getbalance' because coins received by the other copy of the wallet were not necessarily detected. Now ReacceptWalletTransactions will scan the entire blockchain for transactions that should be in the wallet if it runs across a 'spent in the other wallet' transaction. Finally, there was a small bug in the accounts getbalance code-- generated coins with between 100 and 119 confirmations were not being counted in the balance of account "". |
||
|---|---|---|
| cryptopp | ||
| json | ||
| locale | ||
| obj | ||
| rc | ||
| xpm | ||
| base58.h | ||
| bignum.h | ||
| build-msw.txt | ||
| build-osx.txt | ||
| build-unix.txt | ||
| coding.txt | ||
| db.cpp | ||
| db.h | ||
| headers.h | ||
| init.cpp | ||
| init.h | ||
| irc.cpp | ||
| irc.h | ||
| key.h | ||
| license.txt | ||
| main.cpp | ||
| main.h | ||
| makefile.mingw | ||
| makefile.osx | ||
| makefile.unix | ||
| makefile.vc | ||
| net.cpp | ||
| net.h | ||
| noui.h | ||
| README.md | ||
| rpc.cpp | ||
| rpc.h | ||
| script.cpp | ||
| script.h | ||
| serialize.h | ||
| setup.nsi | ||
| sha256.cpp | ||
| strlcpy.h | ||
| ui.cpp | ||
| ui.h | ||
| ui.rc | ||
| uibase.cpp | ||
| uibase.h | ||
| uint256.h | ||
| uiproject.fbp | ||
| util.cpp | ||
| util.h | ||
Bitcoin integration/staging tree
Straw-man plan for Bitcoin development (open source vets, please slap me around and help make this better):
Developers work in their own trees, then submit pull requests when they think their feature is ready.
Requests get discussed (where? bitcoin forums?) and if there's broad consensus they're a good thing, well written, match coding style, etc. then they're merged into the 'master' branch.
master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.
We'll create feature branches if/when there are major new features being worked on by several people.