Si quieren publicar un artículo promocional en nuestro sitio web, escríbannos a contacto@criptonoticias.com

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.

Also Cryptopia's explorer shows 1009112 with nodes:

addnode=194.135.84.136:1856
addnode=192.71.218.138:1856
addnode=24.98.149.31:1856

I'll have to fix those images { perhaps a day shot} and size reduction , did it before i drove to work lol

Less than 24 hours to launch

https://mega.nz/#!6h9mhaha!0_deAyYPMXuWGV6CUTonIOFRf_TgB6HPzttmfVTVhug
this one should be good

[server=1
listen=1
daemon=1
rpcport=1857
port=1856
rpcallowip=127.0.0.1
rpcconnect=127.0.0.1
rpcallowip=localhost
rpcconnect=localhost
rpcuser=**user**
rpcpassword=**password**
addnode=tes1.altcoinsfoundation.com
addnode=seed1.teslachain.info
addnode=seed2.teslachain.info
addnode=seed1.teslacoinfoundation.org
addnode=192.241.153.16
addnode=108.208.35.108
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) Learn history of other coins swapping and be calm. [/size][/b]