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...
Just my .02 btc...
Yea it worked for ADN also.
Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 227. (Read 446058 times)
Yea it worked for ADN also.
I'm looking into it also. Mullick has pointed something out that affected CAPS forever ago.
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!
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...
Just my .02 btc...
Have you talked to Thundertoe? I'll pass that on if you haven't.
i guess someone should let cryptsy know! They need to stop deposits/withdrawals
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...
Just my .02 btc...
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
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
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
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
I am currently on block 506619 if it helps anyone.
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?
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
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)
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!
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?
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?
been stuck on block 506510 for 2 hrs now, nothing changes if i restart wallet etc. 7 active connections
Suddenly started staking again. Now up to block 506587. Last received block 10 minutes ago.
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
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.
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.
Nope, I am on block 506589. All is working great for me, no problems and everything I had has staked with no problems either.
This happened then staking stopped.
connection timeout
trying connection 93.144.219.121:8514 lastseen=533.1hrs
received block 00000000000064c6a1b3
ProcessBlock: ORPHAN BLOCK, prev=00000000000047000c49
connection timeout
received block 00000000000047000c49
ProcessBlock: ORPHAN BLOCK, prev=000000000000245bad2d
trying connection 173.206.111.158:8514 lastseen=3099.2hrs
received block 00000000000039f3f219
ProcessBlock: ORPHAN BLOCK, prev=0000000000003118cbd2
received block e39edfbd8b3c1d72ae3b
Misbehaving: 5.1.19.51:49527 (0 -> 100) DISCONNECTING
disconnecting node 5.1.19.51:49527
ERROR: ProcessBlock() : block with too little proof-of-stake
connection timeout
trying connection 171.5.250.158:8514 lastseen=38.9hrs
connection from 212.21.68.60:34073 dropped (banned)
connection timeout
trying connection 180.180.40.229:8514 lastseen=316.3hrs
connection from 101.166.8.206:56116 dropped (banned)
connection timeout
connection timeout
trying connection 93.144.219.121:8514 lastseen=533.1hrs
received block 00000000000064c6a1b3
ProcessBlock: ORPHAN BLOCK, prev=00000000000047000c49
connection timeout
received block 00000000000047000c49
ProcessBlock: ORPHAN BLOCK, prev=000000000000245bad2d
trying connection 173.206.111.158:8514 lastseen=3099.2hrs
received block 00000000000039f3f219
ProcessBlock: ORPHAN BLOCK, prev=0000000000003118cbd2
received block e39edfbd8b3c1d72ae3b
Misbehaving: 5.1.19.51:49527 (0 -> 100) DISCONNECTING
disconnecting node 5.1.19.51:49527
ERROR: ProcessBlock() : block with too little proof-of-stake
connection timeout
trying connection 171.5.250.158:8514 lastseen=38.9hrs
connection from 212.21.68.60:34073 dropped (banned)
connection timeout
trying connection 180.180.40.229:8514 lastseen=316.3hrs
connection from 101.166.8.206:56116 dropped (banned)
connection timeout
Houston we have a problem.
blocks=506585, Last received block was 52 minutes ago. Staking has been stopped now for 52 minutes. Anybody else having this problem?
blocks=506585, Last received block was 52 minutes ago. Staking has been stopped now for 52 minutes. Anybody else having this problem?
I - last download is 506512
last block 506668
but only 2 active connections
Jump to: