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

[Balthazar]

frontier204
Nope, there are no incompatible changes. I see that it happens sometimes with p2pool for different cryptocurrencies. Is the 7777 port available for connection?

By the way, new p2pool is coming soon.

[frontier204]

Thanks for the quick reply!

I found the issue - it is that p2pool doesn't like the max connections setting...
I have it connecting to a local novacoin-qt now with the following novacoin.conf

Code:

rpcuser=bitcoinrpc
rpcpassword=IUSESOMETHINGELSE
daemon=1
server=1
[b]# maxconnections=16[/b]   <-- hangs p2pool, don't use

[Balthazar]

Hm... I have no idea why you've added this setting. It's P2P connections limit.

rpcuser=bitcoinrpc
rpcpassword=IUSESOMETHINGELSE

I recommend you to set a random RPC username/password and make sure that your 8344 port isn't available for incoming connections from the internet. We have enough skiddies who scans the novacoin network and trying to find p2pool users with opened RPC port.

[Balthazar]

Official repository is moved here:

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

My own repository (CryptoManiac/novacoin) will be available, but it's recommended to use official repository instead.

[Mike270]

Since upgrading my proxy node on my Raspberry Pi to v0.4.4.6-nvc-12-gbafc8da-beta, I'm observing a behaviour I haven't seen before in debug.log:
getblocks 67859 to 00000000000000000000 limit 500
  getblocks stopping at limit 68358 d537d885299074f8efb1
getblocks 68359 to 00000000000000000000 limit 500
  getblocks stopping at limit 68858 000000000007acf2049f
getblocks 68859 to 00000000000000000000 limit 500
  getblocks stopping at limit 69358 b0d680ecdd0e4d6984cc
getblocks 65859 to 1d8fafa34a7f7d29684f limit 500
  getblocks stopping at limit 66358 e7154a17ebfe38e3797a
getblocks 66359 to 00000000000000000000 limit 500
  getblocks stopping at limit 66858 000000000030a21c6998
getblocks 66859 to 00000000000000000000 limit 500
  getblocks stopping at limit 67358 e247514923cb9454c4af
getblocks 67359 to 00000000000000000000 limit 500
  getblocks stopping at limit 67858 00000000006d77fcb0ab
getblocks 67859 to 00000000000000000000 limit 500
  getblocks stopping at limit 68358 d537d885299074f8efb1
getblocks 68359 to 00000000000000000000 limit 500
  getblocks stopping at limit 68858 000000000007acf2049f
getblocks 68859 to 00000000000000000000 limit 500
  getblocks stopping at limit 69358 b0d680ecdd0e4d6984cc
You can see the getblocks looping, i.e. going up to 68859, then starting again at 65859. Since unfortunately it doesn't log IP I cannot see if it's always the same node requesting this.
When stopping & restarting the node , it stays normal for several days until I start seeing this again(happened about 5 times so far). Otherwise, the node seems to remain functional, i.e. forwarding blocks etc.
Anyone else seen this behaviour?

[bizzargin]

Hey everyone,

Just wanted to share some love regarding Novacoin.  I've been creeping these forums for months and there are very few that deserve a "pat on the back".  Many of you on here have given some great opinions regarding the coin and it's future and have helped me through some doubts.  In hindsight, I'm glad I've supported this coin and it's devs.

Keep up the great work guys.

B

[Balthazar]

Since upgrading my proxy node on my Raspberry Pi to v0.4.4.6-nvc-12-gbafc8da-beta, I'm observing a behaviour I haven't seen before in debug.log:
getblocks 67859 to 00000000000000000000 limit 500
  getblocks stopping at limit 68358 d537d885299074f8efb1
getblocks 68359 to 00000000000000000000 limit 500
  getblocks stopping at limit 68858 000000000007acf2049f
getblocks 68859 to 00000000000000000000 limit 500
  getblocks stopping at limit 69358 b0d680ecdd0e4d6984cc
getblocks 65859 to 1d8fafa34a7f7d29684f limit 500
  getblocks stopping at limit 66358 e7154a17ebfe38e3797a
getblocks 66359 to 00000000000000000000 limit 500
  getblocks stopping at limit 66858 000000000030a21c6998
getblocks 66859 to 00000000000000000000 limit 500
  getblocks stopping at limit 67358 e247514923cb9454c4af
getblocks 67359 to 00000000000000000000 limit 500
  getblocks stopping at limit 67858 00000000006d77fcb0ab
getblocks 67859 to 00000000000000000000 limit 500
  getblocks stopping at limit 68358 d537d885299074f8efb1
getblocks 68359 to 00000000000000000000 limit 500
  getblocks stopping at limit 68858 000000000007acf2049f
getblocks 68859 to 00000000000000000000 limit 500
  getblocks stopping at limit 69358 b0d680ecdd0e4d6984cc
You can see the getblocks looping, i.e. going up to 68859, then starting again at 65859. Since unfortunately it doesn't log IP I cannot see if it's always the same node requesting this.
When stopping & restarting the node , it stays normal for several days until I start seeing this again(happened about 5 times so far). Otherwise, the node seems to remain functional, i.e. forwarding blocks etc.
Anyone else seen this behaviour?

I seen that many times on my cubie and I see this now on my VDS.

I don't think that it's the same node, I think this requests are coming from buggy nodes (< 0.4.4.5). The buggy client is able to see that network is on the longer chain currently, but unable to accept this blocks. That's why it tries to sync again and again with a randomly chosen node, bans it and then tries to sync from another one. This can cause some traffic or CPU overhead on normal node, but overall, it's harmless.

We'll add a special condition for incoming connections initiated from versions prior to 0.4.4.5.

You can use a small patch to resolve this by yourself:

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

bizzargin

[carloprs]

Hi, can you help me to configure cgminer for the pool miner? Hi have a Radeon R7 250.

thanks
 

[Balthazar]

Client update 0.4.4.7 released.

This update incorporates all changes from "novacoin-next" branch.

• Core: New proof-of-stake miner implementation. Performance issues resolved, almost 100x faster with massive inputs amount;
• Qt: Coinbase/coinstake transaction records appearance unification;
• Core: Remove BDB support;
• Core: Automatically remove old transactions index database if that's necessary, no runaway exceptions anymore;
• Core: Transaction index is replaced with unspent coins database, ~20% drop of size;
• Core: Batch block connection during initial block download;
• Core: Don't process PoS block coinbase in the ConnectBlock()/DisconnectBlock(), ~3-4mb smaller database size;
• Core: Refactoring of Proof-of-Stake checkings code;
• Core: Remove some redundant messages from debug.log output;
• Core: Make stake related DoS checkings harder;
• Core: Database code is updated, direct CCoins links approach is implemented to decrease count of worthless flush and copy events;
• Core: Initial block download optimization, transaction hashes are cached now to make blocks validation faster;
• Core: Multiple CChainDB instantiations were replaced with a single CBlockTreeDB instance;
• RPC: gettxout and gettxoutsetinfo RPC calls added;
• RPC: getblock and getblockbynumber RPC calls are now providing generator public key for proof-of-stake blocks.

32/64-bit Windows builds of 0.4.4.7 release were uploaded to sourceforge.

Installation packages:
[AMD64 | i686]

Zipballs:
[AMD64 | i686]

Sources tree:

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

Mac OS X and Linux builds will be available later.

[Balthazar]

P2Pool is updated to support connections with v0.4.4.7 nodes.

sources | Win32 py2exe

Older versions won't be able to establish P2P connection with v0.4.4.7 client due to obsolete protocol version. So, if you are switching NVC client to 0.4.4.7 then you need p2pool update as well.

[ewibit]

Sources tree:

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

Mac OS X and Linux builds will be available later.

I have only less then the half of the NVC in wallet now with NovaCoin-Qt version v0.4.4.1-nvc-2-g90d2e98-dirty-beta

and building the new version in Ubuntu 13.10 not possible:

Code:

/git/novacoin/src/leveldb/libmemenv.a
obj/bitcoinrpc.o: In Funktion `context':
/usr/include/boost/asio/ssl/impl/context.ipp:51: Nicht definierter Verweis auf `SSLv2_method'
/usr/include/boost/asio/ssl/impl/context.ipp:54: Nicht definierter Verweis auf `SSLv2_client_method'
/usr/include/boost/asio/ssl/impl/context.ipp:57: Nicht definierter Verweis auf `SSLv2_server_method'
collect2: error: ld returned 1 exit status
make: *** [novacoind] Fehler 1

[pmconrad]

Updated my linux packages for CentOS, Debian, Fedora, RHEL, openSUSE, Ubuntu-13.x at http://software.opensuse.org/download.html?project=home%3Ap_conrad%3Acoins&package=novacoin

[Balthazar]

I have only less then the half of the NVC in wallet now with NovaCoin-Qt version v0.4.4.1-nvc-2-g90d2e98-dirty-beta

0.4.4.1 is unable to work correctly, you need to replace it with 0.4.4.5 or greater.

and building the new version in Ubuntu 13.10 not possible:

Code:

/git/novacoin/src/leveldb/libmemenv.a
obj/bitcoinrpc.o: In Funktion `context':
/usr/include/boost/asio/ssl/impl/context.ipp:51: Nicht definierter Verweis auf `SSLv2_method'
/usr/include/boost/asio/ssl/impl/context.ipp:54: Nicht definierter Verweis auf `SSLv2_client_method'
/usr/include/boost/asio/ssl/impl/context.ipp:57: Nicht definierter Verweis auf `SSLv2_server_method'
collect2: error: ld returned 1 exit status
make: *** [novacoind] Fehler 1

It seems that you have no openssl headers installed...  

[Balthazar]

Updated my linux packages for CentOS, Debian, Fedora, RHEL, openSUSE, Ubuntu-13.x at http://software.opensuse.org/download.html?project=home%3Ap_conrad%3Acoins&package=novacoin

I seen your packages many times in the googling results, you are doing a really great work.

P.S. PM is sent.

Mac OS X and Linux builds will be available later.

Linux static build is available.

[Balthazar]

Updated 64 bit build for Mac OS X is uploaded.

[ewibit]

Linux static build is available.

thx updated and blockchain was build new,
but there are many mined coins with

Code:

? date Mined address [x.xx]

e.g.

Code:

Transaction ID: 178295966b44dc8d626769224b82db2fd4248413b42945b216e2b2fe3865ee08

edit:
from 2014-01-04 all Mined are Status: 0/unconfirmed
have there not been 520 blocks since this date?

[Balthazar]

Linux static build is available.

thx updated and blockchain was build new,
but there are many mined coins with

Code:

? date Mined address [x.xx]

e.g.

Code:

Transaction ID: 178295966b44dc8d626769224b82db2fd4248413b42945b216e2b2fe3865ee08

edit:
from 2014-01-04 all Mined are Status: 0/unconfirmed
have there not been 520 blocks since this date?

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.

[CryptoCurrencyConvention]

Hello group!

I was hoping you could help me make contact with the creator of NOVAcoin?

We are hosting The Crypto Currency Convention in NYC on April 9th. We would like them to speak and promote NOVAcoin.

Our mission is to bring awareness and acceptance to all Crypto Currency and not just bitcoin.

Education and exposure is the only way we all win.

We are expert marketers and expect 1500-2000 attendees.

If you could please forward a message or somehow make an introduction, it would be greatly appreciated and productive.

Thanks!
CryptoCurrencyConvention2014

[Balthazar]

I've sent you a PM.

[Balthazar]

NovaCoin 0.4.4.7 bugfix1 non-critical update.

Changes:

• RPC: getrawtransaction now able to get transaction info from wallet.dat;
• RPC: resendtx uses the new force broadcasting flag.

Source tree:

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