I think so at this point.  I agree that it would probably be a good idea to get Poloniex involved.  I think Poloniex would be open to it since everyone would otherwise be moving all coins over to their competitor.  Not sure if its too late at this point, but would be helpful to a lot of people.  Poloniex currently has about 730k NAV on the sell side, which doesn't include the coins that are just sitting there.

nice, re-tweeted.  gonna let my NAV stake a little bit more before moving it to Bittrex. 

About the bounty,  I agree doing it after the swap is the probably the best idea.  But I think the timing is perfect to start getting an idea of numbers now so all the good news can build off of each other.

ex:
check out this new updated awesome coin
vs
check out this new updated awesome coin, break the encryption and win 10 BTC !

Just my two NAVcoins.

Awesome work guys ! you came through once again.

Wallet is ready, check.
PR is loaded and ready, check.
community is ready to spread the word, check.

But is that enough ?  I think we can do more, and need to do more to get us noticed with all that is going on in the crypto world right now.


The NAV team has done a fantastic job, let's us 'the community' step up our game to their level and add some fuel to this NAVtrain (corny? sure).
The main focal point of NAVcoin is the unbreakable anonymous transactions.....  I have full faith in the product, but don't think this has made its way around the crypto world yet, lets try to change that.
I suggest we start another reward fund that would go to anyone who can trace an anonymous transaction.  I think if we can amass a large enough bounty, maybe some serious players will give it their best shot.  Let's get more people talking about NAVcoin.

I will start off the bounty with 50,000 NAV coins !  Anyone willing to help out, please speak up and help grow this bounty.

The first time around we managed to raise 10 BTC worth of NAV coins, but I know we can do better !

Guess I missed the bounty in January this year (seems a lot of us did from what i can tell), but I see a page was setup on our site to track it.  Not sure if this is a good idea right now or not with the upcoming swap, will let the devs/community decide the best way to do this.

It has been way too quiet lately, lets come out from under this rock where we have been hiding and do our part to spread the word.

If you don't like this idea, no worries, try to think of something else that we can do to help.

Nice work on the new wallet NAV team !!!

Excited to get my coins moved over.

still no movement on the exchanges ..... guessing there is just too much stuff going on in the crypto world right now; ETH/DAO's/halving/etc...

We need to make sure the word gets out to as many people as possible.  This should bring the volume up on the exchanges, but more importantly avoid the headaches of hundreds of manual coin swaps for those that miss it.  I assume a snapshot will be taken of the NAV 1.0 chain to ensure nothing gets lost.

Keep up the good work guys !!!

Hi Raulll,

The syncing process can take a VERY long time and involves many restarts to get the sync process to start again.  It took me about a week to get up to date and had to monitor it quite often.

Here is a link to a blockchain that is a only a few days old:

https://mega.nz/#!TVdVWLqY!1oGbDWtchHG0gG65R-t99CPXpWFXde6_JU_w3xHmaYQ

extract that in your roaming directory and the following nodes to your .conf file:

addnode=67.71.49.191:1856
addnode=188.134.72.213:64571
addnode=188.134.72.213:1856
addnode=104.28.21.109:1856
addnode=194.135.84.136:1856
addnode=24.98.149.31:1856
addnode=24.98.149.31:58041
addnode=188.246.71.198:1856
addnode=89.143.80.234:1856
addnode=162.255.117.105:63927
addnode=193.198.102.16:36182
addnode=82.176.15.155:46850
addnode=193.198.102.16:1856
addnode=82.176.15.155:1856

don't forget to backup your wallet.dat file somewhere safe just in case.


* for full information, read the post only a dozen or so above this one.

ok, think I figured it out... seems like a bug on blockexperts.  I would take a bet that there are no coins missing.

If you click on the "show raw data" link for block 1009413, it shows you a different blockhash than what the site shows you for this block.


so blockexperts is showing the blockhash from the confirmed block 1009413, but the details for this block are being pulled from the orphan block 1009413.

if you look at the raw data for the block on multifauceet, it is correct.

Hi Richie,

that is quite odd....  not even sure how that's even possible unless its a glitch/bug within the blockexperts site.  I see both the before/after blocks match perfectly on both explorers.

I see the sending address "5g5Yi5cux747U4nmPPVieUsBr9ejuArkZC" does not return anything on the blockexperts site, but shows up valid on the multifaucet.

It seems blockexperts shows the correct block, but none of the transactions/data within it for some reason.  The built in block explorer in my QT wallet matches the multifaucet site and shows the transaction you listed.  Also noting that were 20 transactions in block 1009413, didnt look through every single one, but the ones I checked don't show up on blockexperts.

I do see an odd transaction in the previous block that I don't fully understand: (shows up the same on both explorers)

http://www.multifaucet.tk/index.php?blockexplorer=TES&txid=b29e7b6bca13bc56c8b2a0406e39f850e15ab7262d0eefddbbc4b25056bf3bed

Can't explain this, but I am no expert.

Are the coins actually missing ?  

guessing this was brought up via a support ticket to Bittrex ?  if so, feel free to point them our way or my previous post and we can ensure they are on the proper chain if they are missing coins.

I am finally back in sync with the network and it looks like we have got passed this fork.  A couple stragglers are still on the wrong side of the fork, but the majority of us are on track.

Here are the nodes I see still on the wrong chain:
66.255.209.70:1139
46.239.4.8:4986

if you are on the bad chain, you can tell quickly because you are stuck on block 1008577.  But to be absolute certain, here is the proper blockhash from the good chain's block 1009455:

getblockhash 1009455
3b343c49ef93acad94cc2eb1bbf8330db80dd4a141e834f7dc30274415d16916

if your blockhash does not match above, you need to resync.

If on the wrong chain, you will have to resync your wallet :-(.  Yes, if you resync your wallet from scratch, you will sync with proper chain..... it will take a REALLY long time, like a week or so, but you will get there eventually.  To avoid this hassle, I have uploaded my blockchain to mega for others to download.  this blockchain is synced up to block 1009450.

https://mega.nz/#!TVdVWLqY!1oGbDWtchHG0gG65R-t99CPXpWFXde6_JU_w3xHmaYQ

It might be a bit extreme, but here is the addnode list I used:


I have not been able to verify a withdraw/deposit with Bittrex as its wallet is currently in maintenance mode.  But it was in sync with the block explorers when I last checked it before it went into maintenance mode.  I haven't confirmed with cryptopia, but will once my coins finish staking.  Can't check on yobit either since their wallet is still in maintenance mode and has been for a while.

Rest assured, the chances of any coins getting lost are pretty slim.  The fork wasn't really that long, it broke off on block 1008041(ish) and seems to have gotten stuck around 1008577.

The only way you could have lost coins is if you sent coins from an exchange to an address that was created on the bad chain after the fork.  If you sent them to an existing wallet address, they should show up once you get back on the right chain.

Once you're in sync, help support the network and leave your wallet open and let your coins stake. :-)

If anyone is still having issues, let me know and I will try and help you through it.

yep, im an idiot.  I signed up on megafileupload by mistake.

Here it is at 789,000 blocks

https://mega.nz/#!bJcR1KxD!jXDbjNbCY_fivXTpW-BWsfY93ELAI2sydicu09l4544

that was working perfectly for me.  make sure you don't have any addnodes in there as well.  look at your debug.log and see if it got any errors from your conf file.

once the nodes are connected to your wallet, verify they are still on good chain via getpeerinfo.

tired to upload my blockchain that I started from scratch to my new MEGA account so you could download  ( at 742,000 blocks ), but apparently I need the premium account to share links publicily.

if anyone knows a free way for me to get this file out, i will do it.

yes there seems to be two forks, one around block 1009057 and one around 1008577.

I've done a couple test withdrawals from Bittrex of 5 TES the other day and I can see them on the explorer:

http://www.multifaucet.tk/index.php?blockexplorer=TES&txid=f23cb46559fdc8ae62ea09f7351b1a71bda3097309c2e75937c41a388832b668
http://www.multifaucet.tk/index.php?blockexplorer=TES&txid=7111c49d234f52c7eaa6a1c34b5a0cdde10fe2ae96b99d9ce030306f3608cc39

so this proves that the explorers and Bittrex are on the same chain.  it also proves that the block update status of the TES wallet on Bittrex is not always right.  Currently Bittrex wallet says last block update was 176 minutes ago and the explorer shows 10 blocks in that time frame.  so there is a time delay in the reports or something is funky.

Anyways, this at least allows me to focus on meeting the block explorer chain which provides much more info.... blockhash, blockcount, etc...

I let my wallet try to sync from scratch overnight with just about every addnode I could get my hands on so I could get a good idea of where everyone stands.  this morning I had 15 connections and took a look through to see who was on what chain.

on the "good" chain: 1009057ish
194.135.84.136:47930
193.198.102.16:39684
188.134.72.213:55485
82.176.15.155:42332
162.255.117.105:63089


on the "bad" chain: 1008577ish
192.71.218.138:1856
188.246.71.198:1856
104.172.24.79:58883

The rest of the connections were in the same boat as me, trying to catch up.

The problem I am having now is that any wallet on the new chain is not syncing blocks to my wallet.  I assume there is some way to disable this

the only node I can currently get a connection too from the "good" chain is below, and it won't send me any block updates.... I assume the "inbound" field at false has something to do with it.

{
"addr" : "194.135.84.136:1856",
"services" : "00000001",
"lastsend" : 1460726916,
"lastrecv" : 1460726887,
"conntime" : 1460726054,
"version" : 63001,
"subver" : "/Satoshi:9.1.0.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1009099,
"banscore" : 0
}

gonna let it sit for a while... maybe all day and see if can reconnect to anyone else.

Here is my current Teslacoin.conf to only connect to nodes on the good chain.  **my getpeerinfo list shows the odd port numbers, 47930,39684, etc... I also added the default 1856 port as well.

maxconnections=5
connect=194.135.84.136:47930
connect=193.198.102.16:39684
connect=188.134.72.213:55485
connect=82.176.15.155:42332
connect=162.255.117.105:63089
connect=194.135.84.136:1856
connect=193.198.102.16:1856
connect=188.134.72.213:1856
connect=82.176.15.155:1856
connect=162.255.117.105:1856


If I start from the cryptochainer file, the only chain I can get on is the "bad" chain and I get the same that Rw13enlib88 shows, stuck on block 1008577 and last block 1009099.  it shows the higher one as a last block since you are connected to a node from that chain, but I could never get up there.

Hey guys,

I am still not having any luck here.   I can't seem to get in sync with Bittrex. :-(

if anyone in sync with them can post what they did or provide a blockchain to download, my offer still stands. 20,000 TES reward.

Thanks.

ok, well that's some good news.  however, i can't get that one to sync anymore.... stuck on block 1008528. looks like others are as well. what is your blockhash for this block?


getblockhash 1008528

e004c0205ce9af5fdaf1f95e6ad652b3e8117991e23755e741825105fed6d2f2


Maybe i just need to let it sit for a while, will check on it later.  Once I am up and running and confirmed on the Bittrex chain, will send you the 20k TES.

I will also edit my previous post saying not to use your site.

thanks for the help !!!

Thanks Steve !! I wish I would have found your site years ago, it is an awesome idea and would have saved me A LOT of time.  i agree with the comment "if that's even correct".  the chain that is/should be correct is whatever Bittrex is on, we can update explorers easily, Bittrex however is quite a bit more complicated.  does anyone know if its possible to pull the info from Bittrex's teslacoind ?  pretty sure their api is only trading oriented.

I will be testing them out first once I get in sync.

EDIT: Just realized that on bittrex's wallet tab, you can see when the last time a block update occurred and it seems to line up with the explorers...... a very good thing.

nice, so im not crazy.  the more the merrier, thanks.  I am curently at 559k.  For anyone with a wallet running, please confirm against the block explorers:

http://www.multifaucet.tk/index.php?blockexplorer=TES
https://www.blockexperts.com/tes

yobit has been down for a while, their wallet has been in maintenance mode for a while now.  I haven't contacted them but seen a few people complaining about the support response time.

Having issues here getting the wallet to sync up here as well. 

I originally tried over the weekend, it was really tough.  I started from scratch with an empty wallet.dat, I noticed that after about 130,000 blocks the wallet paused the sync process every 500 blocks, not sure why but noticed in the debug.log that it was saying something like " reached getblocks limit of 500".  it wasn't exactly every single 500 blocks, but a large number of pauses caused my sync process to take about 4+ days with constant TLC.  I noticed that restarting the wallet every once and a while seemed to give it a 'kick' to start syncing again.  in the end, my wallet forked somewhere around block 100080 (compared blockhash to that on the explorer) and would never fully sync.  I tried using older versions of the wallet, but no luck. 

Took a different approach  and decided to try the cryptochainer blockchain.  it seems this blockchain is also on a different fork than the block explorer.  DONT USE IT !!!  tried it a couple times and no luck.  Can anyone confirm being on the same chain as the block explorer when using this wallet ?  I checked the blockhash for the first block downloaded after importing this chain and it doesn't match the block explorer.

unless someone can confirm they are good after using this, DONT USE THE CRYPTOCHAINER BLOCKCHAIN  . Don't get me wrong, this site looks awesome and I will definately be using it in the future, but right now its not doing Teslacoin any good.

I then started playing around with my Teslacoin.conf file and things seem to be going smoother now, still need to sync up but it going much faster.  Here is what I have done so far:

** update Teslacoin.conf:
since it seems there are different forks out there, I am using the "connect=<node IP>" as opposed to "addnode=<node ip>".  I go to http://www.multifaucet.tk/index.php?blockexplorer=TES&network_info and grab the nodes that it is connected too, copy those nodes into my conf file and change addnode= to connect=.   the connect should only use the nodes you specify here as opposed to looking for new ones.  However the nodes hard coded int he wallet will still connect.  Maybe my interpretation is incorrect here, but it seems to be working.

ex:
connect=194.135.84.136:1856
connect=192.71.218.138:1856
connect=24.98.149.31:1856
connect=67.71.49.191:1856

1) BACKUP WALLET.DAT !!!!!!
2) double check that you backed up your wallet.dat somewhere safe !!!
3) Remove the entire Teslacoin directory from Roaming 
4) open the wallet (latest version, v3.1.0.1-1-g023d801-Teslacoin) so it re-creates the Teslacoin directory in roaming and starts syncing.  * do not add your wallet.dat file yet, the wallet syncs much faster if its empty.
5) leave the wallet open and monitor the blocks in the help -> debug -> information window to see the blockcount increasing.
6) this time, the sync went non stop till 465,000 blocks ( in about 2-3 hours ).
7) I was stuck at this block overnight
close the wallet and copy of the entire Teslacoin directory somewhere else.
9) Delete the Teslacoin directory from the roaming folder
10) launch the wallet and then close it.  This just essentially re-creates the directory you just removed. ( I think the wallet does something different when it thinks its an initial install )
11) copy over the previous contents of the Teslacoin roaming directory back in place.
12) re-launch wallet.
13) repeat steps 8-13 if your sync pauses for a long time, until you are in sync.

I am still not in sync, currently at 503XXX, but the above method is working much faster than my previous attempts.

If anyone has a blockchain that is confirmed in sync with the explorer, can you please post a link so myself and others can download.  I will give a 20,000 TES bounty for this.

I think the issue here is that their are wallets on different forks and it is causing confusion during the syncing process.

Maybe the problem is between the monitor and keyboard here, but figured I would send out what I have found in case others are seeing the same thing.

it doesn't have to be multiple addresses, it can be multiple 'chunks' within the same address.  I am not sure what the official term for 'chunks' is, but I am referring to a grouping of coins that are the same age.  If you look in coin control, a single address can have hundreds+ of chunks in it.   I don't really have an explanation other than what I have noticed over the past year and what Remy showed me.  Remy did an analysis a while back charting the blocks generated and how many coins it took and how long, etc.... it was very detailed and lined up with what I observed.  So no explanation, just observation.  Remy could probably provide better details.

I'm just regurgitating what he figured out.  On that note, a big kudos to Remy for his continued in depth and very intriguing block chain analysis.  I believe this sort of analysis is of great importance when looking ahead into the future of Navajo.  Thanks Remy !

A good rule of thumb would be to take a look in coin control every once and a while and sort your coins by smallest size as well as oldest age (you will notice some chunks just don't generate a block for some reason).  I then send the 'under performing' chunks together to myself into groups of 1.5k-3k.  if you keep your wallet running 24/7 and do the above, you should be pretty close to maximizing your POS returns.

I think blocks of 1500ish coins are your best bet, it seems to end up like this anyways.

i stepped out the scene for a while, but trying to get caught up.  sad indeed to see the lack of movement here.

I will match your 1,000,000 THC for a takeover/come back bounty.  Lemons ?