Yet another Coin Control Release [CLOSED]

[WilderedB]

Which would bypass the need for all this? Cool 

Thanks

[IVIasterZox]

+1

Love this Addon!

[CIYAM]

Looking very nice - hope to see it appearing in the next major release (although you can do this and more with raw tx's it is going to be helpful to have something so easy to use in the GUI itself).

[IVIasterZox]

Jea if we find it in the next official release it would be great

[MajorMiner]

+1 love the add-on!

[gramma]

Just reading this discussion has taught me a lot more about how bitcoin works. Looking forward to learning more.

As for backing up my wallet.dat, it always seemed easiest to just make a copy of that file, then encrypt and store the backup. In reading this thread, that also sounds like the most reliable backup.  Is it?  Does bitcoin-qt's wallet transfer across wallet clients?  When I upgrade to 0.9, will it be as straightforward as dropping my saved wallet.dat into the usual place?

[calian]

Does bitcoin-qt's wallet transfer across wallet clients?  When I upgrade to 0.9, will it be as straightforward as dropping my saved wallet.dat into the usual place?

It only seems to work for a limited number of upgrades. I tried pulling a v0.3 wallet out of storage with v0.8.1 and it puked. It looked like I could download every intermediate version of bitcoin and run them one at a time with it or just extract the keys with pywallet (my choice). I don't really know why previous wallet files aren't supported, there can't be that many changes in the file structure in that length of time.

[grue]

It only seems to work for a limited number of upgrades. I tried pulling a v0.3 wallet out of storage with v0.8.1 and it puked. It looked like I could download every intermediate version of bitcoin and run them one at a time with it or just extract the keys with pywallet (my choice). I don't really know why previous wallet files aren't supported, there can't be that many changes in the file structure in that length of time.

wallets should always be forward compatible, but backwards compatibility is tricky because there has been various updates to the wallet format since 0.3.x.

[Luke-Jr]

The only cases I am aware of people having trouble "upgrading" wallets, is really because their wallet got corrupted somewhere along the lines.

If Bitcoin-Qt (or any other Satoshi-based client) does not cleanly exit, your wallet.dat is not intact!
It will depend on the database/ subdirectory until you resolve it with a clean shutdown.
If that directory disappears on it (or is replaced, etc), you may be losing money.

[Dabs]

0.8.2 final has been released. (of the main bitcoin-qt reference client.)

[ShadowOfHarbringer]

0.8.2 final has been released. (of the main bitcoin-qt reference client.)

But it does not contain CoinControl.

[Birdy]

0.8.2 final has been released. (of the main bitcoin-qt reference client.)

But it does not contain CoinControl.

Yes :/

[Dabs]

0.8.2 final has been released. (of the main bitcoin-qt reference client.)

But it does not contain CoinControl.

Yes :/

Not yet. I just bumped this thread in the hopes that whoever made the previous version will make an updated version with Coin Control.

[drrussellshane]

Coin Control is crucial!

[grue]

Sipa has an up-to date branch for coincontrol. I have built it using gitian in my build VM. (VMWare Ubuntu guest, Windows 7 x64 host).

My Windows build¹: bitcoin-0.8.2-sipa-coincontrol-win32.zip (SHA b7bc93cdaacbe24b42bff6714d59a9fcc49e85dc)
linux users: do it yourself. you probably know how to do it and you don't have to trust me.
mac users: sipa's build script doesn't build mac (I think). sucks to be you, I guess.




summary of my build instructions:

Code:

git clone -b coincontrol git://github.com/sipa/bitcoin.git
git tag -a v0.8.2-sipa-coincontrol -m 'sipa coincontrol'
./bitcoin-build.sh v0.8.2-sipa-coincontrol

http://bitcoin.sipa.be/builds/bitcoin-build.sh.txt

¹Standard disclaimer: While I'm confident my host system is virus free, and the probability of a virus infecting VM guests is low, I can not guarantee the build is clean. Hashes of the output files are generated within the VM, and are verified at the time of upload, so the risk of tampering in transit is low. However, audits of my build are always welcome.

[phelix]

[...CoinControlForThePeople...]

Sweet.

[cozz]

update:

• v0.8.2
• Updates to the new dust logic
  
  • if you enter dust as recipient amount the label Low Ouput shows "DUST"
  • fee is calculated correctly according to dust, this is when change would be dust, its added to the fee
  • actual dust threshold is 5460 satoshis

[hahahafr]

Question: Why is not coincontrol idea/code implemented in the bitcoin-qt client?

[DannyHamilton]

Question: Why is not coincontrol idea/code implemented in the bitcoin-qt client?

The bottleneck for getting this pulled is testing.

It needs a thorough test plan that tries to test edge cases where things might break, and then it needs people to carry out that test plan to make sure it is solid. "It works for me" isn't good enough for wallet-touching code.

See https://github.com/bitcoin/QA  for a suggested process.

[binaryFate]

How to proceed if one wants to help with testing?