Bitcoin Forum

---

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

• Windows: installer (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120506/bitcoin-next-test-20120506-win32-setup.exe) ‖ zip (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120506/bitcoin-next-test-20120506-win32.zip) (sigs (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20120506/SHA256SUMS.asc))
• Source code: git (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/shortlog/refs/tags/next-test_20120506) ‖ tar.gz (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20120506.tar.gz) ‖ zip (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20120506.zip)

Today's next-test includes the following pull requests (green are merged now; red are disputed):

• Typo-tolerant (optimized) Base58 parser (https://github.com/bitcoin/bitcoin/pull/552)
• Parse URIs with non-BTC amounts (https://github.com/bitcoin/bitcoin/pull/553)
• -acceptnonstdtxn option to skip "non-standard transaction" checks (https://github.com/bitcoin/bitcoin/pull/559)
• Optimized binary-to-hex converter (ToHex) (https://github.com/bitcoin/bitcoin/pull/562)
• FastGetWork optimization (https://github.com/bitcoin/bitcoin/pull/565)
• Specify fees explicitly via JSON-RPC (https://github.com/bitcoin/bitcoin/pull/570)
• Added 'immature balance' for miners. Only displayed if the balance is > 0 (https://github.com/bitcoin/bitcoin/pull/837)
• gettransactions() for non-wallet transactions (https://github.com/bitcoin/bitcoin/pull/841)
• Add -loadblock to load from an external blk000?.dat file (https://github.com/bitcoin/bitcoin/pull/883)
• More details for getblock and gettransaction (https://github.com/bitcoin/bitcoin/pull/886)
• Add a menu option and dialog to verify a signed message (https://github.com/bitcoin/bitcoin/pull/906)
• Reopen log file on SIGHUP (https://github.com/bitcoin/bitcoin/pull/917)
• Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC) (https://github.com/bitcoin/bitcoin/pull/929)
• Bugfix: BIP22: getmemorypool (https://github.com/bitcoin/bitcoin/pull/936)
• New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined (https://github.com/bitcoin/bitcoin/pull/989)
• URI-handling code update - safety check and notification (https://github.com/bitcoin/bitcoin/pull/1002)
• coin control / less change / refactor coin selection (https://github.com/bitcoin/bitcoin/pull/1017)
• IPv6 node support (https://github.com/bitcoin/bitcoin/pull/1021)
• massive URI-handling / IPC server re-work (https://github.com/bitcoin/bitcoin/pull/1023)
• Add UI RPC console / debug window (https://github.com/bitcoin/bitcoin/pull/1075)
• Allow Qt to wrap long tooltips (fixes #1063) (https://github.com/bitcoin/bitcoin/pull/1090)
• Multithreaded JSON-RPC with HTTP 1.1 Keep-Alive support (https://github.com/bitcoin/bitcoin/pull/1101)
• utility functions cleanup / update (https://github.com/bitcoin/bitcoin/pull/1134)
• Trim trailing whitespace in src/*.{cpp,h} (https://github.com/bitcoin/bitcoin/pull/1170)
• Tor hidden service support (https://github.com/bitcoin/bitcoin/pull/1174)
• Move GetStartOnSystemStartup and SetStartOnSystemStartup to GUI code (https://github.com/bitcoin/bitcoin/pull/1178)
• Fix final sign comparison warnings (https://github.com/bitcoin/bitcoin/pull/1180)
• fix for #952 (send coins tab glitch) (https://github.com/bitcoin/bitcoin/pull/1189)
• Don't show grids for address book and transaction tables (https://github.com/bitcoin/bitcoin/pull/1193)
• Prevent stuck download: correct solution (https://github.com/bitcoin/bitcoin/pull/1196)
• Replace BDB-managed addr.dat with bitcoin-managed ipaddr.dat (https://github.com/bitcoin/bitcoin/pull/1198)
• signmessage: auto-select signature when field is focused/clicked (https://github.com/bitcoin/bitcoin/pull/1199)
• add placeholder text to address field (like in sendcoins dialog)... (https://github.com/bitcoin/bitcoin/pull/1204)
• Fine-grained UI updates (https://github.com/bitcoin/bitcoin/pull/1205)
• small passphrasedialog update (capsLabel / maxLength) (https://github.com/bitcoin/bitcoin/pull/1206)
• harmonize the use of ellipsis ("...") in the GUI (https://github.com/bitcoin/bitcoin/pull/1211)
• move many overviewpage settings from code to ui XML-file... (https://github.com/bitcoin/bitcoin/pull/1212)

Bugs found:

• ipaddr.dat doesn't start the first time (https://github.com/bitcoin/bitcoin/pull/1198#issuecomment-5537982)
• RPC Console no such signal (https://github.com/bitcoin/bitcoin/pull/1075#issuecomment-5539795)
• Hard to read transaction list without grid lines (https://github.com/bitcoin/bitcoin/pull/1193#issuecomment-5541163)

Note: This is not vulnerable to CVE-2012-2459 (https://bitcointalk.org/?topic=81749)

Under WinXP, I got error "Couldn't open socket for incoming connections (socket returned error 10047)".

No other bitcoin is running (on first run after boot). Tested with empty wallet folder (starting from scratch).

db.log:
Database handles still open at environment close
Open database handle: blkindex.dat/main

debug.log:
....
Done loading
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Error: Couldn't open socket for incoming connections (socket returned error 10047)
18.5.2012 09:06:04 Flushing wallet.dat
Flushed wallet.dat 0ms
EnvShutdown exception: DbEnv::close: Invalid argument (22)

Montoring

Can you confirm whether IPv6 is enabled or not?

I am away from that particular computer right now (and will be for next week, too). But IPv6 was definitely not used, not sure, if there is some IPv6 layer installed (probably not).
BTW, that PC has 2 ethernet NICs (plus some virtual connections like those from VMWare or OpenVPN). Hope this helps.
The standard 0.6.2 does work fine, connects without problems.

IPv6 had some major changes between this next-test and being merged into master. Please test the new next-test due out sometime soon and see if it works for you.

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2459

https://bitcointalk.org/?topic=81749