Thanks to the anonymous contributor who sent me reverse-engineered documentation of the BitFORCE Single firmware upload protocol, BFGMiner 2.6.5+ now include a tool for flashing BitFORCE Singles on Linux. I don't know if it works for other BFL devices, and I make no guarantees that this won't fry your device - but it does work for mine at least To use, simply build BFGMiner with BitFORCE support (enabled by default) and run (substituting your device's path and the firmware filename you want to flash): bitforce-firmware-flash /dev/ttyUSB0 alphaminer_832.bfl
|
|
|
next is a branch of the mainline bitcoind & Bitcoin-Qt with only pull requests planned for the next version (right now, 0.7) merged into it, to aid in testing them. This branch can be used to test what will likely become 0.7rc1 very soon. 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 WALLETnext - only pull requests planned for merging into 0.7 soon: next-test - everything possible; 0.7, beyond, disputed, etc: Today's next includes the following pull requests (green are merged now): next-test also includes the following pull requests (green are merged now; red are disputed, grey are abandoned):
|
|
|
Note that the poll accepts votes for multiple items, and you can change your votes at any time (Edit: not anymore, thanks to this forum being buggy...). Please only vote if you meet the criteria for the options! Feel free to ask any questions in the thread...
After much discussion, I am leaning toward this two-part plan (or something like it)...
1. Setup new Eligius-Hu pool
This will have the PPLNS×8 reward system: when a block is found, its reward is divided equally* across the last <difficulty> times 8 shares. The number of shares has been chosen to be <difficulty> times 8 so that there is a 99.9% chance of any given share being paid; on average, each share will be paid 8 times.
That means that at the current difficulty 2,190,865, a block found today would reward 0.0000028527545056404662 BTC for each of the 17,526,920 shares preceding it, regardless of what "round" those shares were found in. After 8 blocks, assuming they are all within those 17,526,920 shares since the share was submitted, that share will have been paid a total of 0.00002282203604512373 BTC (equivalent to 100% PPS). If the pool gets lucky or unlucky, we might find more or less blocks within that window, all of which the share is paid for. This does potentially increase variance a bit, but an 8 block window should be enough to minimize it.
This summary is slightly inaccurate, as the shares will be of dynamic difficulty depending on your hashrate, and the value of each share will depend on your share-difficulty and the current block difficulty at the time the share is submitted, to avoid being hoppable during difficulty changes, and gracefully scale to ASICs as they are available.
There will also be a few under-the-hood changes to handle ASICs on Eligius-Hu: (new) BIP22 mining protocol support, and elimination of the permanent eternally-growing share database. The elimination of this database means the current Artefact2 stats will not work with this new pool unless someone steps up to update it. wizkid057 plans to write an updated stats interface.
You can express your support for this new pool only if you plan to use it by voting for the first poll option ("new Eligius-Hu"). If you are a current Eligius-Ra miner, and plan to leave the pool because you don't like Eligius-Hu, vote "dislike Hu" (option 5).
The default pool for the mining.eligius.st hostname will be changed to Eligius-Hu about a week after it goes live (miners can specify an explicit pool to use with the ra.mining.eligius.st or hu.mining.eligius.st hostnames). If you plan to mine on either Eligius-Ra or Hu at that time, and think the default should be changed immediately upon its availability, vote "Hu default" (option 2). If you explicitly think waiting a week more is a good idea, you can vote "Extra week at Ra" (option 6). Regardless of these votes, hu.mining.eligius.st is currently functional as a redirect to Ra, and will switch to Hu immediately when it comes online.
2. Gradual shutdown of Eligius-Ra pool
Since PPLNS×8 does not allow for carryover of existing Extra Credit (EC), Eligius-Ra will continue to operate until the block subsidy halves to 25 BTC (I would need to rewrite the pool software to make it survive the 25 BTC drop). Because of the near Miners who have a lot invested in EC may wish to continue to mine Eligius-Ra until it has been paid to their satisfaction.
Due to the extreme improbability of Eligius-Ra catching up to 100% PPS in this timeframe, it is proposed that it be changed to "SMPPSAM" (ie, an Active Miners variant) until it closes: this would mean inactive miners on Ra would not receive EC until/unless all the active miners are paid an amount equal to their current earnings first. Miners who have EC on Eligius-Ra or plan to be mining on it at that time may vote to support (option 3) or oppose (option 4) the Active Miners rule.
Edit: Note that with the Active Miners rule enabled, ex-miners who have unpaid balances under 0.67 BTC will finally reach the 1 week inactivity and get their payout. Also note that when Eligius-Ra finally closes, all unpaid balances (not EC!) will be paid out regardless of the amount.
Please note that Eligius-Ra may not be updated to handle ASIC load!
Poll option G is for future use should someone propose any other changes: do not vote on it until it is defined. If you have any possibly better ideas, please do bring them up!
|
|
|
I built a "final-state" blk0001.dat with the first 188529 blocks (0 to 188528), in order with no orphan blocks. I loaded it into a bitcoind with BlueMatt's transaction-index-pruning code, and produced a 151 MB blkindex.dat to go with it. This accomplishes reducing the overall disk space used by my 19 (!) bitcoin data directories: - This blk0001.dat can be hard linked between them all - saves about 36 GB
- blkindex.dat is much smaller, since it has all the spent transactions pruned
So here it is for anyone else who wants it (thanks to jrmithdobbs and wizkid057 for 100mbit and gigabit seeds!): Tip: If you copy your current blk0001.dat into your download directory and rescan, you may be able to skip a large chunk of the download. I intentionally did not compress blk0001.dat; since you need this file anyway, the remaining data (compressed) only takes up 64 MB - please continue to seed! Edit: Please note that if you use git master (0.7+), you must not use the included blkindex.dat, or it will break getrawtransaction - use the 0.7 instructions in the INSTALL.txt file!
|
|
|
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 WALLETToday'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:
|
|
|
This is the Linux leapsecond bug. To fix it, either reboot or run (with proper permissions):
|
|
|
I've hidden the 4 private keys making up P2SH (3-of-4) address 3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQX on various Bitcoin-related websites over the past month. To win, you (or your team of cooperating players) need to: - Find at least 3 of the 4 private keys
- Figure out what order they go in
- Figure out how to redeem the P2SH multisig
- Send the prize coins to an address you control
Addresses: - 1Bvvy2EqCLtf1yz8WXHwEnBDbqQ8QS7NFC
- 19ie41obBNDPqTE67tqoy1aKUXX1cdbcR9
- 1KZxJQNGfoof3RpdZdNkz6Ukzkz2cL7u6M
- 1APEu1fpTgUrwJrB123Gf2zT14PufLCWSs
Currently the reward is 2.25 BTC; I encourage others to add to this - just send to 3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQXLooks like someone won. wd.
|
|
|
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 WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed): - IPv6 RPC using asynchronously accepted connections
- 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
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
- BIP22: getmemorypool
- Stop processing messages on full send buffer and dont disconnect.
- New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined
- massive URI-handling / IPC server re-work
- Relay and accept transactions that personally benefit the user
- Tor hidden service support
- Buffer block downloading and commit/check blocks in parallel
- 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
- Show block timestamp
- 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...
- mapAlreadyAskedFor gets additions when AlreadyHave()
- getmemorypool: longpolling support
- Coin Control
- Refactor transaction/accounting time
- Make truncating the debug.log file an option.
- CHub Rev. 3
- 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.
- Cblockstore class
- Make IPv6 support optional again (defaults to enabled)
- Implement raw transaction RPC calls
- Introduce -tracenet option, thereby quieting some redundant debug messages
- GUI: show used OpenSSL library version in about dialog
- write used OpenSSL library version to debug.log
- GUI: merge sign/verify message into a single window with tabbed UI
- Add new P2P command and response: "getcmds", "cmdlist"
- walletmodel: only update cached balances / transaction numbers and emit ...
- add CWalletTx::GetImmatureCredit() and use it in CWallet::GetImmatureBalance()
- Document Gitian build process for Mac OS X bitcoind binary
- Skip tons of duplicate GetHash() calls in Block Commit Thread
- RPC: lock push-down, preparing for parallelization opportunities
- fix a memory leak in key.cpp
- CBigNum: Convert negative int64 values in a more well-defined way
- Add support for a cjdns network type
Bugs found: 5JiDHgjbkS2uKnMKHo1Nw8zrJp2t8wZ4QmJPFi9W9DQjjFgYFG7
|
|
|
bitcoind and Bitcoin-Qt version 0.6.3 release candidate 1 are now available, in another thread.bitcoind and Bitcoin-Qt version 0.5.6 release candidate 3 ( sigs) are now available for download at: bitcoind version 0.4.7 release candidate 3 ( sigs) is now available for download at: bitcoind and Bitcoin-Qt version 0.6.0.9rc1 is also tagged in git. These are bugfix-only releases. Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr. BUG FIXES- Fixed a serious denial-of-service attack that could cause the bitcoin process to become unresponsive. Thanks to Sergio Lerner for finding and responsibly reporting the problem. (CVE-2012-3789)
- Fix BIP16 validation to not enforce non-standard size limit of 200 bytes. Fixes being stuck at block 177617 (0.4 and 0.5)
- Do not select first address automatically in the address book when sending (Bitcoin-Qt)
- Hopefully final fix for the stuck blockchain issue
- Fix various database crashes and improve error checking
- Properly escape double-quote character in strings when exporting CSV
- Fix #952 by checking if we have a new address or an updated label
- Don't call exit() in Shutdown() for Bitcoin-Qt (fixes a tray-icon issue)
- Filter out whitespace and zero-width non-breaking spaces in Bitcoin address validator
- Properly store source addresses in database
- Remove redundant tooltip on optional transaction fee. Fixes #1218 (Bitcoin-Qt)
- Change initial balance on Overview page from "123.456 BTC" to "0 BTC" to not confuse users, whom might see it before we initialize with the real wallet balance (Bitcoin-Qt)
- Fix various places where Bitcoin-Qt was being shutdown improperly
- Hide UI immediately after leaving the main loop (Bitcoin-Qt)
- Various documentation corrections and debugging fixes
Thanks to everybody who contributed code or helped test this release: Sergio Lerner Pieter Wuille Philip Kaufmann Luke Dashjr Wladimir J. van der Laan Matt Corallo Jeff Garzik R E Broadley Fordy Gavin Andresen Michael Hendricks Chris Moore Ricardo M. Correia Christian von Roques Peter Todd
|
|
|
bitcoind and Bitcoin-Qt version 0.5.6 release candidate 2 ( sigs) are now available for download at: bitcoind version 0.4.7 release candidate 2 ( sigs) is now available for download at: bitcoind and Bitcoin-Qt version 0.6.0.8rc2 is also tagged in git. These are bugfix-only releases. Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr. BUG FIXES- Fix BIP16 validation to not enforce non-standard size limit of 200 bytes. Fixes being stuck at block 177617 (0.4 and 0.5)
- Do not select first address automatically in the address book when sending (Bitcoin-Qt)
- Hopefully final fix for the stuck blockchain issue
- Fix various database crashes and improve error checking
- Properly escape double-quote character in strings when exporting CSV
- Fix #952 by checking if we have a new address or an updated label
- Don't call exit() in Shutdown() for Bitcoin-Qt (fixes a tray-icon issue)
- Filter out whitespace and zero-width non-breaking spaces in Bitcoin address validator
- Properly store source addresses in database
- Remove redundant tooltip on optional transaction fee. Fixes #1218 (Bitcoin-Qt)
- Change initial balance on Overview page from "123.456 BTC" to "0 BTC" to not confuse users, whom might see it before we initialize with the real wallet balance (Bitcoin-Qt)
- Fix various places where Bitcoin-Qt was being shutdown improperly
- Hide UI immediately after leaving the main loop (Bitcoin-Qt)
- Various documentation corrections and debugging fixes
Thanks to everybody who contributed code or helped test this release: Pieter Wuille Philip Kaufmann Luke Dashjr Wladimir J. van der Laan Matt Corallo Jeff Garzik R E Broadley Fordy Gavin Andresen Michael Hendricks Chris Moore Christian von Roques Peter Todd
|
|
|
Background:Currently, before a new release of Bitcoin-Qt is published to SourceForge, it must be compiled by 3 different people who verify that they have produced the same exact binaries. This is done to protect against a variety of attack vectors: a single builder could include a trojan or backdoor into their binaries. No matter how much this person is trusted, their ability puts them at risk of being forced (eg, by gunpoint or legal action) to do so, or potential to do so accidentally (eg, if their build system is infected itself). Additionally, there is one person to impersonate or man-in-the-middle-attack, and the chance (5-10% in a person's lifetime, according to a quick Google) the person may begin to go insane. It also leaves open a question to the masses should that person die, of whether his successor is just as trustworthy. However, right now, these thrice-verified builds are only possible for Linux and Windows using the Gitian framework. So far, Gavin has been personally responsible for the Mac OS X binaries, and he (and the community) incurs all the risks above as a result. My proposal:I have succeeded in building bitcoind (the JSON-RPC server) for Mac OS X under Gitian, and verified that this build is deterministic (able to be compared with others' builds). In addition to the cross-compiler and dependencies of bitcoind, I have also succeeded in building the dependencies required for Bitcoin-Qt under Gitian - except for Nokia Qt itself. To build Qt, I need to go back to the cross-compiler and figure out how to get the Objective-C compiler working. Then I will need to configure Qt for cross-compiling using it, and ensure the output is deterministic enough to produce a deterministic Bitcoin-Qt build based on it. This is going to be a lot more work, especially since nobody seems to have ever cross-compiled Qt for Mac OS X before. Therefore, I am asking for donations to help fund completing this effort: 1D8jkYpkcJUQ6BJzjAATAEBjHdgVhvisAVP.S. My work thus far on this specific project is all published in these Gitorious repositories.
|
|
|
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 WALLETToday'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()
|
|
|
-----BEGIN PGP SIGNED MESSAGE-----Hash: SHA256
The cracker who stole 18kBTC from Bitcoinica was on IRC this morning giving them away. A number of us posted our addresses with the intent of returning the stolen coins to Bitcoinica. I have setup an address that will be handed over to Bitcoinica (as a wallet.dat file) at some point when they have figured out where I should send it. Therefore, if you have been sent any stolen coins and wish to return them, please forward them on to 1BPKHoL1sAVnfzxnH38RfXYYcHrEcniUKW ( see balance). Note that with Bitcoin-Qt, you will generally not be able to control which coins you are sending. Since a lot of people got the coins in their main wallet, I have backported coderrr's Coin Control to Bitcoin-Qt 0.6.2. Windows: installer or zipSource: tar.gze3d2ec5694f26eb5f45ea6244aa1c2792ac3e7c87113e0dfae827469eaf31499 bitcoin-0.6.2+coincontrol-win32-setup.exe a3a067273027232ef009c20a4e0e91410cd59820d7c80c89a45780ad3ba23426 bitcoin-0.6.2+coincontrol-win32.zip 42d04be61b340a17bf8ee8607079c90ddb067300cf1fbb041744c5e162f0bc1a bitcoin-0.6.2+coincontrol.tar.gzIf someone could post exact instructions on how to use Coin Control for this purpose, I'm sure it would be appreciated! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux)
iQQcBAEBCAAGBQJPuJzeAAoJEL0ClCQh9IifQJcf/0JV0HwtMuyBouLBbhBBMALd SZEQZGyWlWS7bg1eIXUcC+RuwD+MLRRAPKIvhQ+iFf7L9nO/kFzSyHP7Z9DAfVFM 5QU1eJhgSydYfxM6rnbzhxKq4Zeov5OhoAg3YuUZJmN+b/YSMmtTQ7XxcMRdkfod I+K1pgI8Tl1+IdLMa8i6ZG4KbBmUYkhnRMvPP0wTKUcQvRzpLXTERb9KY/+1ZfVs vyJqj9ghWUzgK1OuOUpOGsJ+QjJ1GkhFWLAmH6QuLewA4pgp1QKVKEzYbKxUjyd/ 0ioFSVecrRO+XayMp5AGkEflocu5w4W0SPhFSRgWEuv+uqhpHGYpF65O5SLvYZIc QChtbPkUHypAnkCeIyZPftwTFc38dw9UKARPlDbznST9dBpnrnxPFrL2ylrJUuDe gg5fWP6AnTD05le7/OA4xIVtq+OYCA+kLjHM7tnWjSZF7l5/pUeYH90lOuJRbDEe fme7HQ/kzKy7RaTdCroYKQFl/WBvRBb+aoLsF3cHZ39DJ2R7gdDvInlzkkXdu89q Ppav1JFIPiZPgD+vg1g+F320m3bOzrdfGBn1QUqXJzE3W/JJ1T8U7E+fGDvcOLW6 kXdcL3jeWfNU4NX80i/4xKUr5ii2DWe2b5H7L5jqydaySsmgmStmHnkAyDiAnKu5 aQwwzQ+u+xGOElunEEkhG4XAJ2Jcm/A52Y99RCRuMXjfNxLftGBg42o3WeC34jY2 r1eqaXo2fgPHuuVxo95NGeuvu3O9n9graG5ZYCD4mS9Vf+GX8alkJCHgda56TjEF kNHOjGAICZ1hLSk8ej9noetwqaxlc6dHWCP5sImCn7fkPxl0RUR+r/smWPK7hAOI bfL5bRQxTQULXGaC26qw8YkMHPrVZaQs+qS9M9ztwmG7/EPC4E0NVTNEwvnHqQih QP7hnfNN6EBDVKDvyXkW7Ja0Vk6V2R2zOPthO7ccbo863iPRFctYdqmwr7RP8OFc Umb2+EOzqItXJMRdpdzNudjphlRxYL3rXQUX7MsLPwpar/VysqlDdbqWC+PT3ht3 ECKE3IKfbDnidfF0QSm1U+BbpnDogcFzxd0v+w4YI6PJvAZeWbMT5G1pFfltYTdc f1ppIANVk/8a5GSTa7PXh/Dpv3TdT+nzD+W1AsmTAmVhw9sS9yYflFLLF6C8foNk iwStTP+9bXUdNFIdQRVb/MVFf085r9jNrbw5x9OpuhZEa/AAqhJaEsXooK0Yd10X jMfqKIlxq+/PKoZNLQLBWF4vOMOKOcQYAcSLbp8HO1qDKPbeS5wAgZtEsJ00gspr TsfvyAodFO6i44U6Epq73edpxMJMx27JURaqkkk236FSSk8frmCcqkD3qGREnnE= =zZ1y -----END PGP SIGNATURE-----
|
|
|
NOTE: This build seems to be unusable. Previous next-test is still available.
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 WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed): - Typo-tolerant (optimized) Base58 parser
- 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)
- Bugfix: 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
- change strings to Bitcoin (uppercase), where it is used as a noun and up...
- Encapsulate BDB environment inside new CDBEnv class
- make CheckDiskSpace() use 50 * 1024 * 1024 Bytes
- Signbugs
- Reorganize(): remove spurious TxnAbort()
- Get rid of snprintf (except one) with fixed buffers, shorten code
- Split BDB database blkindex.dat into multiple databases
- 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()
- Clarify license for debugwindow icon
- ECDSA signature optimization and more DoS prevention
- Win32: use _strnicmp (ISO C++) instead of deprecated strnicmp (POSIX) - V2
- GUI: add an icon for Debug logfile -> Open in the RPC console
- Update Header Licenses
- getmemorypool: longpolling support
- Shared code for wallet lock help and check
- Coin Control / less change / refactor coin selection
Bugs found:
|
|
|
I seem to recall people offering bounties for this functionality. I've implemented the miner side, so if you offered a bounty for this, please post and/or send here when satisfied: 123R1562U9BNAjh7h2QHNiJ44YTSx1oa8P Note this is mostly untested still, and I don't recommend mining with it until I've given it more sanity checking and had some peer review.I don't intend to implement the receiver-wants-to-explicitly-add-a-fee side, at this time. If people start offering bounties for that, I might change my mind.
|
|
|
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 WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed): Bugs found:
|
|
|
bitcoind and Bitcoin-Qt version 0.5.5 are now available for download at: bitcoind version 0.4.6 is now available for download at: bitcoind and Bitcoin-Qt version 0.6.0.7 are also tagged in git, but it is recommended to upgrade to 0.6.1. These are bugfix-only releases. Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr. BUG FIXES- Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
- Verify status of encrypt/decrypt calls to detect failed padding
- Check blocks for duplicate transactions earlier. Fixes #1167
- Upgrade Windows builds to OpenSSL 1.0.1b
- Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
- JSON-RPC listtransactions's from/count handling is now fixed
- Optimize and fix multithreaded access, when checking whether we already know about transactions
- Fix potential networking deadlock
- Proper support for Growl 1.3 notifications
- Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
- Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
- Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
- Missing error condition checking added
- Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
- Increase time ago of last block for "up to date" status from 30 to 90 minutes
- Show a message box when runaway exception happens (Bitcoin-Qt)
- Use a messagebox to display the error when -server is provided without providing a rpc password
- Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
- Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
- Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
- Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
- Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
- Work around issue in boost::program_options that prevents from compiling in clang
- Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
- Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
- Various trivial internal corrections to types used for counting/size loops and warnings
Thanks to everybody who contributed code or helped test this release: Wladimir J. van der Laan Luke Dashjr Jeff Garzik Pieter Wuille Matt Corallo Philip Kaufmann Dwayne C. Litzenberger Timothy Redaelli freewil Gavin Andresen Chris Moore Patrick Schneider cardpuncher graingert
|
|
|
Superceded with next-test 20120506next-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 WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed): Bugs found:
|
|
|
bitcoind and Bitcoin-Qt version 0.6.0.7 release candidate 1 are now available for download at: bitcoind and Bitcoin-Qt version 0.5.5 release candidate 1 are now available for download at: bitcoind version 0.4.6 release candidate 1 is now available for download at: These are bugfix-only releases. Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr. BUG FIXES- Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
- Verify status of encrypt/decrypt calls to detect failed padding
- Upgrade Windows builds to OpenSSL 1.0.1b
- Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
- JSON-RPC listtransactions's from/count handling is now fixed
- Optimize and fix multithreaded access, when checking whether we already know about transactions
- Fix potential networking deadlock
- Proper support for Growl 1.3 notifications
- Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
- Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
- Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
- Missing error condition checking added
- Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
- Increase time ago of last block for "up to date" status from 30 to 90 minutes
- Show a message box when runaway exception happens (Bitcoin-Qt)
- Use a messagebox to display the error when -server is provided without providing a rpc password
- Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
- Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
- Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
- Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
- Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
- Work around issue in boost::program_options that prevents from compiling in clang
- Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
- Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
- Various trivial internal corrections to types used for counting/size loops and warnings
Thanks to everybody who contributed code or helped test this release: Wladimir J. van der Laan Luke Dashjr Jeff Garzik Pieter Wuille Matt Corallo Philip Kaufmann Dwayne C. Litzenberger Timothy Redaelli freewil Gavin Andresen Chris Moore Patrick Schneider cardpuncher graingert
|
|
|
|