ok, i wait, if this solved the problems ... i do the same.
i've compiled 2 wallets on two different servers. one with blockschain and one without block chain. the one without blockchain is still downloading on 12000~ block and the one with blockchain downloaded from defaced still missing balance edit: now i rechecked again from defaced blockchain. now i'm missing even more balance. started with 300~ tek or so and now it's at 290~. it should have about 3k tek in that wallet more or less All coins you had confirmed in wallet prior to hard-fork should be there, if that is not the case (even after -rescan) it means blockchain data was changed before hard-fork point. |
|
|
|
Thats because I turned the client on last night, after the changes were pushed to the repo. Today people are updating, which means all the people who didnt update last night kept mining work blocks.
Which is why their chain is longer, but their chain doesnt calculate stake like mine does which is why mine isnt accepting their blocks and why they arnt accepting my blocks and why im at 506608 and they are at a higher block count.
We could disregard my chain and sync to the current work chain but as soon as one person stakes, the first person to stake will be a fork from the people who havnt upgraded yet. And the argument starts alllllllll over again.
"do we orphan the workers who havnt updated, or do we delete our staked chain and sync to their longer chain"
and then the loop happens again! and again and again and again until someone finally says "this is the chain we are using"
The workers are going to want to keep their easily mined work blocks, the stakers are trying to say, enough is enough lets get stake working again, and everyone else is confused. I vote we paper rock scissors the answer.
Unless you orphan those who have not upgraded or are on any other than legit longest blockchain (the most work done) than it is failed hard-fork. The most work done on the set of rules they are working on, as soon as the rules change their longest chain doesnt matter. Example. Is the tekblockchain dependent on the Bitcoin blockchain? No? Why? Because they are different rule sets. Up until the hardfork blockchain A and blockchain B WERE the same rules, from that point forward they were not. People dont have to use blockchain b, but the incentive to do so is because stake (the reason people use tek) works again. Blockchain A has rules that break stake, work is fine though. A != B They look similar. Smell similar. Even probably taste similar but they are not the same. Nodes 2.0 are not complaining when our swarm stakes PoS blocks. All other nodes disconnect except those still syncing but currently under hard-fork point and nodes 2.0 so now you tell me how is that possible if rules were changed with 2.0 |
|
|
|
Thats because I turned the client on last night, after the changes were pushed to the repo. Today people are updating, which means all the people who didnt update last night kept mining work blocks.
Which is why their chain is longer, but their chain doesnt calculate stake like mine does which is why mine isnt accepting their blocks and why they arnt accepting my blocks and why im at 506608 and they are at a higher block count.
We could disregard my chain and sync to the current work chain but as soon as one person stakes, the first person to stake will be a fork from the people who havnt upgraded yet. And the argument starts alllllllll over again.
"do we orphan the workers who havnt updated, or do we delete our staked chain and sync to their longer chain"
and then the loop happens again! and again and again and again until someone finally says "this is the chain we are using"
The workers are going to want to keep their easily mined work blocks, the stakers are trying to say, enough is enough lets get stake working again, and everyone else is confused. I vote we paper rock scissors the answer.
Unless you orphan those who have not upgraded or are on any other than legit longest blockchain (the most work done) than it is failed hard-fork. Block height 507116 Time 17:47:37 (+1 GMT) "proof-of-work" : 250768.75421742, "proof-of-stake" : 0.00006103, Staking or mining within this swarm does not cause IP ban So how come few 1.1 nodes are working properly and others are all over the place? Also, how it is possible nodes on 2.0 are accepting work from this swarm but still refuse to sync up to our block height? 17:56:08  getpeerinfo 17:56:08  [ { "addr" : "70.181.40.178:8514", "services" : "00000001", "lastsend" : 1409154792, "lastrecv" : 1409154855, "conntime" : 1409150731, "version" : 60006, "subver" : "/tekcoin:1.1.0/", "inbound" : false, "releasetime" : 0, "startingheight" : 507110, "banscore" : 0 }, { "addr" : "110.174.169.110:8514", <--- still syncing, unaware of any issues "services" : "00000001", "lastsend" : 1409154811, "lastrecv" : 1409154811, "conntime" : 1409150894, "version" : 60006, "subver" : "/tekcoin:1.1.0/", "inbound" : false, "releasetime" : 0, "startingheight" : 245698, "banscore" : 0 }, { "addr" : "74.196.63.95:8514", "services" : "00000001", "lastsend" : 1409154855, "lastrecv" : 1409154792, "conntime" : 1409151212, "version" : 60007, "subver" : "/tekcoin:2.0.0/", "inbound" : false, "releasetime" : 0, "startingheight" : 506608, "banscore" : 0 }, { "addr" : "62.116.254.204:8514", <--- still syncing, unaware of any issues "services" : "00000001", "lastsend" : 1409154792, "lastrecv" : 1409154528, "conntime" : 1409154527, "version" : 60007, "subver" : "/tekcoin:2.0.0/", "inbound" : false, "releasetime" : 0, "startingheight" : 47724, "banscore" : 0 } ] |
|
|
|
|
No thanks, there must exist a valid 1.1 version of blockchain, just in case your wallet causes major issues else you will have to rollback everyone back to hard-fork point.
|
|
|
|
version 1.9 will create forks everytime someone stakes due to an overlook in the code. same thing used to happen with bottlecaps.
Versions 1.2 and 1.9.1 are abandoned wallets which were supposed to end up on their own fork. Version v1.1 is wallet that is supposed to continue working after hard-fork but it seems it is accepting PoW from all wallet versions so there are at least 3 versions of v1.1 blockchains: 1. One where PoW from 1.2 and 1.9.1 miners was erroneously accepted, PoS blocks by 1.1 will cause 1.1 node to end up banned. 2. One where PoW from 1.2 and 1.9.1 miners was not accepted but PoS blocks will be rejected anyway because nodes are on very different block heights (based on number of PoS blocks each of them staked for themselves). 3. One where everything is perfectly fine, wallet version 1.1 PoW mining works and PoS staking does not cause forking - even nodes you mentioned are not complaining on submitted work which means it is compatible with your version of blockchain but here is the kicker = your blockchain is shorter (less work done) so please upgrade to our version. Yet another version of partially tested wallet in a situation where half of network didn't even switched to 1.1 is horrible idea. Say I take your suggestion, delete my chain, restart my client sync to yours and mint a couple stake blocks. We will STILL be in the exact same situation we are now, because my client and anyone on my client will go off on their own fork and the pow pools will STILL be mining on their chain. At some point in time blocks are going to be orphaned because the proof of workers wont stop working. Either update and sync with the people staking or continue the work chain, sooner or later everyone will have to choose one and what im not doing is all this work over again. The great thing about consensus is the choice is ultimately yours. Yes, I can opt for not using one more potentialy horrible version of wallet and I will do so. Once a week passes without your version having issues I will switch - not before.  |
|
|
|
version 1.9 will create forks everytime someone stakes due to an overlook in the code. same thing used to happen with bottlecaps.
Versions 1.2 and 1.9.1 are abandoned wallets which were supposed to end up on their own fork. Version v1.1 is wallet that is supposed to continue working after hard-fork but it seems it is accepting PoW from all wallet versions so there are at least 3 versions of v1.1 blockchains: 1. One where PoW from 1.2 and 1.9.1 miners was erroneously accepted, PoS blocks by 1.1 will cause 1.1 node to end up banned. 2. One where PoW from 1.2 and 1.9.1 miners was not accepted but PoS blocks will be rejected anyway because nodes are on very different block heights (based on number of PoS blocks each of them staked for themselves). 3. One where everything is perfectly fine, wallet version 1.1 PoW mining works and PoS staking does not cause forking - even nodes you mentioned are not complaining on submitted work which means it is compatible with your version of blockchain but here is the kicker = your blockchain is shorter (less work done) so please "upgrade" to our version. Yet another version of wallet - partially tested - in a situation where half of network didn't even switched to 1.1 is horrible idea. |
|
|
|
|
listen=0
connect=70.181.40.178
connect=89.201.186.50
It will connect to just those two nodes and also reject any incoming connections. Are you sure you used connect instead of addnode?
|
|
|
|
Ok. I'm redownloading the block chain with wallet locked to prevent PoS... Also with a good backup of my wallet before the fork.
You can actualy PoS a block or few just to make sure you are connected to just legit nodes - all others will ban you (disconnect from your node) as soon as you stake a block. But try to not stake too many blocks in sequence because due to current low PoS difficulty and your big staking weight you might flood other legit nodes (you can think of it as super-instamining) and end up orphaned or even banned! |
|
|
|
BREAKING NEWS!
Node mentioned few times yesterday seems to be the only one that is actualy using newest wallet and PoW mining (or connected to legit PoW miner) and accepting PoS stakes
only from legit wallets v1.1 so here comes lengthy procedure how to setup everything:
1. Shutdown your TEK wallet.
2. Go to TEK data directory and delete everything except wallet.dat file - if you have pre-hard-fork backup of blockchain use it to speed up syncing!
3. Add following lines in your tekcoin.conf file:
listen=0
connect=70.181.40.178
connect=89.201.186.50
4. Restart your modem so you get fresh IP - this is a must because your current IP might be blacklisted for 24 hours by two nodes listed above, if so you will not be able to connect.
5. Start your TEK wallet and let it sync. Once done check info using getdifficulty command, right now it returns:
"proof-of-work" : 250768.75421742,
"proof-of-stake" : 0.00006201,
Current block height is 507092
6. Only after you have fully synced switch to solo mining (if you have SHA miners).
7. Do not enable PoS staking yet!!! I will update procedure only after many of you confirm you have successfuly synced to nodes mentioned above.
All TEK pools are on wrong forks! Do not mine anywhere else except solo (once you finished syncing as explained above). All other forks will ban your IP for 24 hours because of wrong PoW or wrong PoS blocks even if you are using wallet v1.1 http://tek.blockx.info/get/chain/TekCoin is on wrong fork as well. Even if you manage to sync to just v1.1 nodes connected to it ( http://tek.blockx.info/connected-nodes) they will reject your legit PoS blocks and ban your IP for 24 hours. "proof-of-work" : 250768.75421742, "proof-of-stake" : 0.00006103, Current block height is 507103 More PoW miners needed, stop mining at TEK pools! |
|
|
|
I'm at IP 82.171.127.104 , don't know if it does support incoming. How do i check?
If needed I know how to set up a portforward, but don't know if that is what you mean.
Your node is not reachable so it is not accepting incoming connections - that or it already banned my IP  Can you post the config file? Or do you only need those 3 lines?
If it's supposed to look like this then I'm fine:
listen=0
server=1
daemon=1
rpcuser=you
rpcpassword=pass
rpcallowip=127.0.0.1
rpcallowip=192.168.*.*
Port=8514
RPCPort=18514
connect=70.181.40.178
connect=89.201.186.50
If not... I'll edit to delete this.
That will work. |
|
|
|
@subSTRATA Great Work!!! I followed the instructions and are now synced with 70.181.40.178. No other nodes connected yet. I'm at block 507098, blockhash is 32ca21806c77de224765b62b0a6a8639b53677c20d41b7c563fa083878190ca0 "proof-of-work" : 250768.75421742, "proof-of-stake" : 0.00006144, I did put a copy of the blockchain until the day before the fork online here (glad i remembered to backup for once), it's the blk0001.dat file, this is the one used for bootstrap, right?: https://mega.co.nz/#!bx1zQQhD!HOlas1z4_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXEAwaiting further instructions! Can your node accept incoming connections? If yes please post your IP so I can add it to list. What we must create here is a swarm of legit wallets which are using v1.1 and not connect to any other nodes until new wallet is released. All nodes - including v1.1 - which are not connected to swarm will accept PoW blocks but reject PoS blocks, a major issue. |
|
|
|
BREAKING NEWS!
Node mentioned few times yesterday seems to be the only one that is actualy using newest wallet and PoW mining (or connected to legit PoW miner) and accepting PoS stakes
only from legit wallets v1.1 so here comes lengthy procedure how to setup everything:
1. Shutdown your TEK wallet.
2. Go to TEK data directory and delete everything except wallet.dat file - if you have pre-hard-fork backup of blockchain use it to speed up syncing!
3. Add following lines in your tekcoin.conf file:
listen=0
connect=70.181.40.178
connect=89.201.186.50
4. Restart your modem so you get fresh IP - this is a must because your current IP might be blacklisted for 24 hours by two nodes listed above, if so you will not be able to connect.
5. Start your TEK wallet and let it sync. Once done check info using getdifficulty command, right now it returns:
"proof-of-work" : 250768.75421742,
"proof-of-stake" : 0.00006201,
Current block height is 507092
6. Only after you have fully synced switch to solo mining (if you have SHA miners).
7. Do not enable PoS staking yet!!! I will update procedure only after many of you confirm you have successfuly synced to nodes mentioned above.
All TEK pools are on wrong forks! Do not mine anywhere else except solo (once you finished syncing as explained above). All other forks will ban your IP for 24 hours because of wrong PoW or wrong PoS blocks even if you are using wallet v1.1 http://tek.blockx.info/get/chain/TekCoin is on wrong fork as well. Even if you manage to sync to just v1.1 nodes connected to it ( http://tek.blockx.info/connected-nodes) they will reject your legit PoS blocks and ban your IP for 24 hours. |
|
|
|
|
BREAKING NEWS!
Node mentioned few times yesterday seems to be the only one that is actualy using newest wallet and PoW mining (or connected to legit PoW miner) and accepting PoS stakes
only from legit wallets v1.1 so here comes lengthy procedure how to setup everything:
1. Shutdown your TEK wallet.
2. Go to TEK data directory and delete everything except wallet.dat file - if you have pre-hard-fork backup of blockchain use it to speed up syncing!
3. Add following lines in your tekcoin.conf file:
listen=0
connect=70.181.40.178
connect=89.201.186.50
4. Restart your modem so you get fresh IP - this is a must because your current IP might be blacklisted for 24 hours by two nodes listed above, if so you will not be able to connect.
5. Start your TEK wallet and let it sync. Once done check info using getdifficulty command, right now it returns:
"proof-of-work" : 250768.75421742,
"proof-of-stake" : 0.00006201,
Current block height is 507092
6. Only after you have fully synced switch to solo mining (if you have SHA miners).
7. Do not enable PoS staking yet!!! I will update procedure only after many of you confirm you have successfuly synced to nodes mentioned above.
|
|
|
|
I have downloaded the latest wallet, started it yesterday and 3 large blocks staked in a row. I thought it is working, but suddenly the blockchain stucked and now 10k TEK stay unconfirmed. So yesterday i shut down the wallet and today im reading this bad situation here.. are these Coins gone now?
Or is there a way to recover? Does an old wallet.dat help?
Any coins generated or moved before hard-fork will not be lost. All coins generated after hard-fork will be lost - stop PoW mining and PoS staking and moving coins around until new wallet is released! |
|
|
|
What happened here is basically a fireworks scenario - there was a rocket (old blockchain) and then at the time of hard-fork it exploded resulting in countless different blockchains. Gentleman, we have witnessed digital Big Bang!  I'm not able to help the programming as well, but I do have a backup of the blockchain the day before the fork(s) Is it of any use to upload it so people can bootstrap and don't have to resync using the network? No use for it because nodes will sync to random other nodes and inevitably end up on some of countless forks - legit or not - and start kicking out any nodes not complying with their version of blockchain. Even v1.1 nodes are "killing" each other and when you add v1.2 and v1.9.1 in the mix it is a real mess. |
|
|
|
Wallet that has built-in filter to kick all nodes on 1.2 and 1.9.1 is prerequisite for everything else. PoS staking should be enabled only after new nodes v1.1 have made their own
legit swarms (connected only to other legit nodes) and PoS staking should start with high difficulty value, not minimum one!
--------hardfork--------nodes 1.2 and 1.9.1
|
|-------------nodes 1.1----------PoS staking starts here with high difficulty value (0.1 to be safe from major orphaning)
If you are PoW mining (solo or pool) right now stop. If you are PoS staking right now stop as well. If you are running local wallet just shut it down, this situation can
not be fixed using any of existing (public) wallets. Even an upgrade to v1.1 and complete resync (delete everything except wallet.dat file) will not help. Even the latest
wallet is built using outdated code, -reindex command does not work and wallet is unable to self-reorganize blockchain after it accepted certain number of blocks from
other nodes.
This sounds like what Defaced said to me. As noted, I'm not a programmer, so I might be off base. All in all, due to everything posted earlier it is impossible for network to reach majority consensus right now. |
|
|
|
|
Wallet that has built-in filter to kick all nodes on 1.2 and 1.9.1 is prerequisite for everything else. PoS staking should be enabled only after new nodes v1.1 have made their own
legit swarms (connected only to other legit nodes) and PoS staking should start with high difficulty value, not minimum one!
--------hardfork--------nodes 1.2 and 1.9.1
|
|-------------nodes 1.1----------PoS staking starts here with high difficulty value (0.1 to be safe from major orphaning)
If you are PoW mining (solo or pool) right now stop. If you are PoS staking right now stop as well. If you are running local wallet just shut it down, this situation can
not be fixed using any of existing (public) wallets. Even an upgrade to v1.1 and complete resync (delete everything except wallet.dat file) will not help. Even the latest
wallet is built using outdated code, -reindex command does not work and wallet is unable to self-reorganize blockchain after it accepted certain number of blocks from
other nodes.
|
|
|
|
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
Nodes using 1.2 and 1.9.1 are pre-hard-fork wallets, they are on abandoned fork. |
|
|
|
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! |
|
|
|
|
Show Posts
