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

[Balthazar]

Hi guys

Just a little competition. The one who finds the first PoS block after the 1391641017 UNIX timestamp (1 year since genesis block) will receive a small bonus.

If you wish to support a winner, donations are accepted here:

4PenekGWGr55XUaeDDeTQEsbTg7wG2JyTz

Currently we have 16.39 NVC in this wallet.

[1713508579]

1713508579

[1713508579]

1713508579

[1713508579]

1713508579

[Bitinvestor]

The one who finds the first PoS block after the 1391641017 UNIX timestamp (1 year since genesis block) will receive a small bonus.

What date is that in human readable form?

[Balthazar]

The one who finds the first PoS block after the 1391641017 UNIX timestamp (1 year since genesis block) will receive a small bonus.

What date is that in human readable form?

Wed, 05 Feb 2014 22:56:57 GMT 

[kha0S]

http://www.unixtimestamp.com/index.php

The one who finds the first PoS block after the 1391641017 UNIX timestamp (1 year since genesis block) will receive a small bonus.

What date is that in human readable form?

[Balthazar]

NovaCoin 0.4.4.7 bugfix2 critical update.

This update resolves "transaction creation failed" issue.

Changes list:

• Core: bug with fee calculation fixed in CreateTransaction();
• RPC: getsubsidy RPC call added;
• RPC: getmininginfo and getinfo now are providing current proof-of-stake difficulty value.

Source tree:

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

MacOS X dmg: link
Linux 64 bit static build: link

Windows nosetup: i686, AMD64
Windows installer: i686, AMD64

[ewibit]

It seems that you have mined some blocks for the wrong chain. That's not a problem for stake blocks, because those inputs were recovered during synchronization process. With this recovered inputs you are able to find some valid blocks again.

all mined from 2014-01-04 to 2014-01-30 are Status: 0/unconfirmed - generated but not accepted

[Bitinvestor]

all mined from 2014-01-04 to 2014-01-30 are Status: 0/unconfirmed - generated but not accepted

That´s why you have to keep your NVC client updated. PoS mining is cheap and easy, but it does require a minimum of supervision and maintenance. If you had kept an eye on your miner then you would have noticed earlier that something is wrong.

[Balthazar]

Serious issue with stake modifier calculation was found right now at block #72810. If you are using 64 bit windows version of 0.4.4.7 client, please shut it down and use 0.4.4.7 32 bit or 0.4.4.6 / 0.4.4.5 instead, until this issue will be investigated.

We are sorry for inconvenience.

P.S. If you've decided to switch from 64 bit to 32 bit build then you need to download a fresh copy blockchain. That's necessary because old one could contain the wrong checksums created by buggy build.

[glendall]

Aw crap think that might have might have been a problem that I had with the 4.4.7 64 bits Windows. From both of my wallets on two separate boxes they had POS stakes generated for only 40% / 55% of the wallets balance, whereas before it has been POS block proportional to 100% of the balance. Was that the issue? I'm still a bit new to how POS blocks and how they are calculated.

Actually no I forgot, one of my wallet boxes is running Debian linux 0.4.4.7 beta, not Win 64,  so I guess what happened wasn't a bug.

Anyways, will keep updating to newest release.

[Balthazar]

It's a floating issue. Sometimes it happens, sometimes doesn't. So it's possible to have windows 64 bit build working correctly.

If you have no synchronization issues (i.e. your wallet is on a top of the best chain), then it's generally OK. But you can get modifier checksums for some blocks and compare it with values you've got from another client... Some values, for example:

# 72837  "modifierchecksum" : "8378242b",
# 72834  "modifierchecksum" : "0816d578",
# 72830  "modifierchecksum" : "cafd1f98",
# 72810  "modifierchecksum" : "aab46337",

If your values are different then there is a problem. Use getblockbynumber RPC command, it's quite helpful for such cases.

I think that we'll find a reason in the next few days.

Aw crap think that might have might have been a problem that I had with the 4.4.7 64 bits Windows. From both of my wallets on two separate boxes they had POS stakes generated for only 40% / 55% of the wallets balance, whereas before it has been POS block proportional to 100% of the balance. Was that the issue?

Nope, that's normal behavior.

[glendall]

Thanks for the quick help Balthazar. You are the most helpful coin-maker dev IMHO, cheers.

I'll play around with the getblockbynumber command. I think I'm fine.

[Balthazar]

Some users reported syncronization issue with linux builds too. So, it was decided to remove 0.4.4.7 version from repository and send alert notification over the network. Downgrade to 0.4.4.6 or 0.4.4.5 is required to keep your wallet stable, the main repository is downgraded too. If you are using 0.4.4.5/0.4.4.6 releases then it's safe to ignore this notification.


There were more than 10 testing builds with 482 downloads and nobody seen this issue before. We are sorry for inconvenience.

[glendall]

Ok switched to the 0.4.4.6. Deleted my Novacoin %appdata% directory (after backing up my wallet of course).  Started novacoin-qt to d/l block chain and still getting the message about there being a sync issue and to downgrade to 0.4.4.6.

I'm using the recommended version (I think)  v0.4.4.6-nvc-dirty-beta .

[Balthazar]

0.4.4.6 and 0.4.4.7 are using the same protocol version 60011, that's why 0.4.4.6 users see this message too. But it's safe to ignore for 0.4.4.6 users.

[glendall]

Okay thanks.

[ewibit]

0.4.4.6 and 0.4.4.7 are using the same protocol version 60011, that's why 0.4.4.6 users see this message too. But it's safe to ignore for 0.4.4.6 users.

have downgraded to v0.4.4.6-nvc-beta and have this message too - hope it is ok, because Balance is now 0
 

[Balthazar]

0.4.4.6 and 0.4.4.7 are using the same protocol version 60011, that's why 0.4.4.6 users see this message too. But it's safe to ignore for 0.4.4.6 users.

have downgraded to v0.4.4.6-nvc-beta and have this message too - hope it is ok, because Balance is now 0
 

repairwallet RPC command will be helpful.

----

Rollback release will be published soon, it's based on 0.4.4.6 but includes RPC api and wallet.dat related code changes to make it compatible with 0.4.4.7.

[ryanb]

i downgraded to 4.4.6 but it does not seem to be syncing

i do not see the green bar progress being downloaded.

what shall i do?

[Balthazar]

i downgraded to 4.4.6 but it does not seem to be syncing

i do not see the green bar progress being downloaded.

what shall i do?

I think it syncronizing, but you can't see the progress bar if there are any alerts active. You can check a syncronization progress in the debug window (help -> debug window).

Next build (based on 0.4.4.6) will be published a few hours later.

[Balthazar]

Next build (based on 0.4.4.6) will be published a few hours later.

Done. Differences from 0.4.4.6:

• getsubsidy, getinfo, getmininginfo RPC calls now are identical to presented in 0.4.4.7;
• automatic wallet transactions update during initial block download;
• syncronization alert message removed;
• block databases versioning support.

Linux 64 bit static build: link
Mac OS X build: link

Windows nosetup: i686, AMD64

Windows installer: i686, AMD64