Topic: Please test (if you dare): next-test 2012-07-11 (Read 1822 times)
The "verify message" option is helpful to have right in the GUI, since the "sign message" is there.
Also, the coin control feature will be pretty damn handy, although I have not yet tested sending or receiving any coins with this version.
Also, the coin control feature will be pretty damn handy, although I have not yet tested sending or receiving any coins with this version.
next-test is a branch of the mainline bitcoind & Bitcoin-Qt with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details).
Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLET
Today's next-test includes the following pull requests (green are merged now; red are disputed):
- Parse URIs with non-BTC amounts
- -acceptnonstdtxn option to skip "non-standard transaction" checks
- Optimized binary-to-hex converter (ToHex)
- Specify fees explicitly via JSON-RPC
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
- BIP22: getmemorypool
- New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined
- Relay and accept transactions that personally benefit the user
- Refactor CreateNewBlock transaction selection algorithm
- Bugfix: getwork/getmemorypool: NULL pindexPrev across CreateNewBlock, in case it fails
- CreateNewBlock: Check that the produced CBlock is acceptable
- Issue1234
- Add -proxytoo option, which allows proxy use non-exclusively, unlike the -proxy option.
- Quieter initial block download
- Who doctored.... never was very useful, now only for the debuggers...
- Show when node is misbehaving, not just at the point that it gets banned...
- getmemorypool: longpolling support
- Coin Control
- Show how long AcceptBlock() takes to process.
- Refactor transaction/accounting time
- Make truncating the debug.log file an option.
- Treat generation (mined) transactions less different from receive transactions
- Show more significant bytes of block hashes.
- No need to log start time if it's already being done on every line.
- Make IPv6 support optional again (defaults to enabled)
- write used OpenSSL library version to debug.log
- Add new P2P command and response: "getcmds", "cmdlist"
- add CWalletTx::GetImmatureCredit() and use it in CWallet::GetImmatureBalance()
- RPC: lock push-down, preparing for parallelization opportunities
- CBigNum: Convert negative int64 values in a more well-defined way
- Add support for a cjdns network type
- RPC: add 'getnetstats' op, to return data on messages and peers
- Use linker-arguments only when linking
- Give threads a recognisable name to aid in debugging
- Transition to requiring block height in block coinbases
- improve dust spamming prevention algorithm
- RPC: Add per-message statistics to 'getpeerinfo'
- Increase the size of adressbookpage.ui in order to fix issue #1062
- Addnode optimization and addnode access via RPC
- Upgrade and Shared Lock support and locking test cases.
- update Boost version to 1.49 for Windows in the Qt project file
- IPC-server hardening and update
- CHashWriter that does SHA256 in-place during serialization
- GUI: optionsdialog cleanup
- GUI: optionsmodel cleanup
- fix for build.h regeneration failure when compiling on Windows
- (UI) Persistently poll for balance change when number of blocks changed
Bugs found:
Jump to: