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

[Coins-R-Us]

Well yes i suppose i can still mint on android,
but i need to be able to send coins to myself
occasionally, and that does Not seem to work.
I wanted a real wallet to mint coins, and
that part seems to be working... just not yet.

Perhaps it is some odd bug, like coin label starts
with a number, causes an issue.  I can try turning
off coin control also.  But then i lose that control.

I have no problem sending with any of my other
coin wallets, so i'm not sure what the problem is.
That's why i might need a PC wallet soon.

P.S. I am also thinking Rounding Error could be the
cause of this - can't send 1000 'satoshi' if you
really have 999.9 (novatoshi?)  I will test this.
I have seen other wallets miscalculate the fee,
causing a small amount of change to be created.
This might be a similar type of error.
Maybe it is impossible to have 0.9 satoshi, but
I have seen rounding error cause problems many
times.  It is better to truncate sometimes.

[1714020074]

1714020074

[1714020074]

1714020074

[Balthazar]

I like the Novacoin-qt android app, but i'm having trouble sending coins to myself.
Unlocked the wallet, changed the fee to 0.001, and it still won't send.
The send button turns blue, but no message or anything.
Anyone got any ideas about this?  Thanks for your help.

By the way, I have coin control enabled, selected all inputs,
and put a valid address in the send field.  Should work (?)

Hm. Maybe there are some spent coins in your wallet? This could happen in case if you are using old backup copy of wallet.dat, for example.

[Balthazar]

They are green/mature! Two of them are now 38 days old and the other one "only" 34.

Could you provide a block explorer link to some of your inputs? You can use PM to keep your privacy untouched.

Did something happened during this last month? A fork?

Nope, nothing changed.

UPDATE: The solution is to unlock the wallet by hand, using the command line "walletpassphrase <passphrase> timeout mintonly", instead of using the menu. Strange, but real.

Hm, this seems really strange because there is no real difference between these two approaches. Going to check it soon.

[Balthazar]

Coins-R-Us
Hm... If you need android wallet for mining purposes then it's not neccessary to send coins there. You can import your private keys into android installation of novacoin client. Or, if you have root access, you can replace wallet.dat on your android device.

I am also thinking Rounding Error could be the
cause of this - can't send 1000 'satoshi' if you
really have 999.9 (novatoshi?)  I will test this.
I have seen other wallets miscalculate the fee,
causing a small amount of change to be created.
This might be a similar type of error.
Maybe it is impossible to have 0.9 satoshi, but
I have seen rounding error cause problems many
times.  It is better to truncate sometimes.

You're correct, it's impossible to have less than 0.000001 NVC because 1 NVC = 10⁶ Satoshi.

On the other hand, practical limits are much higher than 0.000001 NVC, because value for minimal input volume is currently fixed at 0.0001 NVC. Though you still can generate or receive such transactions, your wallet will ignore those inputs while processing memory pool and transaction index. This has been done in order to prevent DoS attacks on shared wallets. You can adjust the limit by setting -mininput parameter to preferred value.

[Coins-R-Us]

Thank you so much for this information!
I just got the wallet to send coins!  

Instead of trying to send the total amount,
i just sent 'almost' the total, letting the
wallet decide the inputs, paid the 0.001 fee,
and made sure not to leave 'dust' under 0.0001.

This will work fine for me.  I say the issue is resolved.

[Balthazar]

Dear Novacoin users, I have to notify you that terrible thing happened. Unfortunately, the Proof-of-Stake difficulty has been dropped as the result of successful attack. In case if attacker would decide to continue generation, please make sure that you're not processing transaction until 8-9 confirmations were achieved. That will protect you against double spending attempts.

Hard fork is necessary to resolve this issue, updated client will be published in the next few days. Please stay tuned.

[Balthazar]

Workaround is ready and available at github.

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

Binary builds will be published tomorrow.

Please note that redownloading of blockchain is required after applying the latest snapshot.

[Balthazar]

Binary builds for Windows and Linux (for x86 and x86_64 CPUs) were published.

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

[Balthazar]

MacOS X builds were published in the same directory.

[Balthazar]

Debian/ARMv7(Hardware float) builds have been published.

http://sourceforge.net/projects/novacoin/files/novacoin-0.5.5/debian-armv7hf/

[flound1129]

Something seems odd here??

$ novacoind getblocktemplate|grep -i time
    "mintime" : 1469407456,
        "time",
    "curtime" : 1469416605,

[t309]

nvc trade places

btc-e.com
btc-trade.com.ua
yobit.net
cryptsy.com (problems with the withdraw, be careful)

nvc charts

btccharts.com
btce.penek.org

very interesting correlation NVC/LTC https://btce.penek.org/history/nvc-ltc.php

[t309]

bleutrade.com/exchange/NVC/BTC

[iCEBREAKER]

Dear Novacoin users, I have to notify you that terrible thing happened. Unfortunately, the Proof-of-Stake difficulty has been dropped as the result of successful attack. In case if attacker would decide to continue generation, please make sure that you're not processing transaction until 8-9 confirmations were achieved. That will protect you against double spending attempts.

Hard fork is necessary to resolve this issue, updated client will be published in the next few days. Please stay tuned.

Attack details please.

Would like to know if DASH Masternodes are also vulnerable.   

[papa_lazzarou]

Dear Novacoin users, I have to notify you that terrible thing happened. Unfortunately, the Proof-of-Stake difficulty has been dropped as the result of successful attack. In case if attacker would decide to continue generation, please make sure that you're not processing transaction until 8-9 confirmations were achieved. That will protect you against double spending attempts.

Hard fork is necessary to resolve this issue, updated client will be published in the next few days. Please stay tuned.

Attack details please.

Would like to know if DASH Masternodes are also vulnerable.  

From a cursory analysis of the patchup it looks like a simple hashdrift attack...

[t309]

Another exchange https://c-cex.com/?p=nvc-btc very low volume (((

[c-cex]

Another exchange https://c-cex.com/?p=nvc-btc very low volume (((

Just listed, volume is coming up.
Have some doubts about logo. Do we use right logo?

[penek]

Just listed, volume is coming up.
Have some doubts about logo. Do we use right logo?

That is not right logo. Better use this or this

[t309]

Just listed, volume is coming up.
Have some doubts about logo. Do we use right logo?

That is not right logo. Better use this or this

+1

What will you do with pos interest?

[tolikkk]

bleutrade.com/exchange/NVC/BTC

...very low or not trade completely but himself-a presence on this exchange is very positive, is that the ease of operation