[ANN] official NovaCoin thread - the original PoS+scrypt coin.

[Balthazar]

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.

[Balthazar]

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://github.com/CryptoManiac/novacoin/commit/b73a4568bb521678d2904cb514cac550846f8fab

It will be merged into the next release.

[Tranz]

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://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.

[Balthazar]

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.

[Balthazar]

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.

[Balthazar]

Electrum server and client are coming soon

[BTCat]

Hi folks. Just wondering what happened to NVC, I remember it did US$25 per coin and now it's just US$1 almost. Good time to buy? Any developments going on?

Thanks.

[Balthazar]

Novacoin repository has been updated.

https://github.com/novacoin-project/novacoin

Merged changes:

• Additional script checkings against transaction malleability;
• Multi-threaded script verification;
• Watch-only addresses support.

Commit list could be seen here:

https://github.com/novacoin-project/novacoin/pull/21

Builds are coming soon.

Q: Watch-only addresses? What is it?
A: Inputs with these addresses could be watched but it's impossible to spend them.

Q: How is it supposed to work?
A: You can import address into your wallet, without importing any additional address info (i.e. private or public key).

Q: How to use it?
A: Open your RPC console and type: importaddress <novacoinaddress>. Here <novacoinaddress> should be replaced with novacoin address.

Q: Is there any limitation for addresses which could be used for this function?
A: You can use any address here, it's not necessary to import own addresses only.

Unspendable inputs amount is shown at overview page



and in getinfo output

[Balthazar]

Good time to buy? Any developments going on?

Maybe. I've bought 2000 coins yesterday.

Any developments going on?

Electrum lightweight client is coming soon.

[Balthazar]

Recent repository changes were reverted due to bakance calculation issues. it will be merged after applying suitable fixes.

P.S. fixed and publisbed as 0.4.4.6 update 6.

[Zer0Sum]

I've the "URGENT: 0.4.4.7 clients are affected..." message.

Do I just wait for the new binaries... or take other steps?

[Balthazar]

I've the "URGENT: 0.4.4.7 clients are affected..." message.

Do I just wait for the new binaries... or take other steps?

Hi. You need to use 0.4.4.6 update 4 or 0.4.4.6 update 6 binaries

https://sourceforge.net/projects/novacoin/files/

Or compile your own binaries using a source code from the master branch.

https://github.com/novacoin-project/novacoin

This will resolve all syncronization issues.

[fredeq]

Can I request addition of block_reward to explorer API? Thats the last variable I just cant figure out.

Doesnt have to be current, from last block will be just fine, whatever is easier for you

[Balthazar]

Can I request addition of block_reward to explorer API? Thats the last variable I just cant figure out.

Doesnt have to be current, from last block will be just fine, whatever is easier for you

Actually, there is no problem to calculate reward without using any additional tools.

https://github.com/novacoin-project/novacoin/wiki/Proof-of-work

However, I've sent your request to explorer's maintainer.

[fredeq]

Can I request addition of block_reward to explorer API? Thats the last variable I just cant figure out.

Doesnt have to be current, from last block will be just fine, whatever is easier for you

Actually, there is no problem to calculate reward without using any additional tools.

https://github.com/novacoin-project/novacoin/wiki/Proof-of-work

However, I've sent your request to explorer's maintainer.

Hah I was browsing internet for ages looking for that formula, thank you very much!

[bestsponsor]

Stay away from this coin - its developer (Balthazar) support terrorists in Ukraine.
Also he's a crook - stole coins from pool LTCMine.

[Mike270]

Hi,

I'm having some strange coin control display with the version from novacoin-nosetup-0.4.4.6-update7-win32-amd64.zip :

Somehow, the # confirmations OR Date don't match here.
Which value to trust?

Thanks
Mike

[Mike270]

Hi,

I tried reverting from update 7 to update 6, re-downloaded blockchain, but problem persists. Any ideas?
I have this on three different wallets on three different PCs.

Thanks!
Mike

[Bitinvestor]

Somehow, the # confirmations OR Date don't match here.
Which value to trust?

You could look up those transactions in a block explorer. I don't seem to have this problem with my wallet.

[glendall]

Stay away from this coin - its developer (Balthazar) support terrorists in Ukraine.
Also he's a crook - stole coins from pool LTCMine.

If you are gonna make wild claims like that you'll be wanting to put up some proof.