Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 224. (Read 446058 times)
I'dont change the source before there is not a officiel statement. i'dont want lost all coins ...
That is supposed to be the most recent version
i'think here is a big scam with different sources, it should be: https://github.com/maxxine/TEK.git like it's say in page number one here.
or not???
or not???
Wow, didn't expect this to happen, just thought it may occur. Teething issues on the update 
. Let us all keep calm and level headed, this is the time to stay cool and not do anything irrational. We are all aware of the issue and the devs too, so a fix is coming. Not the first time a scare has come to a crypto nor Tek, it won't be the last either.
Best thing is not to open the wallet and not do any transactions. Thats what I am doing until clarity comes to the situation and issues from the hardfork are resolved.
. Let us all keep calm and level headed, this is the time to stay cool and not do anything irrational. We are all aware of the issue and the devs too, so a fix is coming. Not the first time a scare has come to a crypto nor Tek, it won't be the last either. Best thing is not to open the wallet and not do any transactions. Thats what I am doing until clarity comes to the situation and issues from the hardfork are resolved.
when you guys think you have a fix please post a link to the compiled wallet client and please remember to update the version number so we know we are on the correct version. Thanks for your help.
My wallet is a mess i had some stake and then sent some coins to cryptsy everything confirmed but nothing ever arrived there so i guess i was on fork? then i fixed my wallet and now the stakes and what i sent are all showing as 0 confirmations and the coins are not in my balance.
My Wallet is out of sync. Why?
So I have approx 900 coins missing in this debacle...
I finally have a good chain (hopefully) but every single stake says generated but not accepted.
WTF?
Edit:
Nope... Apparently I have the dogshit blockchain after rebuilding from scratch...

[
{
"addr" : "95.165.128.192:8514",
"services" : "00000001",
"lastsend" : 1409121435,
"lastrecv" : 1409121435,
"conntime" : 1409108587,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506602,
"banscore" : 0
},
{
"addr" : "76.90.47.6:8514",
"services" : "00000001",
"lastsend" : 1409121436,
"lastrecv" : 1409121398,
"conntime" : 1409120766,
"version" : 60006,
"subver" : "/tekcoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 431025,
"banscore" : 0
}
]
I finally have a good chain (hopefully) but every single stake says generated but not accepted.
WTF?
Edit:
Nope... Apparently I have the dogshit blockchain after rebuilding from scratch...

[
{
"addr" : "95.165.128.192:8514",
"services" : "00000001",
"lastsend" : 1409121435,
"lastrecv" : 1409121435,
"conntime" : 1409108587,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506602,
"banscore" : 0
},
{
"addr" : "76.90.47.6:8514",
"services" : "00000001",
"lastsend" : 1409121436,
"lastrecv" : 1409121398,
"conntime" : 1409120766,
"version" : 60006,
"subver" : "/tekcoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 431025,
"banscore" : 0
}
]
i'have today in the morning made a git pull. but i have the problem, payouts dossent receive in the target walled. i'was try with crypsy but still nothing receive there.
version" : "v2.0.1.0-gf96a5a-TEK"
Source: https://github.com/maxxine/TEK.git
root@ppl:~# cd TEK/
root@ppl:~/TEK# git pull
Already up-to-date.
root@ppl:~/TEK# date
Mi 27. Aug 07:51:41 CEST 2014
root@ppl:~/TEK#
QUESTION: what is the right official source?
Coinwarez provide: https://github.com/stumpyfr/tekcoin.git
Tekcoin.org provide nothing more??
What is: ?">https://github.com/chrisfranko/TEK??
So what is the official Tekcoin Supported Sources??
And in the Past, before all this updates i'was send correct payouts, for example to crypsy.
So, what is happen?
http://poolparty.port-x.de
version" : "v2.0.1.0-gf96a5a-TEK"
Source: https://github.com/maxxine/TEK.git
root@ppl:~# cd TEK/
root@ppl:~/TEK# git pull
Already up-to-date.
root@ppl:~/TEK# date
Mi 27. Aug 07:51:41 CEST 2014
root@ppl:~/TEK#
QUESTION: what is the right official source?
Coinwarez provide: https://github.com/stumpyfr/tekcoin.git
Tekcoin.org provide nothing more
??What is: ?">https://github.com/chrisfranko/TEK?
?So what is the official Tekcoin Supported Sources?
?And in the Past, before all this updates i'was send correct payouts, for example to crypsy.
So, what is happen?
http://poolparty.port-x.de
do the devs have a DNS translation or some way to contact the bad nodes to tell them to shutdown and upgrade??
I am guessing that ver. 60006 is the Bad block chain version?? I am receiving nodes from somewhere (guessing DNS) with subversion 1.1.0, 1.2.0 and 1.9.1... Where did 1.9.1 come from??
If someone knows how to contact the nodes, I can post some of the IP's here or help out if needed
I am guessing that ver. 60006 is the Bad block chain version?? I am receiving nodes from somewhere (guessing DNS) with subversion 1.1.0, 1.2.0 and 1.9.1... Where did 1.9.1 come from??
If someone knows how to contact the nodes, I can post some of the IP's here or help out if needed
All the pool are up to date?? Dev can you check this plz. Thanks! 
As far as I know, a rescan will perform a rescan of your chain for missing transactions to fix your wallet as such.
Maybe we should consider a roll back in worst case scenario to last known correct height.
EDIT :
Re-index only fixes a corrupt index of your chain on your hd, does not fix the fact you ended up on the wrong one.
For fixing the fork only a new download would help, to speed up things users should download a bootstrap file.
Maybe we should consider a roll back in worst case scenario to last known correct height.
EDIT :
Re-index only fixes a corrupt index of your chain on your hd, does not fix the fact you ended up on the wrong one.
For fixing the fork only a new download would help, to speed up things users should download a bootstrap file.
Node at 70.181.40.178 was reporting the highest block height and wallet v1.1 but I can not connect to it anymore. That node seems to be connected to both
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
you can resync with --rescan and be fine. add my node and try my build
Rescan does not help because I now have my own version of blockchain and wallet can not undo changes made no matter how many other nodes I connect to even if they are on
the exact same block height and using v1.1 - it can not self-reorg after certain number of blocks were accepted. To connect to your node does not help neither because wallet will
not sync to your data unless there is at least one other node on the same blockchain.
I'll have to -reindex tommorow morning, off to bed finaly!
Damn I hate it being on the wrong fork !
(one large step back and watch for the dust to settle) ....
Jason
Jason
And there is also this guy, it seems he is on yet another legit fork - highest block height so far!
"addr" : "108.61.10.90:8514",
"services" : "00000001",
"lastsend" : 1409102093,
"lastrecv" : 1409102093,
"conntime" : 1409102066,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506818,
"banscore" : 0
"addr" : "108.61.10.90:8514",
"services" : "00000001",
"lastsend" : 1409102093,
"lastrecv" : 1409102093,
"conntime" : 1409102066,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506818,
"banscore" : 0
[img]
Something the devs have to sort out, hopefully PressTab can help us out.
Node at 70.181.40.178 was reporting the highest block height and wallet v1.1 but I can not connect to it anymore. That node seems to be connected to both
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
I am not sure if the one with the highest block count is actually the right one.http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
Something the devs have to sort out, hopefully PressTab can help us out.
Node at 70.181.40.178 was reporting the highest block height and wallet v1.1 but I can not connect to it anymore. That node seems to be connected to both
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
http://tekcoin.miners-point.com/index.php?page=statistics&action=pool and http://tek_blockcrawler.miners-point.com/block_crawler.php but I can not make it so that my wallet
connects there. And it is stucked because I turned on PoS mining and wallet refuses to rollback to any other block height. And I have no time for reindex now so it is funny really.
Problem with guy solo mining is that once he connects to other legit nodes he will orphan everyone.
you can resync with --rescan and be fine. add my node and try my build
Damn !
Sorry for sounding harsh here, but how on earth could you release a client without proper fail-save build in !!
No checkpoints ??
No rejection of old clients ??
Again sorry for my harsh words on this, but this is BIG time stupid if you consider how many coins have screwed up in the past exactly by not implementing these fail-save tricks !
Do NOT use in your config addnode= use connect= and make sure you have listen=0
This will force the wallet only to connect to given/known trusted "seeders".
============
listen=1
connect=
connect=
============
Sorry for sounding harsh here, but how on earth could you release a client without proper fail-save build in !!
No checkpoints ??
No rejection of old clients ??
Again sorry for my harsh words on this, but this is BIG time stupid if you consider how many coins have screwed up in the past exactly by not implementing these fail-save tricks !
Do NOT use in your config addnode=
This will force the wallet only to connect to given/known trusted "seeders".
============
listen=1
connect=
connect=
============
Its going to be okay, did no one tell you this was the cutting edge, lol.
the one I just did, is for us to test to see if we can all get on a chain with out forking it.
this commit bumps the protocol version also so if it turns out to work like we want it too I can add a checkpoint and enforce the min protocol to be atleast this client or greater.
this commit bumps the protocol version also so if it turns out to work like we want it too I can add a checkpoint and enforce the min protocol to be atleast this client or greater.
Jump to: