Yet another Coin Control Release [CLOSED]

[Dabs]

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

grue, cozz, what's the difference between your builds? cozz is smaller (probably compressed) and doesn't include the warning message. But otherwise, are they the same?

[1714994954]

1714994954

[1714994954]

1714994954

[cozz]

grue, cozz, what's the difference between your builds? cozz is smaller (probably compressed) and doesn't include the warning message. But otherwise, are they the same?

grues doesnt include the Updates to the new dust logic. Also grues is based on some development snapshot, while mine is based on the latest stable version 0.8.2.

[grue]

grue, cozz, what's the difference between your builds? cozz is smaller (probably compressed) and doesn't include the warning message. But otherwise, are they the same?

mine is based on sipa's branch, but it's otherwise the same as 0.8.2. The warning about not being a release version is there because I was too lazy to edit it out. Also, cozz's build is packed with UPX, hence why it's so small.

[ShadowOfHarbringer]

Is this stable enough for everyday usage ?

I'm considering installing it.

[Dabs]

I've been using Cozz's build for awhile. I don't seem to have a problem. Not yet anyway. I'm only holding less than 100 BTC though.

[cozz]

Using cozz version for few days now, no bugs found whatsoever. One feature request though, it would be cool if numbers on right to "Amount"
and "Minus Fee" are selectable so that one just selects them and copy / paste to BTC amount field. It would make sending the exact "Minus Fee"
amount faster and easier (moving all selected inputs - fee to some address).

you can copy to clipboard. simply direct right click.

[Dabs]

I'm not sure about your particular transaction, but on main net with real bitcoins it works like this:

1. select inputs or rather, select unspent outputs. Only those selected will be used. Everything in those outputs will be used.
2. pay to 1bitcoinaddress. If there is change, you can send it back to a custom change address which can be the same as any of the addresses used by an unspent output.
3. add more recipients as you need, or spend everything so you don't have change.

I have no experience with newly mined coins with coin control, but I believe new coins can only be used after several blocks or confirmations, like 144 or 150 or something, I forgot exactly.

[Abandon]

What do you mean by change? What is change? What change? What kind of change? What is a change address? I feel like I should know what this is, but I don't.

The change input field overflows to the right without being dynamic, as well as the change coin information when using the smallest default size for the client. I'm sure there's enough room to fit it all compactly.

[Dabs]

new coins can only be used after several blocks or confirmations, like 144 or 150 or something, I forgot exactly.

120 with Bitcoin, 520 with PPCoin, etc.

Where is this info? I can't seem to find it on the wiki. Maybe it's in the source code? Anyway, that just means you need to wait a little bit less than a day to use newly mined bitcoins, or about 20 hours.

[kerhac]

Hi. Thanks for the coin control.
Waiting for coin control in 0.8.3

[cozz]

update: v0.8.3

[Birdy]

Great!
Thank you very much for your work

[kerhac]

update: v0.8.3

Yeah, Thank you very much

[drrussellshane]

It works for me. Thanks!

[phelix]

You are welcome to vote for Coin Control as Bitcoin Project of the Quarter:
https://bitcointalk.org/index.php?topic=251087.0

[phelix]

I would like to build on Windows myself (using EasyWinBuilder;)). Unfortunately the github link is not working any more and the linux source archive seems to be missing the Qt project file.

Trying Sipa's branch...

[mandros]

new coins can only be used after several blocks or confirmations, like 144 or 150 or something, I forgot exactly.

120 with Bitcoin, 520 with PPCoin, etc.

Where is this info? I can't seem to find it on the wiki. Maybe it's in the source code? Anyway, that just means you need to wait a little bit less than a day to use newly mined bitcoins, or about 20 hours.

Here: https://en.bitcoin.it/wiki/Protocol_rules#.22tx.22_messages

Rule 12. For each input, if the referenced output transaction is coinbase (i.e. only 1 input, with hash=0, n=-1), it must have at least COINBASE_MATURITY (100) confirmations; else reject this transaction.

The bitcoin client might decide to wait longer, but below 100 confirmations the network would reject the transaction.

[cozz]

I would like to build on Windows myself (using EasyWinBuilder;)). Unfortunately the github link is not working any more and the linux source archive seems to be missing the Qt project file.

Trying Sipa's branch...

I updated the source code link now

[phelix]

I would like to build on Windows myself (using EasyWinBuilder;)). Unfortunately the github link is not working any more and the linux source archive seems to be missing the Qt project file.

Trying Sipa's branch...

I updated the source code link now

Thanks!

Before I dump my time into it... do you also have a hint on this one?

Code:

g++ -Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -Wl,-s -mthreads -Wl,-subsystem,windows -o release/bitcoin-qt.exe object_script.bitcoin-qt.Release  -L'c:/Qt/4.8.5/lib' -lmingwthrd -lmingw32 -lqtmain build/bitcoin-qt_res.o -Llibs/miniupnpc-1.8 -lminiupnpc -liphlpapi C:/_temp/_bitcoin_0.8.3_coincontrol/src/leveldb/libleveldb.a C:/_temp/_bitcoin_0.8.3_coincontrol/src/leveldb/libmemenv.a -lshlwapi -Llibs/boost_1_54_0/stage/lib -Llibs/db-4.8.30.NC/build_unix -Llibs/openssl-1.0.1e -lssl -lcrypto -ldb_cxx -lws2_32 -lshlwapi -lmswsock -lole32 -loleaut32 -luuid -lgdi32 -lboost_system-mgw46-mt-sd-1_54 -lboost_filesystem-mgw46-mt-sd-1_54 -lboost_program_options-mgw46-mt-sd-1_54 -lboost_thread-mgw46-mt-sd-1_54 -lboost_chrono-mgw46-mt-sd-1_54 -lQtGui4 -lQtNetwork4 -lQtCore4 
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x1cda): undefined reference to `WalletModel::listLockedCoins(std::vector<COutPoint, std::allocator<COutPoint> >&)'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x2077): undefined reference to `WalletModel::isLockedCoin(uint256, unsig ned int) const'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x2324): undefined reference to `WalletModel::unlockCoin(COutPoint&)'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x263e): undefined reference to `WalletModel::lockCoin(COutPoint&)'
...

[cozz]

Before I dump my time into it... do you also have a hint on this one?

Code:

g++ -Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -Wl,-s -mthreads -Wl,-subsystem,windows -o release/bitcoin-qt.exe object_script.bitcoin-qt.Release  -L'c:/Qt/4.8.5/lib' -lmingwthrd -lmingw32 -lqtmain build/bitcoin-qt_res.o -Llibs/miniupnpc-1.8 -lminiupnpc -liphlpapi C:/_temp/_bitcoin_0.8.3_coincontrol/src/leveldb/libleveldb.a C:/_temp/_bitcoin_0.8.3_coincontrol/src/leveldb/libmemenv.a -lshlwapi -Llibs/boost_1_54_0/stage/lib -Llibs/db-4.8.30.NC/build_unix -Llibs/openssl-1.0.1e -lssl -lcrypto -ldb_cxx -lws2_32 -lshlwapi -lmswsock -lole32 -loleaut32 -luuid -lgdi32 -lboost_system-mgw46-mt-sd-1_54 -lboost_filesystem-mgw46-mt-sd-1_54 -lboost_program_options-mgw46-mt-sd-1_54 -lboost_thread-mgw46-mt-sd-1_54 -lboost_chrono-mgw46-mt-sd-1_54 -lQtGui4 -lQtNetwork4 -lQtCore4 
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x1cda): undefined reference to `WalletModel::listLockedCoins(std::vector<COutPoint, std::allocator<COutPoint> >&)'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x2077): undefined reference to `WalletModel::isLockedCoin(uint256, unsig ned int) const'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x2324): undefined reference to `WalletModel::unlockCoin(COutPoint&)'
./build/coincontroldialog.o:coincontroldialog.cpp:(.text+0x263e): undefined reference to `WalletModel::lockCoin(COutPoint&)'
...

looks like you are using the original bitcoin-qt.pro, not the new one. I have tested the code I gave you again, it sure compiles for me.