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

[Remy_5]

I'm proud of poloniex. I hate these manual coin swaps. What was the reason why my addresses and balances couldn't be included in the genesis block of V2. I have my coins stored away for 5 years in a paper wallets. It's extremely annoying that I can get my coins stolen right out of my paper wallet. NAUT did this to me. My 200 NAUT paper wallet is now worthless! grrr

I understand your deep and sincere disappointment.
It must not have been easy to print five years ago a paperwallet for NavajoCoin,
expecially considering the fact that this coin was founded only two years ago.

I have to admit it, I'm really amazed by the ability to foresight of the future which you showed us.
Or instead more banally, do You have used a DeLorean? 

[Remy_5]

for anyone having syncing issues on the old chain, please try putting the following into your navcoin.conf file:

maxconnections=2
connect=95.183.50.58
connect=5.230.142.254

And REMOVE any other addnode lines from your config file.

What this does is only allows your wallet to have a maximum of 2 connections and the 'connect' variables will force the wallet to ONLY connect to the nodes listed above.

Without this, your wallet will try to connect to as many nodes as possible, whether on the new or old network and cause delays on syncing to the old chain.

once your wallet is open, you can verify if it has worked by typing, 'getpeerinfo'.  If you only have the nodes with IP's above, it worked.

I haven't test this on NAV since I had my coins on Bittrex for the swap, but the above method has saved numerous headaches for me on other coins.

Please let us know if this fixes the issue.

Remove the old obsolete addnde is correct, but so drastically restrict the number
of connections, IMHO not seem at all the best solution possible, and it does not help
other peers in the same condition.

Especially I would like to avoid that this idea was perceived as overall definitive solution,
valid in all cases, even in the future, because in the long run would be deleterious.

The proper functioning of a crypto currency is based on the creation of distributed
network of peers, sharing and exchange among themselves the blocks with the
transaction between all nodes.

Limit the nodes that way, it ends up transforming the structure of the peer's network of
cryptocoin in a centralized manner, making it very slow, and at the same time this
overloaded its supernodes, making them into weak points in a centralized structure.

In some extreme case can help, but in normal condition this is not the best possible solution.

[Strugg]

Does anyone have a v1 addnode?

There You go:

maxconnections=2
connect=95.183.50.58
connect=5.230.142.254

Full instructions can be found here:
https://bitcointalk.org/index.php?topic=679791.msg15484291#msg15484291

[mulleivan]

Hi there
I have around 30K navs and want to  transfer them from bittrex to my own wallet

I'm using the wallet on Linux, but i'm having a  few problems..........

fist of all what i have done:


╭─ivan@Rebbeca ~  ‹master*›
╰─➤git clone https://github.com/navcoindev/navcoin2

╭─ivan@Rebbeca ~  ‹master*›
╰─➤sudo apt-get install qt5-default qt5-qmake qtbase5-dev-tools qttools5-dev-tools build-essential libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev  libssl-dev libdb++-dev libminiupnpc-dev

╭─ivan@Rebbeca ~  ‹master*›
╰─➤sudo apt-get install libgmp3-dev

╭─ivan@Rebbeca ~  ‹master*›
╰─➤cd navcoin2

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤qmake

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤make

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤   ./NavCoin2-qt.pro
./NavCoin2-qt.pro: 1: ./NavCoin2-qt.pro: TEMPLATE: not found
./NavCoin2-qt.pro: 2: ./NavCoin2-qt.pro: TARGET: not found
./NavCoin2-qt.pro: 3: ./NavCoin2-qt.pro: VERSION: not found
./NavCoin2-qt.pro: 4: ./NavCoin2-qt.pro: INCLUDEPATH: not found
./NavCoin2-qt.pro: 5: ./NavCoin2-qt.pro: QT: not found
./NavCoin2-qt.pro: 6: ./NavCoin2-qt.pro: DEFINES: not found
./NavCoin2-qt.pro: 7: ./NavCoin2-qt.pro: DEFINES: not found
./NavCoin2-qt.pro: 8: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 9: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 10: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 12: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 14: ./NavCoin2-qt.pro: Syntax error: word unexpected (expecting ")")

First error
Then i try to open the executable


╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤  ./navcoin-qt

that open a nice UI  but  that say  12 weeks  behind.....
i download  http://www.navcoin.org/files/Navajo-Blockchain.zip
and extract it on  ~/.navcoin2  hidden folder
after  restar the app still  saying  12 weeks behind
Then i ask a frined   how use NAVS on windows and  told me to add a list of nods on a config flle
as far as i can se the only config file is the      ~/navcoin2/./NavCoin2-qt.pro
but i cant do that run.....


any clue  what i'm doing wrong

cheers and  thanks in advance

[Ginger Ninja]

well to clarify. who i mean what i said about the complainers : people complaining primarily due to missing the pump..

In case that was aimed at me. I have been with Nav for the full 2 years. Did you note the grin at the end of my post?

I am not moaning at the devs. In fact I thanked them and have donated over those 2 years.

My point (like the vast number of long term Navsters vocal on this forum) is that the V1 issue is confusing and not helping. The devs ARE supporting V1 manually so we should switch V1 off until everyone is on the same fork.

Craig, Shahim, Soopy, Strugg etc. have all been performing 110% in the last few months and for that I am grateful.

And with regard to pumping and dumping only a fool would dump now with all the new fantastic features coming online.

[shahim]

Mate! That Blockchain is only for the old client! Please delete all files there.

Then create a ".navcoin2" directory in your home and create the navcoin.conf .

Add these nodes to fasten the sync and let it sync:

addnode=1.10.221.32
addnode=1.10.221.56
addnode=1.34.180.245
addnode=104.236.223.182
addnode=108.95.144.170
addnode=109.110.66.76
addnode=118.173.178.240
addnode=122.166.167.187
addnode=122.53.112.74
addnode=123.3.30.61
addnode=14.192.209.23
addnode=160.176.171.123
addnode=171.6.250.169
addnode=175.214.144.141
addnode=176.154.77.92
addnode=184.167.180.122
addnode=185.17.207.189
addnode=185.61.148.209
addnode=199.189.131.12
addnode=2.121.162.167
addnode=2.84.167.61
addnode=208.95.215.81
addnode=212.180.171.44
addnode=213.108.119.84
addnode=219.88.236.170
addnode=219.88.238.26
addnode=41.142.44.167
addnode=45.50.28.121
addnode=5.230.146.212
addnode=60.53.25.89
addnode=73.10.170.79
addnode=73.254.153.254
addnode=76.21.107.113
addnode=77.121.108.134
addnode=77.236.177.243
addnode=78.88.29.171
addnode=79.42.100.117
addnode=81.156.249.127
addnode=84.52.229.225
addnode=84.84.197.176
addnode=87.113.188.239
addnode=87.195.35.125
addnode=88.217.180.223
addnode=90.200.245.58
addnode=91.153.109.149
addnode=92.45.169.75
addnode=93.185.20.219
addnode=93.185.20.248
addnode=95.183.50.54
addnode=95.183.51.15
addnode=95.183.53.184

[hashforce101]

Put your music on

[hashforce101]

NAV Coin 2.0

Dear NAV Community!

We are very glad to announce a long list of improvements coming in our next update to NAV Coin. Primarily our goal for this release is to deliver the BIP32 update for NAV Coin. If you don’t know what BIP32 is, you can read more about it here:

https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki

It’s quite complicated, but the short version is that apart from the benefits of BIP32 itself, it will mean our wallet is now compliant with the accepted wallet standards for remote reading of the NAV blockchain. This compliance allows us to then develop javascript based web wallets and mobile wallets which are fully qualified wallets. The wallets will be able to operate without needing to download the entire blockchain which can be impractical on devices with limited storage or low performance.

After a long and at times painstaking process of attempting to retrofit the BIP32 standard of Hierarchical Deterministic Wallets to the existing NAV Coin code base we recently changed direction towards a faster and frankly better solution.

As a team we decided the best way forward was to rebase NAV Coin from a more recent fork of the Bitcoin Core which includes the BIP32 Updates and as an added bonus we also get a long list of all the other updates which Bitcoin has implemented since we last forked from them 2 years ago.

New Features in NAV 2.0

Here's the summary of some of the improvements we will be deploying:

BIP 32 - Hierarchical Deterministic Wallets

https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki

Capability to generate wallet addresses from a single private seed. This allows the user to re-generate key pairs from the seed if the wallet is lost. Backup frequency is reduced. Wallet generation methods are now compliant with web & mobile wallet standards.


BIP 38 - Passphrase-protected Private Key

https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki

Capability to encrypt and encode a passphrase protected private key. Typically intended for use on paper wallets and physical coins. Users will now be able to store their coins offline in secure cold storage.

BIP 100 - Floating block size hard limit

https://github.com/jgarzik/bip100/blob/master/bip-0100.mediawiki

Maximum block size is increased to 20MB with the maximum size for mined blocks set to 10MB. Block size is dynamic and changes in response to the volume of transactions. This future proofs the coin to be capable of handling all perceived future transaction volumes.

There are even more BIPs which will be included in the NAV 2.0 release. The full list of BIPs will be announced in the coming days when we verify their implementations.

On top of the added BIPs, the wallet we are deploying has some really nice extra features built into it:

Updated User Interface

As you can see, we’ve refreshed the branding in the wallet to match the websites branding. This branding will be rolled out through the rest of the wallet before launch. You can see the Anonymous Send feature on this send coins dialog window.



Bittrex Trading

The new wallet has the capability to connect to Bittrex with API Keys to trade NAV directly from within the wallet. You can see the current market orders, place & cancel orders as well as see your trade history.



Messages

This feature allows users to send encrypted private messages to other users by their wallet address. All communication is directly from wallet to wallet ensuring maximum privacy.



Block Explorer

The new wallet allows you to look up addresses and transactions from directly within the wallet.

The wallet also includes all the standard features you expect in a cryptocurrecy wallet (send, receive, backup, transaction history etc..)

Upcoming Features in NAV 2.1

With the new wallet deployed it means that we will now be able to finish off and release some of the work on our projects page which was previously blocked by the fact we weren’t able to use remote block chains and performance issues. This includes:

Mobile NAV Coin Wallet

As explained, we will now be able to deploy a mobile NAV wallet for both Android and IOS. Users to have a fully qualified wallet with the coins stored on your device. When we release our mobile wallet we will in a very small club of Proof of Stake coins with a mobile wallet. Then with phase 2 of the mobile wallet the NAV Coin dev team will unlocked a massive milestone; World’s first anonymous cryptocurrency transaction using a mobile phone!

Web based NAV Coin Wallet

Similar to the Mobile wallet, this allows us to build a fully qualified wallet that you can use through your web browser. You could then either run the code from your computer and / or we could integrate it into the NAV website for you to use.

Raspberry Pi Staking Unit

With the performance increases achieved by implementing all the BIP’s we’ve integrated by rebasing NAV Coin will allow us to successfully run the Raspberry Pi staking units. This is going to be a great system you can use to mine NAV very cheaply. Initially it will be a deployment which you run on your own Raspberry Pi and subsequently optionally purchasing a touch screen version from us.

Expect to see these updates released in the near future.

Action Plan for the Release

What does rebasing NAV Coin mean in practical terms?

It is quite a big transformation for NAV Coin to undertake. We did look at implementing the new code base and then refactoring the source to work with our existing blockchain. This process however could have easily taken another 2 months of development time or possibly more. We have a lot of great features planned for the next quarter and didn’t want to waste any more time by attempting the refactor to who knows what end. What we have decided to do instead is to create a new genesis block with all the updated configurations to work with the new source and start the NAV Coin blockchain again from Block Zero.

This means a couple of things will have to happen over the next few weeks to get everyone onto the new block chain.

Bittrex Coin Swap

We have contacted Bittrex Exchange to host the swap process.

We've always been working effectively with Bittrex and it's NAV markets always had the biggest volume. Based on that we believe that our Community also puts as much trust in their team as we do.

Bittrex has successfully performed many coin swaps in the past and has a very safe and reliable system in place to make sure that everything goes smoothly.

All coins will be swapped at a value of 1:1. You will still have exactly the same amount of NAV as you do now and there will still be the same total number of NAV as there are now, so your coin’s will retain the same value.

Swap period on Bittrex will take 2 weeks. We will begin the swap as soon as the new code base is tested to our satisfaction.

After that 2 week period time there will be no option to swap your coins using exchange and the old coins will no longer be valid on the exchanges.

We will offer additional 2 weeks of manual swap after that. To swap your coins manually you will need to contact Development Team directly and we can help you make the swap.

This procedure takes a lot of time and efforts, so please swap Your coins during first 2 weeks using Bittrex.

After the total 4 week swap period, the NAV Foundation will assume guardianship of any unclaimed coins. From then onwards users can contact us if they missed out on the swap and we will do our best to see they get their coins upgraded. Past that, the foundation will use the unswapped coins for covering the costs of new projects and server’s upkeep.

We are still confirming the details and timelines of the swap process with Bittrex and we will post another update when we can confirm the start date. That said, our goal is to initiate the coin swap within the next 2 weeks unless otherwise necessary.

Anonymous network maintenance

We will have to take the NAV Anonymous Network offline for maintenance so that we can begin to port the Anonymous Sending code to the new wallet and test it.

The NAV Anonymous Network will be offline from Thursday 14 March @ 9:00PM GMT until Sunday 17 March @ 9:00AM GMT or until otherwise notified.

Please keep that in mind in case you would need to use that function. We would advise not sending any coins through the anonymous network less than 15 minutes prior to the maintenance time.

Ongoing development

Anonymous Network Decentralisation

Decentralisation of the Anonymous Network is of course still in the pipeline. Once we have the coin swap sorted I will port all the work I have done previously to the new wallet and then resume working on the decentralisation project. It will only be a minor step sideways for the project, i will not have to discard my work and start over. I will update you on this project’s status and timeline on the other side of the coin swap.

As always - We would like to thank You for all Your support!

Please stay tuned & keep an eye on NAV Coin during this exciting time.

Best Regards!

- NAV Coin Development Team

Currently on Bittrex and Alcurex

[bitwho]

well to clarify. who i mean what i said about the complainers : people complaining primarily due to missing the pump..

In case that was aimed at me. I have been with Nav for the full 2 years. Did you note the grin at the end of my post?

I am not moaning at the devs. In fact I thanked them and have donated over those 2 years.

My point (like the vast number of long term Navsters vocal on this forum) is that the V1 issue is confusing and not helping. The devs ARE supporting V1 manually so we should switch V1 off until everyone is on the same fork.

Craig, Shahim, Soopy, Strugg etc. have all been performing 110% in the last few months and for that I am grateful.

And with regard to pumping and dumping only a fool would dump now with all the new fantastic features coming online.

uhmm do you know the shit storm the NAV dev would get if they simply cut it off. They are trying to honor a time frame. To allow other users , who are not as active as me and you, to get a chance to get their coins on the new chain.

the problem here , was that few exchanges, one of them being polo,  a freaking major exchange did not update in timely fashion.


you know what, i feel weird having to explain this over and over.. i don't see how the spike at polo is anything to argue about for.

devs are doing the right thing by extending the v1 life.

[hashforce101]

well to clarify. who i mean what i said about the complainers : people complaining primarily due to missing the pump..

In case that was aimed at me. I have been with Nav for the full 2 years. Did you note the grin at the end of my post?

I am not moaning at the devs. In fact I thanked them and have donated over those 2 years.

My point (like the vast number of long term Navsters vocal on this forum) is that the V1 issue is confusing and not helping. The devs ARE supporting V1 manually so we should switch V1 off until everyone is on the same fork.

Craig, Shahim, Soopy, Strugg etc. have all been performing 110% in the last few months and for that I am grateful.

And with regard to pumping and dumping only a fool would dump now with all the new fantastic features coming online.

uhmm do you know the shit storm the NAV dev would get if they simply cut it off. They are trying to honor a time frame. To allow other users , who are not as active as me and you, to get a chance to get their coins on the new chain.

the problem here , was that few exchanges, one of them being polo,  a freaking major exchange did not update in timely fashion.


you know what, i feel weird having to explain this over and over.. i don't see how the spike at polo is anything to argue about for.

devs are doing the right thing by extending the v1 life.

A swap period is fine and Devs will take care of that.Not an exchange that does not want to upgrade as per hard fork.That has changed now Poloniex will upgrade .

Manual to new coin is still available  and underway..Bittrex and Alcurex are back on track. Great talking to you

[tolikkk]

hi, blockexplorer, I think requires a fix, because it doesn't show correctly the data from my wallet and data from blockexplorer in my purse a large amount than shows the total amount in blockexplorer

and about the new wallet 2.0, which is sometimes an error stops

the question is, when will be updated richlist after the swap?

thank you

[bocyaj]

for anyone having syncing issues on the old chain, please try putting the following into your navcoin.conf file:

maxconnections=2
connect=95.183.50.58
connect=5.230.142.254

And REMOVE any other addnode lines from your config file.

What this does is only allows your wallet to have a maximum of 2 connections and the 'connect' variables will force the wallet to ONLY connect to the nodes listed above.

Without this, your wallet will try to connect to as many nodes as possible, whether on the new or old network and cause delays on syncing to the old chain.

once your wallet is open, you can verify if it has worked by typing, 'getpeerinfo'.  If you only have the nodes with IP's above, it worked.

I haven't test this on NAV since I had my coins on Bittrex for the swap, but the above method has saved numerous headaches for me on other coins.

Please let us know if this fixes the issue.

Remove the old obsolete addnde is correct, but so drastically restrict the number
of connections, IMHO not seem at all the best solution possible, and it does not help
other peers in the same condition.

Especially I would like to avoid that this idea was perceived as overall definitive solution,
valid in all cases, even in the future, because in the long run would be deleterious.

The proper functioning of a crypto currency is based on the creation of distributed
network of peers, sharing and exchange among themselves the blocks with the
transaction between all nodes.

Limit the nodes that way, it ends up transforming the structure of the peer's network of
cryptocoin in a centralized manner, making it very slow, and at the same time this
overloaded its supernodes, making them into weak points in a centralized structure.

In some extreme case can help, but in normal condition this is not the best possible solution.

completely agree Remy.  however this seems to be needed as I only know of two definitive nodes on the old blockchain.  Without adding the max connections of 2,  the wallet could get confused by connecting with nodes on the new and old chain.  I should have added a disclaimer that is only done in certain situations and should be removed immediately after.

[shahim]

hi, blockexplorer, I think requires a fix, because it doesn't show correctly the data from my wallet and data from blockexplorer in my purse a large amount than shows the total amount in blockexplorer

and about the new wallet 2.0, which is sometimes an error stops

the question is, when will be updated richlist after the swap?

thank you

Hi there is a richlist on cryptoid website (not updated in real time!) . Or do you mean the explorer inside the wallet. I don't really get your point. All time i have used it so check an address, it showed the correct amount.

If you can give more detailed information,  i can forward it to the explorer hosting

[Remy_5]

In some extreme case can help, but in normal condition this is not the best possible solution.

completely agree Remy.  however this seems to be needed as I only know of two definitive nodes on the old blockchain.  Without adding the max connections of 2,  the wallet could get confused by connecting with nodes on the new and old chain.  I should have added a disclaimer that is only done in certain situations and should be removed immediately after.

Perfect.  

In theory, the seed node should only propagate the correct nodes, but in this
transitional situation, where there are new and old wallet, all waiting on the same
port, there may be incomplete attempts.

PS:
In addition, if the wallet has been stopped for a _long_ time, it might be useful to
delete the old peers.dat file.

[Remy_5]

hi, blockexplorer, I think requires a fix, because it doesn't show correctly the data from my wallet and data from blockexplorer in my purse a large amount than shows the total amount in blockexplorer

The RichList for the old BlockChain, is for the moment still reachable to
its old url: http://www.navcoin.org/rich-list
and as far as I can see it is updated and correct.

Regarding the new blockchain, the new richlist is much more complete, but
at least in this case a little slow in the updates, but substantially correct.

In the new blockchain explorer, there is also a list of the Largest Wallets,
it is similar to the rich list, but they are two different things, do not be confused.

In case you have an urgent need to control, I have included the usual unofficial richlist,
but as usual there may be some inaccuracies.

Code:

Deep Watch Report  block 1 to 156372 at 2016-07-07 15:42:08 UTC                                             
     Hash 1634dfa569eed897bb7bdac813e5c64bf7339e57a1ae42eceb795ed8721c8dcb                                  
DWR  Rank       Address                total    share      Last (UTC)        1st (UTC)     POS    POW C-Pile
DWR     1    Na9PwB...6UCtS    10000000.000000  16.68  2016-06-06 02:33:04  2016-06-01       0      0      2
DWR     2    NaoDjc...yQSAc     4949999.900000   8.26  2016-06-06 02:33:04  2016-06-06       0      0      1
DWR     3    NLGTav...9AjAX     4949999.900000   8.26  2016-06-06 02:33:04  2016-06-06       0      0      1
DWR     4    NgiAp2...NYLxG     4942974.964792   8.24  2016-07-07 15:42:08  2016-06-03   39543      0  29332
DWR     5    NWgu38...Rz3J7     4899999.800000   8.17  2016-06-06 02:33:04  2016-06-06       0      0      1
DWR     6    NWSEfX...rqssB     4619744.878472   7.70  2016-06-20 02:38:40  2016-06-20       0      0      4
DWR     7    Ndb76o...hN71N     2355585.630122   3.93  2016-06-22 07:29:36  2016-06-13       0      0      1
DWR     8    NSjqWe...84Qfk     2288185.759900   3.82  2016-06-22 07:29:36  2016-06-13       0      0      1
DWR     9    NSeqnr...WjwDa     1803841.677524   3.01  2016-07-07 02:52:16  2016-06-04    6350      0   5004
DWR    10    NbJYKx...9u7Mi     1701758.903461   2.84  2016-06-22 07:29:36  2016-06-13       0      0      1
DWR    11    NZdHXd...G5s8B     1652168.899400   2.76  2016-06-22 07:29:36  2016-06-12       0      0      2
DWR    12    NXB5rR...VJtiQ     1214426.968584   2.03  2016-07-07 15:41:52  2016-06-03   10664      0   6282
DWR    13    Nekc2U...a9ErC     1199900.000000   2.00  2016-07-07 14:43:12  2016-07-06       0      0      2
DWR    14    NiYv2p...8p1JJ     1106074.391930   1.84  2016-06-26 02:33:04  2016-06-26       0      0      1
DWR    15    NVDtgD...Fr4dL     1078211.246478   1.80  2016-06-22 07:29:36  2016-06-10       0      0      1
DWR    16    NicQT5...fe5RV     1076481.875503   1.80  2016-07-06 15:04:00  2016-06-20     432      0    441
DWR    17    NiQzyh...T9uSy     1035476.704888   1.73  2016-06-19 12:53:36  2016-06-03    4082      0   4012
DWR    18    NbzMQu...WQibd      558139.424463   0.93  2016-07-07 11:00:48  2016-06-03     744      0    750
DWR    19    NhfDxW...v6gWF      499596.194511   0.83  2016-06-14 04:57:52  2016-06-13       1      0      1
DWR    20    NWCXzC...1SQss      480653.009581   0.80  2016-07-07 15:41:52  2016-06-03    4199      0    509
DWR    21    NgXr3W...vyAfF      477684.390839   0.80  2016-07-05 20:22:56  2016-07-04       0      0      5
DWR    22    NN2jTv...r9orR      469336.987966   0.78  2016-07-06 07:35:12  2016-06-03     928      0    932
DWR    23    NiZwVH...R8Vxd      434722.361201   0.72  2016-07-07 15:34:24  2016-06-03    5612      0   2164
DWR    24    NWQyCL...ik1PL      409000.000000   0.68  2016-07-02 02:14:40  2016-06-13       0      0      1
DWR    25    Nf3BJB...G2sEU      390044.188837   0.65  2016-07-07 15:26:08  2016-06-03    3850      0   1984
DWR    26    Nb5Q5x...qzGJe      348824.053585   0.58  2016-07-06 14:27:28  2016-06-03      86      0     88
DWR    27    NMsVo3...7r4cs      334904.667751   0.56  2016-06-06 05:15:44  2016-06-03      46      0     52
DWR    28    NfHBNj...WobmN      313909.294127   0.52  2016-07-07 15:39:12  2016-06-14    2194      0   1389
DWR    29    NTDDhw...DLBhe      300821.345989   0.50  2016-07-03 08:29:04  2016-06-04     239      0    240
DWR    30    NRxCcT...dGTbk      293730.518384   0.49  2016-06-27 23:00:00  2016-06-14       0      0      1
DWR    31    NTRzvV...tFAqA      216215.247766   0.36  2016-07-06 00:05:04  2016-07-02       1      0      1
DWR    32    NaqyfU...MV2K9      215146.668668   0.36  2016-07-07 15:06:08  2016-06-03     161      0    163
DWR    33    NYJSZa...Yv3ZL      211722.907495   0.35  2016-07-07 15:39:44  2016-06-03    1971      0   1543
DWR    34    NTUCeR...7EAj8      207489.901340   0.35  2016-07-06 00:05:04  2016-07-06       0      0      1
DWR    35    NQzRPy...uymRT      194645.273520   0.32  2016-07-07 15:00:16  2016-06-27     454      0    456
DWR    36    NYiwzX...tYhGk      158947.577914   0.27  2016-06-13 08:09:36  2016-06-01    1345      0    865
DWR    37    NdNekw...TdVAZ      154000.934702   0.26  2016-07-06 01:15:12  2016-06-04    1180      0    864
DWR    38    NVgmJU...Pb1b7      150073.837972   0.25  2016-07-07 15:37:04  2016-06-03    2731      0    866
DWR    39    NaU5qx...46BN9      147000.000000   0.25  2016-07-06 01:25:36  2016-06-03       0      0      2
DWR    40    NfQJDy...3TMiG      143153.926986   0.24  2016-07-07 11:10:56  2016-06-27       9      0     13
DWR    41    NWKF67...51ecs      134448.465157   0.22  2016-07-07 09:30:24  2016-07-04       7      0      9
DWR    42    NdSaNQ...e7UDf      116519.964246   0.19  2016-07-07 15:35:12  2016-06-12     520      0    514
DWR    43    NMTjWT...AD4V8      113775.523742   0.19  2016-06-04 01:43:44  2016-06-04       0      0      1
DWR    44    NdwYDT...64s7s      110693.692096   0.18  2016-07-07 15:05:04  2016-06-04     889      0    500
DWR    45    NXryKP...ebABU      103231.673531   0.17  2016-07-07 15:15:44  2016-06-03     979      0    473
DWR    46    NiJyHq...F13LE      103188.484119   0.17  2016-07-07 15:32:16  2016-06-03    1014      0    777
DWR    47    Nc3Xur...TNsdy      100369.844617   0.17  2016-07-07 15:20:00  2016-06-08     894      0    397
DWR    48    NUftRd...1rGHs      100136.750575   0.17  2016-07-06 21:01:36  2016-06-03     162      0    168
DWR    49    NS9MCQ...PyS1m       83542.293147   0.14  2016-06-13 08:09:36  2016-06-01     740      0    399
DWR    50    NMqF9t...sxXrT       80513.428627   0.13  2016-06-13 08:09:36  2016-06-01     722      0    420
DWR    51    NdjxXB...QXnFB       77754.318653   0.13  2016-06-13 08:09:36  2016-06-01     725      0    356
DWR    52    NerBSP...J48SM       67973.547506   0.11  2016-07-07 12:53:04  2016-06-03      39      0     40
DWR    53    Ng3Hnv...avozu       61010.429044   0.10  2016-06-20 05:53:36  2016-05-12   14125      0    365
DWR    54    NgucLL...4ZRYh       60155.519177   0.10  2016-07-07 14:40:16  2016-06-03      40      0     41
DWR    55    NgpyGU...x2Y5L       60139.398766   0.10  2016-07-07 13:37:04  2016-06-03      48      0     49
DWR    56    NizS5V...3kwAX       60128.704657   0.10  2016-07-07 15:37:52  2016-06-03      32      0     34
DWR    57    NUDke4...i7ugk       53657.377283   0.09  2016-07-07 15:40:48  2016-05-12   13024      0    243
DWR    58    NPRfHV...HUifT       50225.108097   0.08  2016-07-07 14:15:12  2016-06-11     282      0    196
DWR    59    NTDNVR...5vDd8       49131.426225   0.08  2016-07-07 12:46:56  2016-06-11     310      0    230
DWR    60    NVtky7...hTKSL       40127.603249   0.07  2016-07-07 00:41:52  2016-06-05     212      0    199
DWR    61    NVBhMo...GvC9G       30899.406190   0.05  2016-07-07 01:26:24  2016-07-07       0      0      1
DWR    62    NZqoLb...Be9KV       26181.054974   0.04  2016-07-06 00:02:24  2016-06-14     141      0    104
DWR    63    NLkEcT...EYcot       25513.384863   0.04  2016-07-07 14:00:00  2016-06-05      87      0     84
DWR    64    NaX7KL...WTuoA       25294.124647   0.04  2016-07-06 22:49:36  2016-06-04      44      0     18
DWR    65    NhaeTt...NaPoC       23677.695305   0.04  2016-07-04 05:02:56  2016-06-03      85      0     53
DWR    66    NizhaA...7h12p       22789.597181   0.04  2016-07-03 21:28:00  2016-07-03       0      0      1
DWR    67    NgKQrR...dw2kF       20238.011017   0.03  2016-06-15 16:42:24  2016-06-04      59      0     57
DWR    68    Nh7dv9...pfwjf       20159.916543   0.03  2016-07-06 23:20:32  2016-07-06       0      0      1
DWR    69    NLuDD9...M32NN       19753.883735   0.03  2016-07-06 13:12:16  2016-07-06       0      0      1
DWR    70    NYuKYF...ej2UQ       19111.347571   0.03  2016-07-07 11:12:00  2016-06-20      68      0     69
DWR    71    NPdVzK...EoyMd       16849.987705   0.03  2016-07-06 16:30:24  2016-07-05       3      0      7
DWR    72    NgotyM...phzhQ       14117.965392   0.02  2016-07-06 18:46:24  2016-06-01     206      0     77
DWR    73    NRsZoV...XeCGH       10002.833561   0.02  2016-07-07 08:09:04  2016-07-04      11      0     12
DWR    74    NYznZD...SJhmU        9607.032307   0.02  2016-07-07 14:43:12  2016-06-03       5      0     16
DWR    75    Nd8u8H...fd3x3        9028.785753   0.02  2016-07-06 18:33:52  2016-06-04      48      0     39
DWR    76    NPP6Vx...8A4CU        7996.877133   0.01  2016-07-07 15:31:28  2016-07-05       2      0      4
DWR    77    NLEx6R...K669E        7017.170821   0.01  2016-07-05 15:46:08  2016-06-04      50      0     46
DWR    78    NhfUtg...4vvGQ        5517.228136   0.01  2016-07-06 13:24:32  2016-06-04      20      0      1
DWR    79    Nfh8ha...Dc1FA        3932.427523   0.01  2016-07-06 02:56:16  2016-07-06       0      0      1
DWR    80    NZjh6G...wtBZw        3534.756057   0.01  2016-07-06 16:30:24  2016-07-06       0      0      1
DWR    81    NP21hv...nvSju        3149.655541   0.01  2016-07-07 01:10:56  2016-07-07       0      0      1
DWR    82    NaS1Eb...8UA5d        3120.096163   0.01  2016-06-10 14:15:44  2016-06-10       0      0      1
DWR    83    NNjz1x...AbTpE        2784.410560   0.00  2016-06-27 22:41:52  2016-06-13       0      0      1
DWR    84    NXUKxN...zXG9f        2000.000000   0.00  2016-07-05 02:25:52  2016-07-05       0      0      1
DWR    85    NbV6iZ...zwWir        1881.912154   0.00  2016-06-30 12:58:56  2016-05-13     512      0     16
DWR    86    NbDYv6...de8b9        1800.000000   0.00  2016-07-06 01:55:12  2016-07-06       0      0      1
DWR    87    NdeXFg...7PeeQ        1724.909403   0.00  2016-07-07 02:04:16  2016-05-13     538      0     12
DWR    88    NUPUqf...Nnx1f        1652.808496   0.00  2016-07-05 09:38:56  2016-05-13     446      0     10
DWR    89    NZMCRi...wNDVi        1584.800000   0.00  2016-06-21 19:19:44  2016-06-21       0      0      1
DWR    90    NTpr56...d9MyN        1316.161369   0.00  2016-07-04 06:17:36  2016-05-13     432      0      7
DWR    91    NQrtJD...o2dxB        1000.000000   0.00  2016-06-03 21:17:20  2016-06-03       0      0      1
DWR    92    NZpTYy...KbVkg         902.818704   0.00  2016-07-06 05:04:16  2016-06-04       5      0      6
DWR    93    NQx7Tc...epof5         899.799900   0.00  2016-06-04 14:21:04  2016-06-04       0      0      1
DWR    94    NTJAiR...Sbzcu         799.999800   0.00  2016-05-14 08:30:56  2016-05-14       0      0      1
DWR    95    NVtqsT...HfeFh         778.536612   0.00  2016-07-05 21:56:32  2016-06-04      11      0      2
DWR    96    NaRZDk...woXkq         702.803520   0.00  2016-07-06 22:55:44  2016-06-08      10      0      1
DWR    97    Ne3bSS...1aYbk         671.677259   0.00  2016-07-01 01:16:48  2016-05-13     406      0      5
DWR    98    NUyWv7...VpuUZ         498.899900   0.00  2016-07-07 13:40:16  2016-06-03       0      0      1
DWR    99    Nj4hig...jyXZ6         466.679080   0.00  2016-07-04 01:37:52  2016-06-11       3      0      4
DWR   100    NTmVEB...XYq8N         272.174306   0.00  2016-06-22 09:31:28  2016-06-13       0      0      1

[soopy452000]

Hi there
I have around 30K navs and want to  transfer them from bittrex to my own wallet

I'm using the wallet on Linux, but i'm having a  few problems..........

fist of all what i have done:


╭─ivan@Rebbeca ~  ‹master*›
╰─➤git clone https://github.com/navcoindev/navcoin2

╭─ivan@Rebbeca ~  ‹master*›
╰─➤sudo apt-get install qt5-default qt5-qmake qtbase5-dev-tools qttools5-dev-tools build-essential libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev  libssl-dev libdb++-dev libminiupnpc-dev

╭─ivan@Rebbeca ~  ‹master*›
╰─➤sudo apt-get install libgmp3-dev

╭─ivan@Rebbeca ~  ‹master*›
╰─➤cd navcoin2

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤qmake

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤make

╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤   ./NavCoin2-qt.pro
./NavCoin2-qt.pro: 1: ./NavCoin2-qt.pro: TEMPLATE: not found
./NavCoin2-qt.pro: 2: ./NavCoin2-qt.pro: TARGET: not found
./NavCoin2-qt.pro: 3: ./NavCoin2-qt.pro: VERSION: not found
./NavCoin2-qt.pro: 4: ./NavCoin2-qt.pro: INCLUDEPATH: not found
./NavCoin2-qt.pro: 5: ./NavCoin2-qt.pro: QT: not found
./NavCoin2-qt.pro: 6: ./NavCoin2-qt.pro: DEFINES: not found
./NavCoin2-qt.pro: 7: ./NavCoin2-qt.pro: DEFINES: not found
./NavCoin2-qt.pro: 8: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 9: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 10: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 12: ./NavCoin2-qt.pro: CONFIG: not found
./NavCoin2-qt.pro: 14: ./NavCoin2-qt.pro: Syntax error: word unexpected (expecting ")")

First error
Then i try to open the executable


╭─ivan@Rebbeca ~/navcoin2  ‹master*›
╰─➤  ./navcoin-qt

that open a nice UI  but  that say  12 weeks  behind.....
i download  http://www.navcoin.org/files/Navajo-Blockchain.zip
and extract it on  ~/.navcoin2  hidden folder
after  restar the app still  saying  12 weeks behind
Then i ask a frined   how use NAVS on windows and  told me to add a list of nods on a config flle
as far as i can se the only config file is the      ~/navcoin2/./NavCoin2-qt.pro
but i cant do that run.....


any clue  what i'm doing wrong

cheers and  thanks in advance

Hi Mulleivan,

We understand your concerns please follow the following steps.

1. Please create a file named navcoin.conf and add the following nodes as shared by Shahim a few posts above this.

Code:

addnode=1.10.221.32
addnode=1.10.221.56
addnode=1.34.180.245
addnode=104.236.223.182
addnode=108.95.144.170
addnode=109.110.66.76
addnode=118.173.178.240
addnode=122.166.167.187
addnode=122.53.112.74
addnode=123.3.30.61
addnode=14.192.209.23
addnode=160.176.171.123
addnode=171.6.250.169
addnode=175.214.144.141
addnode=176.154.77.92
addnode=184.167.180.122
addnode=185.17.207.189
addnode=185.61.148.209
addnode=199.189.131.12
addnode=2.121.162.167
addnode=2.84.167.61
addnode=208.95.215.81
addnode=212.180.171.44
addnode=213.108.119.84
addnode=219.88.236.170
addnode=219.88.238.26
addnode=41.142.44.167
addnode=45.50.28.121
addnode=5.230.146.212
addnode=60.53.25.89
addnode=73.10.170.79
addnode=73.254.153.254
addnode=76.21.107.113
addnode=77.121.108.134
addnode=77.236.177.243
addnode=78.88.29.171
addnode=79.42.100.117
addnode=81.156.249.127
addnode=84.52.229.225
addnode=84.84.197.176
addnode=87.113.188.239
addnode=87.195.35.125
addnode=88.217.180.223
addnode=90.200.245.58
addnode=91.153.109.149
addnode=92.45.169.75
addnode=93.185.20.219
addnode=93.185.20.248
addnode=95.183.50.54
addnode=95.183.51.15
addnode=95.183.53.184

2. Place this navcoin.conf file on  ~/navcoin2/

3. Let it sync.

Please write back if you experience any further issues.

Warm Regards,
~SoopY~

[nodemonster]

ANY NEWS IS GOOD NEWS! ?


http://www.newsbtc.com/2016/07/07/arbitrage-nav-coin/

front page on blockchain.info

[The Bitcoin Co-op]

Very interesting story developing here for traders. I decided to cover it on NewsBTC: http://www.newsbtc.com/2016/07/07/arbitrage-nav-coin/

EDIT: somebody beat me to it, wow 

[bocyaj]

Very interesting story developing here for traders. I decided to cover it on NewsBTC: http://www.newsbtc.com/2016/07/07/arbitrage-nav-coin/

EDIT: somebody beat me to it, wow 

Very nice article and great overview of the situation, Thanks!  It might even push Poloniex to update sooner rather than later.

[Strugg]

Very interesting story developing here for traders. I decided to cover it on NewsBTC: http://www.newsbtc.com/2016/07/07/arbitrage-nav-coin/

EDIT: somebody beat me to it, wow 

Very interesting article, thank You! Retweeted
https://twitter.com/TheAndrewWagner/status/751118357714210816