New fee policy has become active.
https://explorer.novaco.in/tx/d642dcb559ae8ac491e0c13bb5810ff95aee6b6472a123b1b0d54be2ceefeb00
There are a lot of old nodes yet, so if you have any issues with transactions confirmation then you can set 0.01/1kb fee manually in the client options.
Topic: [ANN] official NovaCoin thread - the original PoS+scrypt coin. --POOL LIST-- - page 24. (Read 282664 times)
July 19, 2014, 08:52:49 PM
July 19, 2014, 08:42:09 AM
Important notice.
64-bit installer file name always contain "amd64" substring.
There are users, who tried to use 64-bit windows installer in 32-bit operation system. Before installation please make sure that you're not using 64-bit installer on 32-bit windows, that will cause silent update failure.
I suppose that next time we'll pack both 32-bit and 64-bit executables into one installer, but it's better to make sure that you're using right version.
64-bit installer file name always contain "amd64" substring.
There are users, who tried to use 64-bit windows installer in 32-bit operation system. Before installation please make sure that you're not using 64-bit installer on 32-bit windows, that will cause silent update failure.
I suppose that next time we'll pack both 32-bit and 64-bit executables into one installer, but it's better to make sure that you're using right version.
July 18, 2014, 10:29:41 PM
I have a question on novacoin. I tried some multisig functions, but it seems something is not working. I tried to reproduce what Gavin did for BTC:
https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
I suppose that this commit will be helpful for your case:https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
https://github.com/CryptoManiac/novacoin/commit/b73a4568bb521678d2904cb514cac550846f8fab
It will be merged into the next release.
Thanks for this. I struggled with this a bit myself. I think it will be important to mitigate counter-party risk.
I added this code a while back ago(missed listunspent), but still had a few issues. I also had to change sendrawtransactions (https://github.com/Tranz5/HoboNickels/commit/4f7f87375863f15ee22fa5624a0d7718cc7fee6b). The wallet will allow it to go through, but not accepted by the block chain.
I have only attempted it once, so might be something I did, but I will be curious how this works out for your users.
As always, thanks for your dedication.
July 18, 2014, 07:28:38 PM
I have a question on novacoin. I tried some multisig functions, but it seems something is not working. I tried to reproduce what Gavin did for BTC:
https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
I suppose that this commit will be helpful for your case:https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
https://github.com/CryptoManiac/novacoin/commit/b73a4568bb521678d2904cb514cac550846f8fab
It will be merged into the next release.
July 12, 2014, 08:44:15 PM
NVC is based on the bitcoin 0.7.2 source code.
We'll investigate signrawtransaction behavior a bit later, I don't think that there would be any problem to fix this issue. In case if this problem is caused by an old implementation of RPC method we'll syncronize it with upstream version.
We'll investigate signrawtransaction behavior a bit later, I don't think that there would be any problem to fix this issue. In case if this problem is caused by an old implementation of RPC method we'll syncronize it with upstream version.
July 12, 2014, 06:47:29 PM
I have a question on novacoin. I tried some multisig functions, but it seems something is not working. I tried to reproduce what Gavin did for BTC:
https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
https://gist.github.com/gavinandresen/3966071
I created 3 pairs of private/public keys from addresses from one qt client, then used 3 public keys to create a 3-2 address. Send some coins to the address, then use createrawtransaction to create a spent tx.
Now if I sign this tx with one private key at a time, it is not working, the same tx is returned. If, however, I just signrawtransaction without explicitly the private key, it works (as all private keys are in this client), and then I can sendrawtransaction, and it did registered in the blockchain.
If I use 1 address from this qt client, and 2 other addresses from another qt, then I am unable to complete the signing of the tx. It is not working the signrawtransaction (just return the same unsigned one), as without explicitely giving privatekey means only 1 that is in this client.
The same process works in BTC. And I checked the code version, the protocol version nova uses is 600xx, while bitcoin uses 700xx. And the signrawtransaction code is different. Is this problem related to the old version? Does nova have the plan to upgrade the codebase to the latest bitcoin codebase?
July 12, 2014, 05:09:04 AM
July 11, 2014, 05:16:25 AM
NovaCoin client update 0.4.4.6 u4 has been published.
This update is mandatory for everybody and should be applied before 20 Aug 2014.
Database format is compatible with recent 0.4.4.6 builds, so if you're using 0.4.4.6 client then you don't need to re-syncronize the blockchain. If you're using 0.4.4.7 then block chain downloading process will be started automatically.
Windows:
Linux:
Mac OS X:
Sources tree:
https://github.com/novacoin-project/novacoin
ARM builds will be published later.
This update is mandatory for everybody and should be applied before 20 Aug 2014.
Database format is compatible with recent 0.4.4.6 builds, so if you're using 0.4.4.6 client then you don't need to re-syncronize the blockchain. If you're using 0.4.4.7 then block chain downloading process will be started automatically.
Code:
"protocolversion" : 60015,
Windows:
Linux:
Mac OS X:
Sources tree:
https://github.com/novacoin-project/novacoin
ARM builds will be published later.
Is this related at all to my issue? Sends seem to be working normally again on 0.4.4.6.
Yep, unfortunately there was an issue with 0.4.4.7 clients. CoinsDB engine isn't stable enough for now, so I suppose that 0.4.4.7 branch will be frozen for indefinite time. But its experience will be used in the 0.4.4.6 branch. 0.4.4.6u3 build incorporates the most of recent protocol and GUI changes from 0.4.4.7 branch. 
July 10, 2014, 06:06:14 AM
Master branch was recreated as a copy of 'legacy', 'current' was renamed to 'unstable'.
Update of 0.4.4.6 branch is scheduled tomorrow, it will include recent interface and protocol changes from 0.4.4.7.
Update of 0.4.4.6 branch is scheduled tomorrow, it will include recent interface and protocol changes from 0.4.4.7.
Is this related at all to my issue? Sends seem to be working normally again on 0.4.4.6.
July 10, 2014, 04:59:25 AM
Master branch was recreated as a copy of 'legacy', 'current' was renamed to 'unstable'.
Update of 0.4.4.6 branch is scheduled tomorrow, it will include recent interface and protocol changes from 0.4.4.7.
Update of 0.4.4.6 branch is scheduled tomorrow, it will include recent interface and protocol changes from 0.4.4.7.
July 10, 2014, 01:12:48 AM
Attention please!
There is a critical issue with block chain syncronization in 0.4.4.7 versions of novacoin client. If you are using 0.4.4.7 then downgrade to 0.4.4.6 update 3 or update2 is strictly recommended.
Binaries for linux armv6 and win32/win64 are available at sourceforge.
Unaffected source could be cloned from legacy repository:
git clone -b legacy https://github.com/novacoin-project/novacoin
Issue is currently under investigation.
Valid chain is currently consists of 107621 blocks, block #107620 is 000000000070ac2d51c8b288dcb18adca11bd4571a8e8c7e27fad3994980c7fd.
There is a critical issue with block chain syncronization in 0.4.4.7 versions of novacoin client. If you are using 0.4.4.7 then downgrade to 0.4.4.6 update 3 or update2 is strictly recommended.
Binaries for linux armv6 and win32/win64 are available at sourceforge.
Unaffected source could be cloned from legacy repository:
git clone -b legacy https://github.com/novacoin-project/novacoin
Issue is currently under investigation.
Valid chain is currently consists of 107621 blocks, block #107620 is 000000000070ac2d51c8b288dcb18adca11bd4571a8e8c7e27fad3994980c7fd.
July 09, 2014, 06:25:08 PM
I'm still getting the conflicted transactions with v0.4.4.7-nvc-bugfix5-beta afer redownloading the blockchain.
Also, now the entire balance disappears and doesn't come back unless I do a -salvagewallet or a -rescan.
Also, now the entire balance disappears and doesn't come back unless I do a -salvagewallet or a -rescan.
July 09, 2014, 09:52:19 AM
What is the current annual stake rate for NVC? I see in main.h that it starts at 100%, but it is my understanding that with the rise in difficulty that the reduction of stake rate has kicked into gear.
Keep up the good work here. We all know that NVC created a whole bunch of fun coins.
Keep up the good work here. We all know that NVC created a whole bunch of fun coins.
wiki (filling only begun) for PoS: https://wiki.novaco.in/proof-of-stake/ (from https://github.com/novacoin-project/novacoin/wiki)
Calc here: https://novaco.in/posprob.php (or from Home page)
July 08, 2014, 11:16:02 AM
What is the current annual stake rate for NVC? I see in main.h that it starts at 100%, but it is my understanding that with the rise in difficulty that the reduction of stake rate has kicked into gear.
Keep up the good work here. We all know that NVC created a whole bunch of fun coins.
Keep up the good work here. We all know that NVC created a whole bunch of fun coins.
July 08, 2014, 11:15:47 AM
> ...
> this is the insulting robot
> robots do appreciate humans who keep their promises
> robotic life is not without hardships as well
> this is the insulting robot
> robots do appreciate humans who keep their promises
> robotic life is not without hardships as well
July 08, 2014, 05:39:31 AM
insulting_robot
Unfortunately, a painful amount of money were spent to cover my ltc pool payments since its crash. Eventually it will be resolved.
Unfortunately, a painful amount of money were spent to cover my ltc pool payments since its crash. Eventually it will be resolved.
July 07, 2014, 05:15:09 PM
> ...
> this is the insulting robot
> this is a reminder for Balthazar regarding the NovaCoin logo contest that is still unresolved since more than a year
> will this contest be resolved at all?
> this is the insulting robot
> this is a reminder for Balthazar regarding the NovaCoin logo contest that is still unresolved since more than a year
> will this contest be resolved at all?
July 07, 2014, 09:39:30 AM
Hi flound1129 
cc5699d0dd84468665d6 transaction exists in the main chain, it seems that your transaction is trying to use input which was spent by this transaction.
Try to apply 0.4.4.7b5 update, maybe it will resolve this situation.
So after the transaction was rebroadcasted wouldn't it show up as confirmed?
It will show this transaction as confirmed once block with transaction will be accepted. Your client is synchronized with the rest of the network properly, or not?Why is it still showing conflicted?
"Conflicted" status means that transaction exists in the wallet, but doesn't exist neither in the memory pool nor blockchain. Memory pool is currently exists only as a memory structure, it doesn't saved to HDD yet. So, any unconfirmed transaction could be shown as "conflicted" after restart unless your client gets a copy of this transaction into memory pool. This problem will be resolved in the next release, through saving a copy of memory pool to HDD. "account" : "",
"address" : "4PNf73X2L9iUm3cE6tvFq919XrHeiEmPtQ",
"category" : "conflicted",
"amount" : -0.18378200,
"fee" : -0.01000000,
"confirmations" : -1,
"txid" : "6d67a895afe4d077ccf62351c2263295c2fe312ed80e6fdefe259beff64c97e4",
"metahash" : "8ae7e84de3445781bc15194f09813f3c0aae57fb7ee034bf119a1681ae848aa7",
"walletconflicts" : [
"cc5699d0dd84468665d693751646bf497b921b68a78163691947c5bb09d51c36"
],
"time" : 1404720093,
"timereceived" : 1404720093
https://explorer.novaco.in/tx/cc5699d0dd84468665d693751646bf497b921b68a78163691947c5bb09d51c36"address" : "4PNf73X2L9iUm3cE6tvFq919XrHeiEmPtQ",
"category" : "conflicted",
"amount" : -0.18378200,
"fee" : -0.01000000,
"confirmations" : -1,
"txid" : "6d67a895afe4d077ccf62351c2263295c2fe312ed80e6fdefe259beff64c97e4",
"metahash" : "8ae7e84de3445781bc15194f09813f3c0aae57fb7ee034bf119a1681ae848aa7",
"walletconflicts" : [
"cc5699d0dd84468665d693751646bf497b921b68a78163691947c5bb09d51c36"
],
"time" : 1404720093,
"timereceived" : 1404720093
cc5699d0dd84468665d6 transaction exists in the main chain, it seems that your transaction is trying to use input which was spent by this transaction.
WTF is going on? am I on a buggy version? What version should I be on?
Actually, there are nothing going on yet, so this situation seems pretty surprising for me too. Current version is 0.4.4.7 bugfix5, this release contains some protocol changes, but these changes will be activated only since 20 Jul. Stake entropy calculation update was added by 0.4.4.6u3, but this update has become active more than a month ago. So, now there is nothing new in the network yet. Try to apply 0.4.4.7b5 update, maybe it will resolve this situation.
July 07, 2014, 04:09:59 AM
I'm getting these errors now with a brand new wallet that has no transactions other than 2 transfers to it.
"account" : "",
"address" : "4PNf73X2L9iUm3cE6tvFq919XrHeiEmPtQ",
"category" : "conflicted",
"amount" : -0.18378200,
"fee" : -0.01000000,
"confirmations" : -1,
"txid" : "6d67a895afe4d077ccf62351c2263295c2fe312ed80e6fdefe259beff64c97e4",
"metahash" : "8ae7e84de3445781bc15194f09813f3c0aae57fb7ee034bf119a1681ae848aa7",
"walletconflicts" : [
"cc5699d0dd84468665d693751646bf497b921b68a78163691947c5bb09d51c36"
],
"time" : 1404720093,
"timereceived" : 1404720093
WTF is going on? am I on a buggy version? What version should I be on?
"account" : "",
"address" : "4PNf73X2L9iUm3cE6tvFq919XrHeiEmPtQ",
"category" : "conflicted",
"amount" : -0.18378200,
"fee" : -0.01000000,
"confirmations" : -1,
"txid" : "6d67a895afe4d077ccf62351c2263295c2fe312ed80e6fdefe259beff64c97e4",
"metahash" : "8ae7e84de3445781bc15194f09813f3c0aae57fb7ee034bf119a1681ae848aa7",
"walletconflicts" : [
"cc5699d0dd84468665d693751646bf497b921b68a78163691947c5bb09d51c36"
],
"time" : 1404720093,
"timereceived" : 1404720093
WTF is going on? am I on a buggy version? What version should I be on?
July 05, 2014, 02:57:06 PM
So after the transaction was rebroadcasted wouldn't it show up as confirmed? Why is it still showing conflicted?
Jump to: