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?
Topic: [ANN] official NovaCoin thread - the original PoS+scrypt coin. --POOL LIST-- - page 32. (Read 282708 times)
January 26, 2014, 03:43:33 PM
January 26, 2014, 01:42:18 PM
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.
https://github.com/novacoin-project/novacoin
My own repository (CryptoManiac/novacoin) will be available, but it's recommended to use official repository instead.
January 26, 2014, 12:41:37 PM
Hm... I have no idea why you've added this setting. It's P2P connections limit. 
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.
Quote
rpcuser=bitcoinrpc
rpcpassword=IUSESOMETHINGELSE
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.
January 26, 2014, 12:01:21 PM
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
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
rpcpassword=IUSESOMETHINGELSE
daemon=1
server=1
[b]# maxconnections=16[/b] <-- hangs p2pool, don't use
January 26, 2014, 10:41:53 AM
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.
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.
January 26, 2014, 10:00:59 AM
Is the p2pool software incompatible with the current version of novacoin or something?
Running the p2pool gives me this:
(and it stalls here)
I'm running p2pool 11.4.3 and novacoind 0.4.4.6, both compiled from github / running on Ubuntu 13.04
Running the p2pool gives me this:
Code:
Cme@mycomputer:~/p2pool-11.4.3$ python run_p2pool.py
fatal: Not a git repository (or any of the parent directories): .git
2014-01-26 09:52:46.939552 p2pool (version 11.4.3)
2014-01-26 09:52:46.939911
2014-01-26 09:52:46.940105 Testing bitcoind RPC connection to 'http://127.0.0.1:8344/' with username 'bitcoinrpc'...
2014-01-26 09:52:46.965543 ...success!
2014-01-26 09:52:46.965719 Current block hash: ed546b552e694ef3b192325acb663258611bc00c7b7c48fafbe11c6fc3e01381
2014-01-26 09:52:46.965787 Current block height: 70799
2014-01-26 09:52:46.965832
2014-01-26 09:52:46.965911 Testing bitcoind P2P connection to '127.0.0.1:7777'..
I'm running p2pool 11.4.3 and novacoind 0.4.4.6, both compiled from github / running on Ubuntu 13.04
January 25, 2014, 07:33:46 PM
Download [AMD64 | i686 | src]
Additional notes:
Rebuilt again.Additional notes:
- This builds should be considered as pre-release, i.e. it could be used for a new release if there will be no new critical issues;
- If you see zero balance after updating then execute repairwallet command using RPC console and restart your client.
[AMD64 | i686 | src]
- Winsock related compiler warnings are fixed;
- You don't need repairwallet after upgrading anymore, wallet consistency being restored automatically during initial download process.
I guess that it's a last testing build and v0.4.4.7 will be released at monday.
January 25, 2014, 05:43:50 AM
Deterministic wallets status.
WD wallets support is already implemented in the novacoin-hdkeys testing branch and works pretty well. So it's planned for integration into upcoming 0.4.4.8 release, but with one little change
According to testing results we shouldn't abandon the keypool approach. Instead of this we have to implement a separate and deterministic key pools for required purposes (receive, mining and change addresses).
As a result we've got this:
WD wallets support is already implemented in the novacoin-hdkeys testing branch and works pretty well. So it's planned for integration into upcoming 0.4.4.8 release, but with one little change
According to testing results we shouldn't abandon the keypool approach. Instead of this we have to implement a separate and deterministic key pools for required purposes (receive, mining and change addresses).
As a result we've got this:
January 24, 2014, 04:41:23 PM
Download [AMD64 | i686 | src]
Additional notes:
Rebuilt and uploaded.Additional notes:
- This builds should be considered as pre-release, i.e. it could be used for a new release if there will be no new critical issues;
- If you see zero balance after updating then execute repairwallet command using RPC console and restart your client.
Changes list is pretty small:
- Changes done by repairwallet RPC command now applied on the fly, so it's not required to restart client after integrity checkings;
- Block and transaction timestamps were added to gettxout RPC command output.
Download [AMD64 | i686 | src]
-----
Quote
gettxout 01c4dea3d857183a43c126cf34f232bfd2453d3f8f78195b211d9e7a3544a31d 0
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"confirmations" : 60394,
"amount" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : ""
},
"version" : 1,
"coinbase" : false,
"coinstake" : true,
"time" : 1363070975,
"blocktime" : 1363070975
}
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"confirmations" : 60394,
"amount" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : ""
},
"version" : 1,
"coinbase" : false,
"coinstake" : true,
"time" : 1363070975,
"blocktime" : 1363070975
}
January 22, 2014, 08:33:09 PM
Testing builds were updated.
Changes list:
Download [AMD64 | i686 | src]
Additional notes:
------
Changes list:
- Refactoring of Proof-of-Stake checkings code;
- Remove some redundant messages from debug.log output;
- Make stake related DoS checkings harder;
- Database code is updated, direct CCoins links approach is implemented to decrease count of worthless flush and copy events;
- Initial block download optimization, transaction hashes are cached now to make blocks validation faster;
- Multiple CChainDB instantiations were replaced with a single CBlockTreeDB instance;
- CCoinsDB and CBlockTreeDB are updated to use LevelDB storage;
- gettxout and gettxoutsetinfo RPC calls added;
- getblock and getblockbynumber RPC calls are now providing generator public key for proof-of-stake blocks.
Download [AMD64 | i686 | src]
Additional notes:
- This builds should be considered as pre-release, i.e. it could be used for a new release if there will be no new critical issues;
- If you see zero balance after updating then execute repairwallet command using RPC console and restart your client.
------
Quote
getblock 2f942cad0019a69cc83e9cfbdb65dcad7f8ed81eca2b027b2fa490f71f75e7af
{
"hash" : "2f942cad0019a69cc83e9cfbdb65dcad7f8ed81eca2b027b2fa490f71f75e7af",
"confirmations" : 60393,
"size" : 1146,
"height" : 10022,
"version" : 2,
"merkleroot" : "6950c20fca1f4b3091cc274ba4c0cc37e86927431814e9a927cca81ab50e5441",
"mint" : 0.25000000,
"time" : 1363070975,
"nonce" : 0,
"bits" : "1e0fffff",
"difficulty" : 0.00024414,
"blocktrust" : "100001",
"chaintrust" : "102727",
"previousblockhash" : "0000000000e5885d4087ab52b37d81baf28b4b58231402cfd9fe6d4946edacf8",
"nextblockhash" : "00000000072940ff4f46eabace834d681fd20488034517acdc13c8ec7b2771d3",
"flags" : "proof-of-stake stake-modifier",
"proofhash" : "000018d0aa7d744d1c92e2ed0d3b9b2ea313e4a6e72fc7013b6bbebbd414eaf9",
"entropybit" : 1,
"modifier" : "a736cfbe4e9a6031",
"modifierchecksum" : "fede5a20",
"tx" : [
"7473c894134d83bf4a0a5207310520c12edb9bf69411e27b672d77a847d553a0",
"01c4dea3d857183a43c126cf34f232bfd2453d3f8f78195b211d9e7a3544a31d",
"578f2a5464c6f4beade6ea0627c4dc4f3f486d52affe3b24e3f3db349b1d7582",
"41de352ef0b8f1c3cd2dcf3837c4429a43aaebb8cda12a608f8b3dbd896dc76b",
"fb725604b226f8e59aeb07ec21c775f2bd8e3d2033ed46f4562e71b43427cfbf"
],
"generator" : "02afed4a3e2473670ea7a93d61e9fcc883e308812769ff9135a6819b1bccc6486d",
"signature" : "304402207f5985ec8b0e2f034d0ace6a0105d371a0acdf82ea64fca8f0e4bd58a6dcd5a902201e1 0950ef5816402822a7e0ffd078cf3bfd985e015fc032e23febd899110b294"
}
{
"hash" : "2f942cad0019a69cc83e9cfbdb65dcad7f8ed81eca2b027b2fa490f71f75e7af",
"confirmations" : 60393,
"size" : 1146,
"height" : 10022,
"version" : 2,
"merkleroot" : "6950c20fca1f4b3091cc274ba4c0cc37e86927431814e9a927cca81ab50e5441",
"mint" : 0.25000000,
"time" : 1363070975,
"nonce" : 0,
"bits" : "1e0fffff",
"difficulty" : 0.00024414,
"blocktrust" : "100001",
"chaintrust" : "102727",
"previousblockhash" : "0000000000e5885d4087ab52b37d81baf28b4b58231402cfd9fe6d4946edacf8",
"nextblockhash" : "00000000072940ff4f46eabace834d681fd20488034517acdc13c8ec7b2771d3",
"flags" : "proof-of-stake stake-modifier",
"proofhash" : "000018d0aa7d744d1c92e2ed0d3b9b2ea313e4a6e72fc7013b6bbebbd414eaf9",
"entropybit" : 1,
"modifier" : "a736cfbe4e9a6031",
"modifierchecksum" : "fede5a20",
"tx" : [
"7473c894134d83bf4a0a5207310520c12edb9bf69411e27b672d77a847d553a0",
"01c4dea3d857183a43c126cf34f232bfd2453d3f8f78195b211d9e7a3544a31d",
"578f2a5464c6f4beade6ea0627c4dc4f3f486d52affe3b24e3f3db349b1d7582",
"41de352ef0b8f1c3cd2dcf3837c4429a43aaebb8cda12a608f8b3dbd896dc76b",
"fb725604b226f8e59aeb07ec21c775f2bd8e3d2033ed46f4562e71b43427cfbf"
],
"generator" : "02afed4a3e2473670ea7a93d61e9fcc883e308812769ff9135a6819b1bccc6486d",
"signature" : "304402207f5985ec8b0e2f034d0ace6a0105d371a0acdf82ea64fca8f0e4bd58a6dcd5a902201e1 0950ef5816402822a7e0ffd078cf3bfd985e015fc032e23febd899110b294"
}
Quote
gettxoutsetinfo
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"transactions" : 56978,
"txouts" : 90709,
"bytes_serialized" : 4375823
}
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"transactions" : 56978,
"txouts" : 90709,
"bytes_serialized" : 4375823
}
Quote
gettxout 01c4dea3d857183a43c126cf34f232bfd2453d3f8f78195b211d9e7a3544a31d 0
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"confirmations" : 60394,
"amount" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : ""
},
"version" : 1,
"coinbase" : false,
"coinstake" : true
}
{
"bestblock" : "6cdbb76beb4ccf8a3c1a5dc5f1bcd3728c80cd1b98fa72b6926e2243acdd18f1",
"confirmations" : 60394,
"amount" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : ""
},
"version" : 1,
"coinbase" : false,
"coinstake" : true
}
January 22, 2014, 04:48:25 PM
I am running the "portable" nosetup version though...
It doesn't matter if you haven't specified data directory path manually. It tries to load transactions database from %UserProfile%\AppData\Roaming\NovaCoin folder. 
January 22, 2014, 03:27:37 PM
I am completely new to NVC... downloaded the latest win client v0.4.4.6 and getting the following error on launch:
Any ideas? Thanks!
https://bitcointalksearch.org/topic/m.4310529Any ideas? Thanks!
Quote
Q: Why I'm getting runaway exception while trying to start 0.4.4.6 client?
A: That's normal, it's happened because 0.4.4.6 update makes blockindex code incompatible with previous versions. You need to remove old blockchain files and resyncronize with a rest of the network.
Q: How to remove the old blockchain database files?
A: You need to remove everything except wallet.dat from your client data directory. Data directory is located at
Windows Vista/7/8/2008 Server: C:\Users\\AppData\Roaming\NovaCoin
Windows 2000/XP: C:\Documents and Settings\\Application Data\NovaCoin
Linux/*BSD: ~/.novacoin
A: That's normal, it's happened because 0.4.4.6 update makes blockindex code incompatible with previous versions. You need to remove old blockchain files and resyncronize with a rest of the network.
Q: How to remove the old blockchain database files?
A: You need to remove everything except wallet.dat from your client data directory. Data directory is located at
Windows Vista/7/8/2008 Server: C:\Users\
Windows 2000/XP: C:\Documents and Settings\
Linux/*BSD: ~/.novacoin
I am running the "portable" nosetup version though...
January 22, 2014, 03:10:09 PM
I am completely new to NVC... downloaded the latest win client v0.4.4.6 and getting the following error on launch:
Any ideas? Thanks!
https://bitcointalksearch.org/topic/m.4310529Any ideas? Thanks!
Quote
Q: Why I'm getting runaway exception while trying to start 0.4.4.6 client?
A: That's normal, it's happened because 0.4.4.6 update makes blockindex code incompatible with previous versions. You need to remove old blockchain files and resyncronize with a rest of the network.
Q: How to remove the old blockchain database files?
A: You need to remove everything except wallet.dat from your client data directory. Data directory is located at
Windows Vista/7/8/2008 Server: C:\Users\\AppData\Roaming\NovaCoin
Windows 2000/XP: C:\Documents and Settings\\Application Data\NovaCoin
Linux/*BSD: ~/.novacoin
A: That's normal, it's happened because 0.4.4.6 update makes blockindex code incompatible with previous versions. You need to remove old blockchain files and resyncronize with a rest of the network.
Q: How to remove the old blockchain database files?
A: You need to remove everything except wallet.dat from your client data directory. Data directory is located at
Windows Vista/7/8/2008 Server: C:\Users\
Windows 2000/XP: C:\Documents and Settings\
Linux/*BSD: ~/.novacoin
January 22, 2014, 01:59:06 PM
I am completely new to NVC... downloaded the latest win client v0.4.4.6 and getting the following error on launch:
Any ideas? Thanks!
Any ideas? Thanks!
January 21, 2014, 04:26:39 PM
Update: issue suspected with validation of coinstake signature in block #69484, we can't reproduce it but "-next" builds were removed for now.
Fixed, new builds will be published later. January 19, 2014, 07:26:50 PM
Testing branch has been updated.
https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
[AMD64 | i686 | src]https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
Switch to unspent coins approach
This commit replaces old transactions index with unspent coins database
which contains a basic metadata like heights, amounts, coinstake/coinbase
flags and timestamps.
We still need access to blockchain for proof-of-stake blocks validation.
Currently CheckProofOfStake() uses the coin database to find the block height,
and then scans that block to find the dependency of coinstake kernel.
Batch block connection during initial block download
This reduces the load on the database engine, as subsequent blocks often
update an earlier block's transaction already.
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
Please note that this feature is extremely experimental ATM, some parts of functionality weren't tested very well.
Update: binaries were rebuilt from latest snapshot. No broadcasting attempts of orphaned coinstake txns anymore.
- Don't process PoS block coinbase in the ConnectBlock()/DisconnectBlock(), ~3-4mb smaller database size;
- Known issues with reorganize and PoS miner has been fixed.
Update: issue suspected with validation of coinstake signature in block #69484, we can't reproduce it but "-next" builds were removed for now.
January 19, 2014, 12:59:40 AM
Testing branch has been updated.
https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
[AMD64 | i686 | src]https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
Switch to unspent coins approach
This commit replaces old transactions index with unspent coins database
which contains a basic metadata like heights, amounts, coinstake/coinbase
flags and timestamps.
We still need access to blockchain for proof-of-stake blocks validation.
Currently CheckProofOfStake() uses the coin database to find the block height,
and then scans that block to find the dependency of coinstake kernel.
Batch block connection during initial block download
This reduces the load on the database engine, as subsequent blocks often
update an earlier block's transaction already.
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
Please note that this feature is extremely experimental ATM, some parts of functionality weren't tested very well.
Update: binaries were rebuilt from latest snapshot. No broadcasting attempts of orphaned coinstake txns anymore.
January 18, 2014, 03:49:44 PM
Hahah where does a person get a spare kilogram of piracetam from ? Haha No need to answer that, actually. But that's funny.
No need to answer that, actually. But that's funny. 
January 18, 2014, 03:35:28 PM
Testing branch has been updated.
https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
https://github.com/CryptoManiac/novacoin/tree/novacoin-next
screenshot
Switch to unspent coins approach
This commit replaces old transactions index with unspent coins database
which contains a basic metadata like heights, amounts, coinstake/coinbase
flags and timestamps.
We still need access to blockchain for proof-of-stake blocks validation.
Currently CheckProofOfStake() uses the coin database to find the block height,
and then scans that block to find the dependency of coinstake kernel.
Batch block connection during initial block download
This reduces the load on the database engine, as subsequent blocks often
update an earlier block's transaction already.
As a result we've got a significantly smaller (~30% drop of size) and faster database.
Windows binaries will be published soon.
January 17, 2014, 04:38:15 PM
how fast so crypto 
// I've just thought about selling nootropic medicines for some NVC... I have 1kg of Piracetam and I think that it's really too much
// I've just thought about selling nootropic medicines for some NVC... I have 1kg of Piracetam and I think that it's really too much
Hahah where does a person get a spare kilogram of piracetam from ? Haha
No need to answer that, actually. But that's funny. Jump to: