Requesting "Eligius" and "0-fee" patched builds for Windows...! 
Here you are: a 0-fee sir http://ifile.it/jyzwhpi . I'll talk to luke about the eligius version and make a binary soon.
Topic: Bitcoin version 0.3.22 - page 3. (Read 18188 times)
Here you are: a 0-fee sir http://ifile.it/jyzwhpi . I'll talk to luke about the eligius version and make a binary soon.
Windows 7 Pro x64, RPC command "getwork" causes the rpc server to lock up, thread uses full CPU usage (25% on Q6600.)
Application has to be terminated via task manager.
No issue in 0.3.21, no other rpc commands seem to cause any problems, just "getwork"
First discovered problem by launching a local GPU miner (Phoenix), then verified it was the getwork command by testing with PHP client and just using the bitcoin command line.
Tested in a XP VM, same result.
Application has to be terminated via task manager.
No issue in 0.3.21, no other rpc commands seem to cause any problems, just "getwork"
First discovered problem by launching a local GPU miner (Phoenix), then verified it was the getwork command by testing with PHP client and just using the bitcoin command line.
Tested in a XP VM, same result.
Forgot "-Preliminary development of double-secret CIA backdoor and un-anonymizing framework" in the notes.
bitcoin.org and weusecoins.com are still linking to the old version. As a result, in the just last few hours, we've gained ~100 0.3.21 users, and just a handful of 0.3.22 users. We still only have just 189 0.3.22 nodes online - barely more than at the end of RC testing. We need to do a better job of getting the word out.
What about a MacOS version?
This.
What about a MacOS version?
News: Version 0.3.21 is now available.
Thanks!
0.01 BTC - demands the commission 0.01 BTC 
0.10 BTC - hasn't proved to be true yet
Anyway I come back on 0.3.20.2.
At me with it problems aren't present.
Simply it would be desirable "the new" version
0.10 BTC - hasn't proved to be true yet
Anyway I come back on 0.3.20.2.
At me with it problems aren't present.
Simply it would be desirable "the new" version
Transaction is over 0.70 btc.
Let me describe the whole story. Some services (like http://bitcoin-contact.org/) require btc address validation.
To do that you need send some specific amound of BTC from own address to the same address - twice (second time, after at least one confirmation of first tx). So, that can be case of spam transactions defend. But i am applied fee 0.0005 in both cases (first gone without troubles and now has 20 confirmations), so it should not be.
Also, i am using addnode with ip`s that receive free or very small fees. Last BTC i am have received to my wallet, have at least 2000 confirmations.
First transaction:
http://blockexplorer.com/tx/8bf1483fa075a0a64593d2b332acaeee3af15d83e13c749dbdd1298e28d5aeca
Let me describe the whole story. Some services (like http://bitcoin-contact.org/) require btc address validation.
To do that you need send some specific amound of BTC from own address to the same address - twice (second time, after at least one confirmation of first tx). So, that can be case of spam transactions defend. But i am applied fee 0.0005 in both cases (first gone without troubles and now has 20 confirmations), so it should not be.
Also, i am using addnode with ip`s that receive free or very small fees. Last BTC i am have received to my wallet, have at least 2000 confirmations.
First transaction:
http://blockexplorer.com/tx/8bf1483fa075a0a64593d2b332acaeee3af15d83e13c749dbdd1298e28d5aeca
And after you tried it once - try again. And post the results. My 0.3.22 refuse to do it, after one free (or 0.0005 btc) tx, again. I am trying this for some number of blocks (14) and that did not happend.
txid?
The limit of 0.01 BTC on small value transactions still exists. That has not changed.
If you are sending values smaller than 0.01 BTC, a fee is required.
And after you tried it once - try again. And post the results. My 0.3.22 refuse to do it, after one free (or 0.0005 btc) tx, again. I am trying this for some number of blocks (14) and that did not happend.
-paytxfee=0.0000
Will work?
Will work?
Yes, that works. That should reset your client back to default behavior: free transactions, unless it's clearly not possible for your transaction to fit into the free area of a block.
-paytxfee=0.0000
Will work?
Will work?
Yes, that works. That should reset your client back to default behavior: free transactions, unless it's clearly not possible for your transaction to fit into the free area of a block.
xf2_org,
-paytxfee=0.0000
Will work?
-paytxfee=0.0000
Will work?
But it still did not allow to use 0.0005 fee.
Can you be more specific? -paytxfee=0.0005 should work.
Well, that version solved a lot of problems with GUI issues ("cut" windows, error messages).
But it still did not allow to use 0.0005 fee. (OP mentioned it). So i am still stick to 0.3.20.
But it still did not allow to use 0.0005 fee. (OP mentioned it). So i am still stick to 0.3.20.
I am ready to wait. Whether it is possible to pay in the version 0.3.22 the commission absolutely? Or it is necessary to use 0.3.20.2?
how come the message isn't pgp signed? for the last release, it was signed by gavin.
https://forum.bitcoin.org/index.php?topic=6642.0
https://forum.bitcoin.org/index.php?topic=6642.0
There ya go:
SHA1 sums, pgp-signed: http://paste.pocoo.org/show/401127/
how come the message isn't pgp signed? for the last release, it was signed by gavin.
https://forum.bitcoin.org/index.php?topic=6642.0
https://forum.bitcoin.org/index.php?topic=6642.0
There ya go:
SHA1 sums, pgp-signed: http://paste.pocoo.org/show/401127/
I'm a little out of the loop with the development, but just downloaded the client and noticed that it still has only .00 instead of .000. I was under the impression that we were gonna add the third zero in this version
It handles smaller values just fine, just type 1.001 in the send dialog, and your balance will change appropriately. No change was made to the default number of decimal places. Jump to: