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

[Frederik_FL]

I am still new in cryptomoedas market and unfortunately only a short time I follow the NAV, but I'm happy to be knowing that the team is serious and all these ongoing projects I have no doubt that this currency is very promising.

I'm investing and plan to continue with NAV, because the future will give many joys to those who believe in this project.

Welcome! 

Enjoy your investment and if you would have any questions, shoot!

[PH300R]

I'm from Brazil and I'm happy with this project

[kold678]

i think by christmas this will be 30-50k sat so enjoy the ride up ...look at what exp did in about the same time frame and i think the development here is much better good luck to all and nice work devs dont slow down you really have something here

[Sjacmur]

Invest Long Term

(...)

Patience is the key

Why you wrote this ? We waiting for annon 2-3 years and now you wrote its "long term invest" ?? Another 2-3 years you mean ?
Before swap to Nav 2.0 I was thinking annon was developed and working now I heard not working and its another "long term investment" and "need patient" ??
So already NAV again no have working any annon ? Even centralized ?
And some people suprised about NAV drop prices when someones fake buy walls disapears.

[bspus]

Invest Long Term

(...)

Patience is the key

Why you wrote this ? We waiting for annon 2-3 years and now you wrote its "long term invest" ?? Another 2-3 years you mean ?
Before swap to Nav 2.0 I was thinking annon was developed and working now I heard not working and its another "long term investment" and "need patient" ??
So already NAV again no have working any annon ? Even centralized ?
And some people suprised about NAV drop prices when someones fake buy walls disapears.

LOL its as if you don't know hashforce or you never heard of NAV.
Hashforce always makes such comments at least one on each page
And anon has been working since early 2015 which again you should know.

The long term investment in NAV has already paid of. Even now with the dumping its over double what it had reached in early 2015 when anon was working. And lets not even talk about its usual price until summer which was less than 1000.

[redjedievolution]

mmmmm the price since february moved from 500-1000 satoshi.

Now we are at 7000 satoshi. Why are you feeling bad?

 

Invest Long Term

(...)

Patience is the key

Why you wrote this ? We waiting for annon 2-3 years and now you wrote its "long term invest" ?? Another 2-3 years you mean ?
Before swap to Nav 2.0 I was thinking annon was developed and working now I heard not working and its another "long term investment" and "need patient" ??
So already NAV again no have working any annon ? Even centralized ?
And some people suprised about NAV drop prices when someones fake buy walls disapears.

[Diego24]

Why you wrote this ? We waiting for annon 2-3 years and now you wrote its "long term invest" ?? Another 2-3 years you mean ?

It is like it is. If you don't want to wait, don't buy NAV. You almost sound like it is am obligation for anon coins to go up in price or you will get angry.

Even centralized ?

At the moment yes. So what ? That's an amazing opportunity to buy NAV. You can still buy it before decentralization. After decentralization the price will go up and you can forget to get cheap NAV ever again.

And some people suprised about NAV drop prices when someones fake buy walls disapears.

Actually nobody is surprised NAV price dropped when fake buy wall disapeared.

[pakage]

Navtech Anon Beta

We’ve had a busy week at Nav Coin HQ with the first round of Beta Testing of the Navtech Anon system completed successfully. We’ve made some minor improvements to the code and have re-deployed the updates to the servers. The second round of tests have begun and the test group has been widened to all 22 members of the slack channel #navtech-anon-beta. If you are interested in helping with the test, please join us on slack and get a sneak preview of the system in action!

Now we have more users, we can start to stress test the system and I will also start to add more servers into the cluster this week. I am very pleased with the testing so far. Any adjustments we’ve made have been very minor so it is looks like everything is progressing as expected.

So what was tested ? What was succesful and what wasn't ? Not being critical. Just from interest as NAV investor. 

Sure, so the issues we've encountered so far are pretty minor but i will explain.

1) Coins were returned from the incoming server to the sender. This is one of the graceful fail overs the system has in place, so it actually worked as intended. The reason why the coins was rejected was when the system went to process the transactions and send to the outgoing server, it found the outgoing server was not up to date with the latest block as visible on the network. It was only 1 block behind, but this caused the incoming server to think the outgoing server was not ready to process transactions. I have loosened this check. So it will consider an incoming or outgoing server ready to transact if it is within 5 blocks of the current block. In practice, I've only ever seen them 1 - 2 blocks out but 5 seems like a good buffer. It still has to be up to date with the latest block to process the transactions, but this should reduce the incidence of unnecessarily returned coins when there is a small block count difference.

2) The coins started being always returned to sender, the server needed to be restarted to fix this. This one was a little tricky, the reason why it was failing was because when the incoming server tried to process the transactions, it's query to the outgoing server was being rejected because the outgoing server couldn't find the incoming server's IP address in its whitelist. This error happened over time and the reason for it is an interesting nuance of programming. Basically, as the outgoing server requests to be refilled by the incoming server, it will cross servers off the list if it doesn't receive the correct response and ask to be refilled from another server. This crossing off of servers is done by looping through the whitelist and sending out requests, when a server has failed to respond it is removed from the list. The nuance of JavaScript is that even though i had created a new variable which i was looping through and deleting items from, it is actually just what is known as a pointer, so it was actually crossing items out of the main whitelist entry as well. So the next time it went to use the whitelist, there were no items on it and all requests were being rejected. I have solved this by making sure we clone the whitelist object out of the settings rather than just point to it, this means each time we fetch the whitelist, it is a new instance of the original list from the settings and when we delete items they don't get deleted from the main entry.

Everything else has worked great. All coins have either been returned to sender or made it through the system perfectly which is the intention. So I am glad that the two minor technical issues we had, resulted in no loss of coins by the sender.

There are 24 people in the test group now and I am awaiting more feedback from them over the next couple of days.

Cheers,
Craig.

[Golftech]

Navtech Anon Beta

We’ve had a busy week at Nav Coin HQ with the first round of Beta Testing of the Navtech Anon system completed successfully. We’ve made some minor improvements to the code and have re-deployed the updates to the servers. The second round of tests have begun and the test group has been widened to all 22 members of the slack channel #navtech-anon-beta. If you are interested in helping with the test, please join us on slack and get a sneak preview of the system in action!

Now we have more users, we can start to stress test the system and I will also start to add more servers into the cluster this week. I am very pleased with the testing so far. Any adjustments we’ve made have been very minor so it is looks like everything is progressing as expected.

So what was tested ? What was succesful and what wasn't ? Not being critical. Just from interest as NAV investor. 

Sure, so the issues we've encountered so far are pretty minor but i will explain.

1) Coins were returned from the incoming server to the sender. This is one of the graceful fail overs the system has in place, so it actually worked as intended. The reason why the coins was rejected was when the system went to process the transactions and send to the outgoing server, it found the outgoing server was not up to date with the latest block as visible on the network. It was only 1 block behind, but this caused the incoming server to think the outgoing server was not ready to process transactions. I have loosened this check. So it will consider an incoming or outgoing server ready to transact if it is within 5 blocks of the current block. In practice, I've only ever seen them 1 - 2 blocks out but 5 seems like a good buffer. It still has to be up to date with the latest block to process the transactions, but this should reduce the incidence of unnecessarily returned coins when there is a small block count difference.

2) The coins started being always returned to sender, the server needed to be restarted to fix this. This one was a little tricky, the reason why it was failing was because when the incoming server tried to process the transactions, it's query to the outgoing server was being rejected because the outgoing server couldn't find the incoming server's IP address in its whitelist. This error happened over time and the reason for it is an interesting nuance of programming. Basically, as the outgoing server requests to be refilled by the incoming server, it will cross servers off the list if it doesn't receive the correct response and ask to be refilled from another server. This crossing off of servers is done by looping through the whitelist and sending out requests, when a server has failed to respond it is removed from the list. The nuance of JavaScript is that even though i had created a new variable which i was looping through and deleting items from, it is actually just what is known as a pointer, so it was actually crossing items out of the main whitelist entry as well. So the next time it went to use the whitelist, there were no items on it and all requests were being rejected. I have solved this by making sure we clone the whitelist object out of the settings rather than just point to it, this means each time we fetch the whitelist, it is a new instance of the original list from the settings and when we delete items they don't get deleted from the main entry.

Everything else has worked great. All coins have either been returned to sender or made it through the system perfectly which is the intention. So I am glad that the two minor technical issues we had, resulted in no loss of coins by the sender.

There are 24 people in the test group now and I am awaiting more feedback from them over the next couple of days.

Cheers,
Craig.

thanks for this update dev hope everything will be settle and the value of the coin will be recognized after everything succeed i believe nav is just getting started and we will see even more progress coming from this project, good luck

[hashforce101]

Invest Long Term

(...)

Patience is the key

Why you wrote this ? We waiting for annon 2-3 years and now you wrote its "long term invest" ?? Another 2-3 years you mean ?
Before swap to Nav 2.0 I was thinking annon was developed and working now I heard not working and its another "long term investment" and "need patient" ??
So already NAV again no have working any annon ? Even centralized ?
And some people suprised about NAV drop prices when someones fake buy walls disapears.

LOL its as if you don't know hashforce or you never heard of NAV.
Hashforce always makes such comments at least one on each page
And anon has been working since early 2015 which again you should know.

The long term investment in NAV has already paid of. Even now with the dumping its over double what it had reached in early 2015 when anon was working. And lets not even talk about its usual price until summer which was less than 1000.

Yes want I meant is if you take a long term investment strategy in NAV. Its pays BIG $$$$ for that you need some Patience and to be rock solid in Holding your NAV

Yes Anon is Developed and as you can see doing extremely well under testing for the Big release. Also look at Thunderclap which everyone should join

If you sell your NAV every time the price drops you end up  losing money. Then Buying back higher.

I am looking at the history of All the competitors of NAV in the Anonymous Anon Market and NAV has huge growth potential.

Its not so long term now compared to 2014. We are at 2016 and are now at the Business end of the Project.

Meaning this thing is ready to go to the Moon.

[Caladonian]

i like that statement creating our own history im so glad im still holding the coin that i have and did not panic price went down to 6k let see how this nav will bring us looking forward for more success. good luck

[koYnsta]

buy walls are back at trex (at least for now)
70 btc at 5000sat and 100 btc at 4000 sat

[Waldozaur12]

buy walls are back at trex (at least for now)
70 btc at 5000sat and 100 btc at 4000 sat

NAV pump on Bittrex is much easier than Poloniex  

[DragonBall Fan]

I like this NAV picture, it looks so international. (It would look good as title screen on the NAV facebook site)

https://d1p42fqrbwqdsw.cloudfront.net/campaigns/background_images/000/047/929/web/NAV-Nations-small.jpg

[thisisanalias]

I've been staking 24/7 on my laptop. Is staking just random stake amounts and random income amounts because I am staking all my coin and it just sometimes stakes 2000 for eg then 5000 and all income amounts are differnet. Avg 1 NAV an hour. Just curious how it works? Tempted to ditch more Monero for NAV haha.

Cheers

[X1235]

Version 3.6.0 does not sync: "0 active connections".

[thisisanalias]

Version 3.6.0 does not sync: "0 active connections".

What platform, in Ubuntu 16.04 I had to add the nodes to a config file and it fixed it. https://chainz.cryptoid.info/nav/#!network cut and past all the IP's to a config file in the folder.

addnode=1.34.180.245
addnode=104.145.225.90
addnode=104.156.240.143
addnode=104.200.151.45
addnode=104.238.95.31
addnode=104.243.249.20
addnode=105.155.78.175
addnode=105.157.20.78
addnode=109.202.107.10
addnode=113.80.61.108
addnode=113.80.61.9
addnode=113.91.122.107
addnode=121.99.177.103
addnode=124.198.202.122
addnode=138.68.28.50
addnode=138.68.28.51
addnode=138.91.249.96
addnode=139.59.210.59
addnode=144.132.239.24
addnode=158.181.27.252
addnode=159.203.59.69
addnode=159.203.59.72
addnode=162.216.46.36
addnode=162.219.178.66
addnode=163.172.60.111
addnode=166.48.75.134
addnode=171.232.14.211
addnode=175.144.211.155
addnode=176.154.77.92
addnode=176.198.172.210
addnode=176.9.58.13
addnode=178.116.98.215
addnode=178.222.149.88
addnode=180.216.87.3
addnode=184.148.5.222
addnode=184.167.180.122
addnode=184.178.50.168
addnode=185.61.148.209
addnode=188.166.53.199
addnode=195.46.23.74
addnode=2.121.6.128
addnode=2.87.182.25
addnode=208.167.254.52
addnode=208.95.215.81
addnode=212.180.171.44
addnode=212.225.199.128
addnode=213.152.162.170
addnode=213.152.162.94
addnode=217.248.53.33
addnode=217.248.55.175
addnode=219.88.236.50
addnode=24.220.128.119
addnode=37.25.73.90
addnode=45.127.50.240
addnode=45.56.158.145
addnode=47.151.176.146
addnode=49.147.175.245
addnode=5.1.91.86
addnode=5.189.144.97
addnode=5.230.142.15
addnode=5.230.146.212
addnode=62.43.224.206
addnode=67.170.64.102
addnode=68.197.13.94
addnode=71.53.152.225
addnode=72.196.215.114
addnode=73.254.153.254
addnode=79.8.1.204
addnode=80.167.238.90
addnode=80.218.184.244
addnode=81.156.249.155
addnode=81.242.204.39
addnode=82.192.40.170
addnode=83.185.92.231
addnode=85.189.15.237
addnode=87.13.211.1
addnode=89.66.232.171
addnode=89.67.108.90
addnode=90.71.206.232
addnode=91.121.41.59
addnode=91.153.109.149
addnode=95.183.50.54
addnode=95.183.51.15
addnode=95.183.52.165
addnode=95.183.53.184
addnode=95.40.139.235

[X1235]

Version 3.6.0 does not sync: "0 active connections".

What platform, in Ubuntu 16.04 I had to add the nodes to a config file and it fixed it. https://chainz.cryptoid.info/nav/#!network cut and past all the IP's to a config file in the folder.

Thank you. OS X, still no luck.

[btcforks]

where can I find the online wallet for NAVCOIN

[Lafu]

where can I find the online wallet for NAVCOIN

You want to download it or need a wallet on an Platform ?