Version 0.7.0 release candidate 3 ready for testing

[jgarzik]

well, the documentation seems to suggest that you must enable ipv6 by including USE_IPV6=1, but the build file has USE_IPV6:=1 as default.   i tried changing that to USE_IPV6=- and USE_IPV6=0, still results in same error

Try commenting out the entire line

Code:

#USE_IPV6:=1

[imsaguy]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

[LightRider]

Consistently getting a "TX rejected (code -22)" message when trying using sendrawtransaction. I believe I'm following all the steps properly. (createrawtransaction, signrawtransaction, sendrawtransaction)

Using the rpc console in Win7x64.

Same result using bitcoind.

[Diapolo]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

[Gavin Andresen]

Consistently getting a "TX rejected (code -22)" message when trying using sendrawtransaction. I believe I'm following all the steps properly. (createrawtransaction, signrawtransaction, sendrawtransaction)

debug.log might tell you why it is being rejected. Some reasons it might be rejected:

+ You're re-using an input that has already been spent.
+ Sum(outputs) is greater than Sum(inputs)
+ signrawtransaction was unable to sign all of the inputs (it did not report "complete" : true )

By the way: be EXTREMELY careful with the raw transactions API. You can easily forget to include a change output and create transactions with huge fees; test your code thoroughly on testnet before putting it into production.

[imsaguy]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

[Diapolo]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

Do you use portable Zip or installation? Only the installation will update the file associations for bitcoin URIs, which could also cause errors.

Dia

[imsaguy]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

Do you use portable Zip or installation? Only the installation will update the file associations for bitcoin URIs, which could also cause errors.

Dia

Install.  I'm installing RC2 as we speak and will give it a go.

[Gavin Andresen]

Consensus is the RPC-doesn't-work-if-you-disable-IpV6 bug is serious enough to hold up the 0.7.0 final release.

So the plan will be: get a fix for that bug and release/test a 0.7.0rc3.

[piotr_n]

Bitcoin version 0.7.0 release candidate 2 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/test/

Unless another critical bug is found, this should be the final 0.7.0 release.

This is a great progress that you guys did in the 0.7 version.
You don't see a progress at the first sight, but the extra RPC commands and the built-in console - for me, just paradise. And it will be so easy to explain to my mom how to use it, so she doesn't have to keep her wallet on the same pc where my father watches porn, pressing yes at every button...
The idea witn some bitcoind.exe, that she had to run from a command prompt... she did not like it.
But a built in RPC console - just genius!
And I must say switching to Qt really seems to have been a good idea, after all.

Thanks.

[Diapolo]

Consensus is the RPC-doesn't-work-if-you-disable-IpV6 bug is serious enough to hold up the 0.7.0 final release.

So the plan will be: get a fix for that bug and release/test a 0.7.0rc3.

It seems to me that the RPC server currently entirely ignores the fact that <nets> can be limited via e.g. -onlynet="IPv4" which should never use IPv6 for anything then, right?

Dia

[Diapolo]

Bitcoin version 0.7.0 release candidate 2 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/test/

Unless another critical bug is found, this should be the final 0.7.0 release.

This is a great progress that you guys did in the 0.7 version.
You don't see a progress at the first sight, but the extra RPC commands and the built-in console - for me, just paradise. And it will be so easy to explain to my mom how to use it, so she doesn't have to keep her wallet on the same pc where my father watches porn, pressing yes at every button...
The idea witn some bitcoind.exe, that she had to run from a command prompt... she did not like it.
But a built in RPC console - just genius!
And I must say switching to Qt really seems to have been a good idea, after all.

Thanks.

Thanks for the Qt commendation, wumpus and I'm very happy to hear such things as we put some efforts into making the Qt GUI better / cleaner / more polished . I really love his RPC console, too and I'm glad I could help him improving that beast a little ^^.

Dia

[LightRider]

Consistently getting a "TX rejected (code -22)" message when trying using sendrawtransaction. I believe I'm following all the steps properly. (createrawtransaction, signrawtransaction, sendrawtransaction)

debug.log might tell you why it is being rejected. Some reasons it might be rejected:

+ You're re-using an input that has already been spent.
+ Sum(outputs) is greater than Sum(inputs)
+ signrawtransaction was unable to sign all of the inputs (it did not report "complete" : true )

By the way: be EXTREMELY careful with the raw transactions API. You can easily forget to include a change output and create transactions with huge fees; test your code thoroughly on testnet before putting it into production.

ERROR: CTxMemPool::accept() : not enough fees

I'm assuming this is the error that I'm getting. Is this expected behavior? How does one include fees in a raw transaction?

[foo]

ERROR: CTxMemPool::accept() : not enough fees

I'm assuming this is the error that I'm getting. Is this expected behavior? How does one include fees in a raw transaction?

The fee is Sum(inputs) - Sum(outputs). Drop some coins on the floor and a miner will pick 'em up.

[thezerg]

Sorry if this is a little OT, but if I just pull from master am I getting your RC?  If so, its working great for me :-)

[imsaguy]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

Do you use portable Zip or installation? Only the installation will update the file associations for bitcoin URIs, which could also cause errors.

Dia

Install.  I'm installing RC2 as we speak and will give it a go.

Still getting that message with RC2.  Win 7 x64 Chrome Browser default.

[Diapolo]

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

Do you use portable Zip or installation? Only the installation will update the file associations for bitcoin URIs, which could also cause errors.

Dia

Install.  I'm installing RC2 as we speak and will give it a go.

Still getting that message with RC2.  Win 7 x64 Chrome Browser default.

Can you try to set IE as default browser for a quick test please?

Dia

[finway]

Translation not updated.

[Pieter Wuille]

Regarding the IPv6 RPC issue, can you guys test whether pull request #1822 fixes the problem?

I can create a build of that, if necessary.

[zvs]

Regarding the IPv6 RPC issue, can you guys test whether pull request #1822 fixes the problem?

I can create a build of that, if necessary.

i'll test it, it'll be a bit though since this kimsufi is godawful slow