Something is wrong. 

The website shows the current block is 629467... but my wallet shows it's stuck @ 616660.
Yes, I have the latest version of the wallet.

Actually... peer info is all over the board.


[
{
"addr" : "18.188.145.216:10556",
"addrlocal" : "76.29.29.254:51352",
"services" : "00000001",
"lastsend" : 1539146757,
"lastrecv" : 1539146757,
"bytessent" : 754734,
"bytesrecv" : 12129002,
"conntime" : 1539145076,
"pingtime" : 0.05800600,
"version" : 70017,
"subver" : "/Satoshi:2.1.0/",
"inbound" : false,
"startingheight" : 616660,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "51.15.162.24:10556",
"addrlocal" : "76.29.29.254:51380",
"services" : "00000001",
"lastsend" : 1539146772,
"lastrecv" : 1539146772,
"bytessent" : 14332,
"bytesrecv" : 81185,
"conntime" : 1539145091,
"pingtime" : 0.24202500,
"version" : 70017,
"subver" : "/Satoshi:2.1.0/",
"inbound" : false,
"startingheight" : 624960,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "198.23.253.188:10556",
"addrlocal" : "76.29.29.254:51381",
"services" : "00000001",
"lastsend" : 1539146772,
"lastrecv" : 1539146772,
"bytessent" : 13945,
"bytesrecv" : 89014,
"conntime" : 1539145092,
"pingtime" : 0.06500700,
"version" : 70017,
"subver" : "/Satoshi:2.1.0.2/",
"inbound" : false,
"startingheight" : 624960,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "142.93.100.247:10556",
"addrlocal" : "76.29.29.254:51575",
"services" : "00000001",
"lastsend" : 1539146780,
"lastrecv" : 1539146780,
"bytessent" : 146118,
"bytesrecv" : 2221365,
"conntime" : 1539145219,
"pingtime" : 0.14601500,
"version" : 70017,
"subver" : "/Satoshi:2.1.0.1/",
"inbound" : false,
"startingheight" : 616660,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "81.84.61.95:10556",
"addrlocal" : "76.29.29.254:53329",
"services" : "00000001",
"lastsend" : 1539146728,
"lastrecv" : 1539146729,
"bytessent" : 421,
"bytesrecv" : 1955,
"conntime" : 1539146488,
"pingtime" : 0.40404000,
"version" : 70017,
"subver" : "/Satoshi:2.1.0/",
"inbound" : false,
"startingheight" : 574626,
"banscore" : 0,
"syncnode" : false
}
]

As for an exchange for this coin:

As long as there is an explorer -- why not add it to Bisq?
https://bisq.network/

No exchange 'listing fees' and keeps it in a P2P Exchange environment!

As long as there is an explorer -- why not add it to Bisq?
https://bisq.network/

No exchange 'listing fees' and keeps it in a P2P Exchange environment!

Just bumping to see if there is any news on this coin 

Yes, a lot of us were frustrated and pulling our hair out.
However, the issue was quickly identified and a solution was deployed in a matter of days.

It was a tough time, for sure, but we got back on track pretty quickly.

As of right now 2TB would bring appx 200/month based on the burst mining calculator.

You just fill the 2TB with plot files and off you go.
You can always delete the plot files whenever you want... no need to buy a new drive.

Keep in mind, 200 a month doesn't sound like a lot.
There also was a time when 200 ltc didn't sound like a lot either 

Does anyone know why I keep seeing these messages in my debug.log file:

connect() to 12.150.98.xxx:10556 failed after select(): Connection refused
connect() to 78.24.221.xxx:10556 failed after select(): Connection refused
connect() to 90.150.185.xxx:10556 failed after select(): Connection refused
connect() to 159.203.134.xxx:10556 failed after select(): Connection refused
connect() to [2003:85:8f11:9a00:57b:5c4f:f5e3:xxxx]:10556 failed after select(): Permission denied
connect() to 46.7.69.xxx:10556 failed after select(): Connection refused
connect() to 79.224.185.xx:10556 failed after select(): No route to host
connect() to 78.24.221.xxx:10556 failed after select(): Connection refused
connect() to 90.150.185.xxx:10556 failed after select(): Connection refused
connect() to 159.203.134.xxx:10556 failed after select(): Connection refused
connect() to 87.170.216.xx:10556 failed after select(): No route to host
connect() to [2003:85:8f11:9a00:57b:5c4f:f5e3:xxxx]:10556 failed after select(): Permission denied
connect() to [2003:85:8f15:d400:57b:5c4f:f5e3:xxxx]:10556 failed after select(): Permission denied

This is not an on-site network issue... it's unique to GSR.

When it happens the wallet spikes up to 99% CPU for a while, then after a few minutes it 'breaks free' and is ok again.
I have masked the last part of the IP addresses from the log.

They creep forward slowly, but never come more than 14,000 blocks to current.
I don't understand how that can be... and I guess we'll never know.

Yes.. for solo mining I agree, a lot of TB is needed.
However, you can still pool mine and you still use minimal power.  In that respect you can make a profit long term.

What will the price be in 5 years?
If it was going to $5/Burst, would you mine now?

It will most certainly rise as all coins have in the coming years.

This coin is far from dead... it's just starting.
I suggest you do a little more research before spreading fud.

Just out of curiosity what's with the weird mining reward of 10.66686666?

I understand the block reward is 5.33353333.
Every so often I wind up mining a 10.666... value block.

Not that I am complaining... but why is that?

It's not really moving at all.
Coinsmarket seems to be working just fine!

This coin is a sleeping giant!

What we really need is a p2p exchange that works with all coins.  A kind of 'P2pool' exchange if you will.

Then... We would have some real value and traction.

The wallet crashed at random times while syncing.

Tbo I've experienced this with other coins so nothing new there.  Once in sync it's been solid.

Well, it does say 3% yearly.

I hope that doesn't mean the min stake age is 365 days.
I'll have a peek at the source.

Edit: The min stake age looks to be 8 hours. The max is unlimited.  Someone holding more than 8 hours should have staked something by now.  Looking through block explorer now...

Edit: I don't see anything that looks like a stake transaction in the last 100 blocks.

I take that back... something fishy is going on at YoBit.
They removed the Wallet Delayed message and the wallet shows as online... but it's off by about 10000 blocks.

It's advanced one block since earlier today.

Hot damn... that's a record.  YoBit's wallet is back in sync!

No, I wouldn't try it.
We need a new exchange.

NovaExchange is closing... yobit it, well, yobit.
Cryptopia, Poloniex or Bleutrade would be great choices.

I've seem this before with YoBit.  The status is delayed.... but it's delayed since the start of this POW phase.

Always check wallet statuses before sending coins to any Exchange.
Additionally, make sure they haven't changed their withdraw policy so you get screwed and can't withdraw your coins (Bittrex, I'm looking at you).

Sometimes the Delayed status catches up but it's been delayed for like 7 days now... not a good sign on YoBit's behalf.