★[ANN] [NAV] NAV COIN - Community Fund Live!!!

[bspus]

Edit: After 4 hours I am 14 weeks behind and connection number rise to 6. So some better but synchronize still very slow.

Just to be clear, 4 weeks of Nav Blocks are the equivalent of nearly 2 years worth of Bitcoin Blocks due to our 30 second block time. Syncing 4 weeks in 4 hours is actually pretty decent. It's never going to be instant and the speed will vary depending on your connection and computing power. Syncing all 8 years of Bitcoin blocks takes me a couple of days usually so block for block the speed you are reporting with even only 6 connections is technically faster than Bitcoin.

Also re: the number of connections, you only connect to peers with the same wallet version so this will increase as more people adopt the new wallet. Please be patient.

Happy syncing everybody!

You can't compare bitcoin blocks and NAV blocks due to vast difference in size. Many btc blocks are near 1 MB which is the max whereas most NAV block are very small
The total btc ledger is dozens of GBs whereas NAV 2.0 is just a few hundred MBs right now.

[pakage]

Edit: After 4 hours I am 14 weeks behind and connection number rise to 6. So some better but synchronize still very slow.

Just to be clear, 4 weeks of Nav Blocks are the equivalent of nearly 2 years worth of Bitcoin Blocks due to our 30 second block time. Syncing 4 weeks in 4 hours is actually pretty decent. It's never going to be instant and the speed will vary depending on your connection and computing power. Syncing all 8 years of Bitcoin blocks takes me a couple of days usually so block for block the speed you are reporting with even only 6 connections is technically faster than Bitcoin.

Also re: the number of connections, you only connect to peers with the same wallet version so this will increase as more people adopt the new wallet. Please be patient.

Happy syncing everybody!

You can't compare bitcoin blocks and NAV blocks due to vast difference in size. Many btc blocks are near 1 MB which is the max whereas most NAV block are very small
The total btc ledger is dozens of GBs whereas NAV 2.0 is just a few hundred MBs right now.

This is true, the main point I'm trying to illustrate is just that there are a lot more blocks to process than people realise. Regardless of size it will still take some time to process and for your wallet to validate

[hashforce101]

Edit: After 4 hours I am 14 weeks behind and connection number rise to 6. So some better but synchronize still very slow.

Just to be clear, 4 weeks of Nav Blocks are the equivalent of nearly 2 years worth of Bitcoin Blocks due to our 30 second block time. Syncing 4 weeks in 4 hours is actually pretty decent. It's never going to be instant and the speed will vary depending on your connection and computing power. Syncing all 8 years of Bitcoin blocks takes me a couple of days usually so block for block the speed you are reporting with even only 6 connections is technically faster than Bitcoin.

Also re: the number of connections, you only connect to peers with the same wallet version so this will increase as more people adopt the new wallet. Please be patient.

Happy syncing everybody!

Checked this morning on the New Laptop running Windows 10

The wallet is fully Synced with 19 connections!

I started from scratch - So tested FULL sync from start to finish with no issues.

Very Happy that this issue has been fixed by the team before October 20 Thunderclap campaign.

More importantly the False Positive has been fixed before the major releases

So no more surprises

[alexf1852]

Waiting for the MAC OS X 3.7 wallet.

[redjedievolution]

i synced 3 wallets in 3 different computers with 3 different connections, they synced fast, some hours to complete. now they're 9 connections 10 and 8 in those 3 wallets.

Thanks!

[thisisanalias]

I saved a copy of the hidden .navcoin2 folder in Ubuntu. Deleted everything, made new 3.7 wallet and just copied the .navcoin2 files back into the new made .navoin2 folder replacing them except for navcoin.conf where I used your nodes and settings.

I just made up a random rpc name and password (that's ok right?)

Now I have one connection to the network and all my coins are back so it must have worked, am I correct doing what I did?

Only problem is my network weight is about 1000 NAV off my balance in my wallet and I'm not staking just yet, which now I think is probably an old stake not matured yet. I'll wait and see.

[for everet]

I still can not connect, help with

[for everet]

I still can not connect, help with

01- rpcuser=<USERNAME>
rpcpassword=<PASSWORD>
rpcallowip=127.0.0.1
rpcport=44444
port=44440
listen=1
daemon=1
server=1
txindex=1
staking=1
maxorphanblocks=10000
addnode=185.61.148.209
addnode=95.183.51.15
addnode=95.183.50.54
addnode=5.230.142.15
addnode=5.230.146.212
addnode=95.183.53.184




02- rpcuser=<USERNAME>
rpcpassword=<PASSWORD>
rpcallowip=127.0.0.1
rpcport=44444
port=44440
listen=1
daemon=1
server=1
txindex=1
staking=1
maxorphanblocks=10000
addnode=104.200.153.87
addnode=109.156.105.111
addnode=124.169.97.86
addnode=176.154.77.92
addnode=185.61.148.209
addnode=2.87.182.25
addnode=212.180.171.44
addnode=212.225.199.128
addnode=219.88.236.74
addnode=24.220.128.119
addnode=31.16.109.143
addnode=45.56.158.54
addnode=47.208.182.225
addnode=49.145.116.11
addnode=5.230.142.15
addnode=5.230.146.212
addnode=62.43.224.206
addnode=75.157.162.73
addnode=78.88.28.147
addnode=81.156.249.155
addnode=84.246.229.4
addnode=84.78.226.16
addnode=86.138.223.45
addnode=88.217.180.209
addnode=89.164.172.6
addnode=89.67.108.90
addnode=95.183.50.54
addnode=95.183.51.15
addnode=95.183.52.165
addnode=95.183.53.12
addnode=95.183.53.184

BUT STILL CAN NOT CONNECT

[pakage]

I still can not connect, help with

Are you sure that there's not something on your local network blocking the port? Everyone else seems to have this new wallet working fine?

[CryptoJohn]

hey team,

question about new wallet. wallet only synced to 9 weeks and then nothing for the past 4 hours. everytime i close wallet i get the below error.



I tried deleting everthing except wallet.dat and starting again, results repeated.

[for everet]

I still can not connect, help with

Are you sure that there's not something on your local network blocking the port? Everyone else seems to have this new wallet working fine?

Version 3.6 is still working normally

[hashforce101]

I still can not connect, help with

Are you sure that there's not something on your local network blocking the port? Everyone else seems to have this new wallet working fine?

Version 3.6 is still working normally

Ill post my conf tonight if that helps

[for everet]

I still can not connect, help with

Are you sure that there's not something on your local network blocking the port? Everyone else seems to have this new wallet working fine?

Version 3.6 is still working normally

Ill post my conf tonight if that helps

ok, thank

[shahim]

hey team,

question about new wallet. wallet only synced to 9 weeks and then nothing for the past 4 hours. everytime i close wallet i get the below error.



I tried deleting everthing except wallet.dat and starting again, results repeated.

hm can not open Database seems to show some file corruption. When you google that error it all points to a damaged wallet.dat file. can you try using a backup?

regards
shahim

[redjedievolution]

With this navcoin.conf my wallets syncs like a ferrari  

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=44444
port=44440
listen=1
daemon=1
server=1
txindex=1
staking=1
maxorphanblocks=10000
addnode=188.165.3.6
addnode=95.183.53.12
addnode=72.196.215.114
addnode=1.34.180.245
addnode=212.225.199.128
addnode=68.197.13.94
addnode=176.9.58.13
addnode=89.67.108.90
addnode=109.131.2.8
addnode=71.53.152.225
addnode=2.121.6.128
addnode=185.61.148.209

[redjedievolution]

Shahim i have a question:

I have one wallet with currently 11 active connections. I use rpccommand "getpeerinfo" and take note of each ip. and put this ips into another wallet navcoinf.conf with addnode=x.x.x.x

Then i start the second wallet and starts syncing but it only has one connection. Why?

[shahim]

Shahim i have a question:

I have one wallet with currently 11 active connections. I use rpccommand "getpeerinfo" and take note of each ip. and put this ips into another wallet navcoinf.conf with addnode=x.x.x.x

Then i start the second wallet and starts syncing but it only has one connection. Why?

Perhaps the nodes do not accept more conenctions right now? normally it needs some time until the wallet get's more connections. but it will find them itself when you just let it run.

Which IP is the "one connection" you have? Perhaps 185.61.148.209 ?

regards
shahim

[redjedievolution]

This 188.165.3.6

Shahim i have a question:

I have one wallet with currently 11 active connections. I use rpccommand "getpeerinfo" and take note of each ip. and put this ips into another wallet navcoinf.conf with addnode=x.x.x.x

Then i start the second wallet and starts syncing but it only has one connection. Why?

Perhaps the nodes do not accept more conenctions right now? normally it needs some time until the wallet get's more connections. but it will find them itself when you just let it run.

Which IP is the "one connection" you have? Perhaps 185.61.148.209 ?

regards
shahim

[redjedievolution]

Shahim, and how can i increase the max connections, i mean i have very good connectivity in some nodes, maybe i can increase the "maxconnections" in my configuration to allow better network/sync progress to other navcoiners... I have several nodes with 1gb-10gb
thanks

[shahim]

Shahim, and how can i increase the max connections, i mean i have very good connectivity in some nodes, maybe i can increase the "maxconnections" in my configuration to allow better network/sync progress to other navcoiners... I have several nodes with 1gb-10gb
thanks

Just do not set any "maxconnections=" value inside the navcoin.conf. I have several nodes running and each have usually around 40 connections or more.

Right now it is less, because we need to wait until all people have updated to the new wallet version 3.7 ! There is no other way sadly.