[TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico

[mafort1469]

Nope, I am on block 506589. All is working great for me, no problems and everything I had has staked with no problems either.

[vancefox]

Yeah I'm stuck on 6555 right now... 2 active connections.

All is well, the wallet is updating... this is probably just due to the staking restart... too much going on right now.  I'm guessing it'll calm down by tomorrow.

Edit:  Seems like I'm in the same boat with not actually updating... just saying it's x blocks behind.

[mmfiore]

I stopped and restarted the wallet. The wallet could see that there was other blocks to load. About 73 more blocks but it could not load them. So I am still stuck at block 506585

[mmfiore]

Suddenly started staking again. Now up to block 506587. Last received block 10 minutes ago.

[holepunch]

been stuck on block 506510  for 2 hrs now, nothing changes if i restart wallet etc. 7 active connections

[jdhatch]

Does a payment to yourself require any confirmations??

I sent myself a large number of coins about 15 mins ago and it is in my coin control but no confirms.

I am afraid if it generates no confirms it will not stake in 30 days.

Thoughts?

[Dexpla]

i think its suck, all mine have staked, but my 1st staked block has  only 19 confirmations for about an hour, looks like nothing is confirming at the moment, Probably very busy and may take awhile to clear the backlog!

[holepunch]

rich list also stuck at block 506508, network difficulty has also dropped by approx 2/3rds, i guess 2/3rds of the network didn't prepare for the fork (as usual)

[Biomech]

Does a payment to yourself require any confirmations??

I sent myself a large number of coins about 15 mins ago and it is in my coin control but no confirms.

I am afraid if it generates no confirms it will not stake in 30 days.

Thoughts?

If it went through, it'll confirm. And yes, it does need to confirm. But if it fails, it'll just revert to what it was, and you'll need to do it again.

On my own wallet, I somehow got on a fork. I'm resyncing, dammit. Takes forever

[mafort1469]

I am currently on block 506619 if it helps anyone.

[subSTRATA]

What a mess! Situation right now is as follows:

1. Majority of full nodes are still using all wallet versions.
2. TEK pools seems to be isolated from each other thus generating blocks only for themselves.
3. It seems that wallet will not sync to just one node that reports highest block count, it waits for at least two nodes to report same block height which is impossible right now.
4. Other full nodes using newest wallet version are stuck or "clueless" because 1. and 2. and 3.

Legit node with the most blocks seems to be one at 70.181.40.178 so add line below to your tekcoin.conf file and restart wallet!

addnode=70.181.40.178

[Biomech]

What a mess! Situation right now is as follows:

1. Majority of full nodes are still using all wallet versions.
2. TEK pools seems to be isolated from each other thus generating blocks only for themselves.
3. It seems that wallet will not sync to just one node that reports highest block count, it waits for at least two nodes to report same block height which is impossible right now.
4. Other full nodes using newest wallet version are stuck or "clueless" because 1. and 2. and 3.

Legit node with the most blocks seems to be one at 70.181.40.178 so add line below to your tekcoin.conf file and restart wallet!

addnode=70.181.40.178

Thanks, I'll do that immediately. The fix worked fine in testing, but I think we failed to account for volume

[presstab]

I would recommend finding the correct fork, issuing a checkpoint past the hard fork, and then reissuing the wallet. This was my strategy with HYP, and it worked well.

Just my .02 btc...

[holepunch]

i guess someone should let cryptsy know! They need to stop deposits/withdrawals

[Biomech]

I would recommend finding the correct fork, issuing a checkpoint past the hard fork, and then reissuing the wallet. This was my strategy with HYP, and it worked well.

Just my .02 btc...

Have you talked to Thundertoe? I'll pass that on if you haven't.

[subSTRATA]

All TEK pools should shutdown immidiately and let legit full nodes which are PoS staking overtake network. If you are PoW mining stop it right now!

[defaced]

I'm looking into it also. Mullick has pointed something out that affected CAPS forever ago.

[defaced]

I would recommend finding the correct fork, issuing a checkpoint past the hard fork, and then reissuing the wallet. This was my strategy with HYP, and it worked well.

Just my .02 btc...

Yea it worked for ADN also.

[subSTRATA]

I would recommend finding the correct fork, issuing a checkpoint past the hard fork, and then reissuing the wallet. This was my strategy with HYP, and it worked well.

Just my .02 btc...

Yea it worked for ADN also.

It can not work if majority of network are "cancer" nodes which is the case here. Unless there is filter for all older versions of TEK client there is very little chance legit nodes will
be able to connect to other legit nodes - especially important with pools - but once they manage to do that there will be major orphaning of others' blocks. I'm not sure how many
blocks in past can TEK network reorganize but it is almost a must to stop being polite to morons who are still using abandoned wallets and kick them out from network until they
finaly upgrade. Flappycoin did that successfuly, check it's source-code.

This is a perfect example of Hal-Finey (or it is Sybil?) attack, where adversary can cause major problems by intentionaly creating and connecting many "cancer" nodes to network.
That is the reason why Bitcoiners are afraid of continualy dropping number of legit full nodes on Bitcoin network. If legit nodes can not find other legit nodes it is basically game over.

[ofeefee]

Does someone have a list of current nodes on right fork?  And I see the checkpoint key was changed in fix, so that will only provide checkpointing to new clients?  But new client still can sync to old client "static const int NOBLKS_VERSION_END = 60004;"  (i may have missed if you put another check in for this, still new at it all)

And if someone has the old alert key, can issue an alert to the old clients so everyone can update?  However, like FLT when it forked, we had the issue, and still do where people just don't update for whatever reason for months!

And can someone put up a blockchain file, so we can download it quickly?  dropbox? or another site?  Preferably from a dev...