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

[Luke-Jr]

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

Also note this is the first next-test that excludes my Coinbaser enhancement. Click here for details.
It is also the first next-test to include coderrr's coin control features.

• Windows: installer ‖ zip (sigs)
• Source code: Git tag ‖ tar.gz ‖ zip

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

• coin control features: send from address(es), view address linkages, view all addresses (plus some improvements by Dooglus)
• Typo-tolerant (optimized) Base58 parser
• Parse URIs with non-BTC amounts
• Optimized binary-to-hex converter (ToHex)
• FastGetWork optimization
• Multithreaded JSON-RPC with HTTP 1.1 Keep-Alive support
• Specify fees explicitly via JSON-RPC
• Support for multiple local addresses
• Added 'immature balance' for miners. Only displayed if the balance is > 0
• gettransactions() for non-wallet transactions
• Toggle hide
• Add -loadblock to load from an external blk000?.dat file
• More details for getblock and gettransaction
• JSON-RPC call to accept transactions that don't meet acceptance fees
• Don't create change when it isn't necessary.
• Refactor SelectCoinsMinConf() and add unit tests.
• Add a menu option and dialog to verify a signed message
• Reopen log file on SIGHUP
• Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
• Add a pong message that is sent in reply to a ping.
• Bugfix: BIP22: getmemorypool
• Limit getheaders to a hard 2000.
• Added ability to respond to signals during Block Loading stage.
• fix filesystem paths in database code for WIN32
• Introduce explicit -walletupgrade option

[1715645205]

1715645205

[1715645205]

1715645205

[da2ce7]

While it is great that Luke has put the time into preparing these next-test builds . I just wanted to explain why the maroon pull patches are contested.

Typo-tolerant (optimized) Base58 parser

The problem is that this may (quite unlikely) correct to an unspendable address.

 

Parse URIs with non-BTC amounts

Support URI with Satoshi or Hex or (Tonal, that is just hex with funny characters).  Problem.  People want URI's to be easily human readable.

Optimized binary-to-hex converter (ToHex)

Danger of buffer overflow, (if there is a bug in the to hex code).  Virtually no real-life performance gain.

Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)

Tonal support, tonal is base 16 numbers with strange characters for the numbers higher than 9.
Problem: nobody cares about tonal other than Luke.

[Luke-Jr]

Optimized binary-to-hex converter (ToHex)

Danger of buffer overflow, (if there is a bug in the to hex code).  Virtually no real-life performance gain.

6% performance gain, to be specific.

Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)

Tonal support, tonal is base 16 numbers with strange characters for the numbers higher than 9.
Problem: nobody cares about tonal other than Luke.

Or from others' perspective, nobody cares about Bitcoin other than Luke.

[Serenata]

Any newer releases?
On my setup (Win7 64, main client v0.6, wallet upgraded) , bitcoin-next-test-20120324-win32 crashes all the time I liked coin control features.

[Luke-Jr]

Any newer releases?
On my setup (Win7 64, main client v0.6, wallet upgraded) , bitcoin-next-test-20120324-win32 crashes all the time I liked coin control features.

I'll probably spin another next-test pretty soon. Stay tuned

[Serenata]

Nice! Thaanks!!

[Luke-Jr]

This next-test has been superceded.

[beckspace]

Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)

Tonal support, tonal is base 16 numbers with strange characters for the numbers higher than 9.
Problem: nobody cares about tonal other than Luke.

I find very interesting the Tonal discussion. Computers use it all the time. Music also. And when I'm slicing pizza.

And astronauts:



http://history.nasa.gov/computers/Ch4-7.html

[rjk]

Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)

Tonal support, tonal is base 16 numbers with strange characters for the numbers higher than 9.
Problem: nobody cares about tonal other than Luke.

I find very interesting the Tonal discussion. Computers use it all the time. Music also. And when I'm slicing pizza.

And astronauts:

http://history.nasa.gov/computers/p126.jpg

http://history.nasa.gov/computers/Ch4-7.html

But do you use the fonts that nobody can read? The alternate name to throw people off the fact that it is just hex?

[Luke-Jr]

The alternate name to throw people off the fact that it is just hex?

Except it's not.

[beckspace]

Please, Luke, enlighten me.

Where did you see Tonal (or Hex) in Bitcoins?

I see that there is 21000000.00000000 Bitcoins, that's 16 numbers (is it a clue?)

But the units are decimals (0-9), so, where does it fits? Mathematically? (Something tells me that one or another type of measure will have non-round numbers).

I'd like to see examples of simple conversions so maybe I can grasp it.

[Luke-Jr]

Please, Luke, enlighten me.

Unlike the later invention of hexadecimal, which only provides digits for base 8*2 (and hijacks them from the Latin alphabet), Tonal also provides pronunciations (an, de, ti, go, su, by, ra, me, ni, ko, hu, vy, la, po, fy, ton), fractions (forbidden in hexadecimal), and units for measurement of length (the Earth's circumference is 1,0000 millmeters), time/circles/compass (each day is divided into 10 tims), capacity (1 gall = 1 cubic meter), weight (1 pon = 1 gall of water), power (1 effect = 1 pon lifted 1 meter in 1 timmill), money (cents, shillings, and dollars), postage stamps, the calendar (ANuary, DEbrian, TImander, GOstus, SUvenary, BYlian, RAtamber, MEsudius, NIctoary, KOlumbian, HUsamber, VYctorious, LAmboary, POlian, FYlander, TONborious), temperature/heat (10 temps = 100 celcius), music, and abacus/stchoty.

Where did you see Tonal (or Hex) in Bitcoins?

As no government has adopted Tonal for currency, there has been a void. The day I discovered Bitcoin, it seemed obvious it could fill this void.

I see that there is 21000000.00000000 Bitcoins, that's 16 numbers (is it a clue?)

But the units are decimals (0-9), so, where does it fits? Mathematically? (Something tells me that one or another type of measure will have non-round numbers).

I'd like to see examples of simple conversions so maybe I can grasp it.

There are technically 2,100,000,000,000,000 actual items in the Bitcoin protocol. For whatever reason, Satoshi chose to set the unit of "BTC" at 100,000,000 of these. TBC, on the other hand, is exactly 1,0000 (tonal, remember) items. Therefore, 1 TBC = 0.00065536 BTC and 1 BTC = 55.1 TBC (the wiki has a nice chart of units). Since the decimal and tonal units are fundamentally different, they can mostly function as independent currencies (for example, clients can detect whether a transaction is BTC or TBC based on its value) while still being directly exchanged between single-number-system users without confusion (since their client will only show the units they understand) and cooperating on mining efforts, adoption, etc.

[rjk]

The alternate name to throw people off the fact that it is just hex?

Except it's not.

Nice selective quoting/arguing, and dodging around the fact that it is a base 16 numbering system. Since it will never be used by the greater masses, there is no need to be worried about it. Just keep it the fuck out of my bitcoin client, thank you.