Please test (if you dare): next-test 20120519

[Luke-Jr]

Superceded with next-test 2012-06-21

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 ‖ zip (sigs)
• Source code: git ‖ tar.gz ‖ zip

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)
• FastGetWork optimization
• Specify fees explicitly via JSON-RPC
• Reopen log file on SIGHUP
• 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
• URI-handling code update - safety check and notification
• massive URI-handling / IPC server re-work
• Relay and accept transactions that personally benefit the user
• Trim trailing whitespace in src/*.{cpp,h}
• Tor hidden service support
• Fine-grained UI updates
• 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
• Signbugs
• Reorganize(): remove spurious TxnAbort()
• Get rid of snprintf (except one) with fixed buffers, shorten code
• Show block timestamp
• Add -proxytoo option, which allows proxy use non-exclusively, unlike the -proxy option.
• translation updates / string updates
• Filter out whitespace and zero-width non-breaking spaces in address field validator
• Who doctored.... never was very useful, now only for the debuggers...
• Should not be T minus, as this indicate duration to future event.
• Unless debugging, show a more useful format for the askfors
• mapAlreadyAskedFor gets additions when AlreadyHave()
• ECDSA signature optimization and more DoS prevention
• RPC: add client startuptime to RPC getinfo
• GUI: add an icon for Debug logfile -> Open in the RPC console
• Update Header Licenses
• getmemorypool: longpolling support
• Coin Control / less change / refactor coin selection
• remove strncasecmp() + strnicmp() calls use boost::algorithm::istarts_with()

[R-]

Could you make one thread?

[BCB]

Error: Couldn't open socket for incoming connections (socket returned error 10047)

[Luke-Jr]

Error: Couldn't open socket for incoming connections (socket returned error 10047)

Try -onlynet=IPv4

[BCB]

worked.

[Luke-Jr]

worked.

Can you detail your OS version and system configuration?

[BCB]

XP Pro 2002 SP3

[Pieter Wuille]

Error: Couldn't open socket for incoming connections (socket returned error 10047)

Is that error fatal?

[BCB]

No. 

https://i.imgur.com/TvKXj.png

I clicked ok and the client opened out of sync.  I think it might have synced when the block chain downloaded.

After your message. I created a default bitcoin.conf in \Application Data\bitcoin and added
onlynet=IPv4

and it opened fine after restart.

I haven't tried any other actions.

[bitlane]

getmemorypool: longpolling support

Does this mean longpolling for solo mining ?

Would it be beneficial to try this build for solo mining, or is this more intended for every day wallet use 'testing' ?

[Luke-Jr]

getmemorypool: longpolling support

Does this mean longpolling for solo mining ?

Only with a getwork server in between, like Eloipool or P2Pool - but neither of them support longpolling yet (unless Forrest has already added it).

Would it be beneficial to try this build for solo mining, or is this more intended for every day wallet use 'testing' ?

Compared to all the released versions, this build might perform better for (direct) solo mining due to the multithreaded JSON-RPC server (already merged into git master, so not listed specifically for next-test).

[Red Emerald]

Got a bitcoind tor hidden service running with -discover

p2hwc26zdsrqxiix.onion

Seems to be running great! I'll send some transactions to/from it soon.

[pc]

Is there any chance of getting a Mac build of these tests?

[Luke-Jr]

Is there any chance of getting a Mac build of these tests?

That would be one result of my deterministic Mac binaries project.

[Diapolo]

Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process .

Dia

[phelix]

Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process .

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)

[Red Emerald]

Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process .

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)

Cant you just "git clone git@github.com:luke-jr/bitcoin -b next-test" and always have the latest? That's what I do.

[Diapolo]

Luke is there any newer next-test? I'm asking, because that is always a good source to know, if own patched break the build process .

Dia

would be nice to have a central place to see the latest one.

(coin control for everybody!)

Cant you just "git clone git@github.com:luke-jr/bitcoin -b next-test" and always have the latest? That's what I do.

As luke-jr uses cross-compilation or perhaps the official release-process via Gitian for this, it will show if my patches break something I can't detect, because I'm compiling own builds on Windows.

Dia

[Luke-Jr]

Superceded with next-test 2012-06-21