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

[flound1129]

Hello.
Looks like you are sending an already spent input. You need to re-download the blockchain.
This can happen if you use the same wallet in several instances of novacoin daemon.

Your coins were already spent here:

https://explorer.novaco.in/tx/0865db4c00a4ca4cbafefd37ee43d2acaa78e923dab02d24c781be0e274b8113


Cheers.

This wallet has never been used in any other locations.

Why should redownloading the blockchain work vs. a rescan?

[Balthazar]

Your client is unable to see this transaction in the local copy of blockchain, but it seems that transaction has been sent and confirmed properly:

https://explorer.novaco.in/tx/2849cfe9e487fb45f88fc36a61c1d42d2be1bb8d58a99df59f39dbead78e47b7

You can find it in block #106134.

Possible reasons are corrupt database or obsolete version.

P.S. Future builds will be able to save tx mempool data to hdd, this will be helpful to prevent the most part of such issues.

[flound1129]

Your client is unable to see this transaction in the local copy of blockchain, but it seems that transaction has been sent and confirmed properly:

https://explorer.novaco.in/tx/2849cfe9e487fb45f88fc36a61c1d42d2be1bb8d58a99df59f39dbead78e47b7

You can find it in block #106134.

Possible reasons are corrupt database or obsolete version.

P.S. Future builds will be able to save tx mempool data to hdd, this will be helpful to prevent the most part of such issues.

So it's returning an error, but the coins are actually sending?  That's even worse.

[penek]

Added chart to PoS probability and reward

Also available API (/api/posprob) for this chart, may be anyone create widget for win7/8

[Balthazar]

So it's returning an error, but the coins are actually sending?  That's even worse.

Creation of transaction & sending transaction are separate operations. The daemon couldn't send transaction for some reason, but then it was re-broadcasted using a local copy got from the wallet.dat. It's a regular behavior for any satoshi-based client, especially when a local copy of blockchain isn't syncronized properly.

If you wish to prevent re-broadcasting then you can use RAW transactions API to perform your payments. RAW transactions are saved only if those transactions are accepted and valid.

You need these functions:

• listunspent - returns a list of available inputs;
• createrawtransaction '[{"txid":"deadbeef...", vout:0}, ...]' '{"address1":10.01, "address2": 1.22, ...}'- create raw transaction. Returns transaction data on success. Please note that difference between outputs and input sums will be considered as transaction fee;
• signrawtransaction <txdata> - append signatures to raw transaction, returns object which contains a signed transaction code and signing status;
• sendrawtransaction <txdata> - sends transaction over the network, returns true on success or false otherwise.

[flound1129]

So after the transaction was rebroadcasted wouldn't it show up as confirmed?  Why is it still showing conflicted?

[flound1129]

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?

[Balthazar]

Hi flound1129

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

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.

[insulting_robot]

> ...

> 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?

[Balthazar]

insulting_robot

Unfortunately, a painful amount of money were spent to cover my ltc pool payments since its crash. Eventually it will be resolved.

[insulting_robot]

> ...

> this is the insulting robot

> robots do appreciate humans who keep their promises

> robotic life is not without hardships as well

[presstab]

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.

[penek]

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.

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)

[flound1129]

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.

[Balthazar]

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.

[Balthazar]

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.

[flound1129]

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.

Is this related at all to my issue?  Sends seem to be working normally again on 0.4.4.6.

[Balthazar]

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.

Code:

"protocolversion" : 60015,

Windows:

• Win32 setup
• Win64 setup
• Win32 nosetup
• Win64 nosetup

Linux:

• Linux AMD64
• Linux i686

Mac OS X:

• Mac OS X AMD64

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.

[Balthazar]

ARM HF builds:

• Linux armv6l
• Linux armv7l

[dfox101]

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?