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

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

Quote from: 4x13 on August 26, 2014, 07:38:41 PM

I Stopped the wallet, deleted the peers.dat and restarted and this is the error I get when I try to add node

Method not found (code -32601)

Ideas??

what app do you use to edit the peers.dat file??

Run "help", I assume it will have the RPC call listed. I cant check at the moment.

mellorbo

hero member

Activity: 620

Merit: 500

Quote from: mmfiore on August 26, 2014, 07:44:47 PM

You should stop mining until this mess is straightened out. Stay tuned to this station for updates as they happen.

ok thankyou

mmfiore

hero member

Activity: 808

Merit: 502

You should stop mining until this mess is straightened out. Stay tuned to this station for updates as they happen.

mellorbo

hero member

Activity: 620

Merit: 500

anyone know if http://xguild.net/tek/ is on the right fork? i dont want to be wasting my hash there if not

4x13

legendary

Activity: 1078

Merit: 1011

I Stopped the wallet, deleted the peers.dat and restarted and this is the error I get when I try to add node

Method not found (code -32601)

Ideas??

what app do you use to edit the peers.dat file??

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

Quote from: 4x13 on August 26, 2014, 07:28:27 PM

I am not able to use the command add node remove in my console, how do I remove the bad nodes?

I am running the Mac Wallet, so for whatever reason tekcoin.conf makes the wallet crash

Can stop wallet, delete the peers.DAT, start wallet, addnode addnode

4x13

legendary

Activity: 1078

Merit: 1011

I am not able to use the command add node remove in my console, how do I remove the bad nodes?

I am running the Mac Wallet, so for whatever reason tekcoin.conf makes the wallet crash

ryanb

legendary

Activity: 1148

Merit: 1000

Is cryptsy having deposit issues? I made a deposit and i have 70 confirmation and it is still not posted on my cryptsy account

subSTRATA

legendary

Activity: 1288

Merit: 1043

:^)

Quote from: ofeefee on August 26, 2014, 07:09:20 PM

My client synced up but wa s behind what someone posted earlier. If explorer is in sync, and checkpoint node is in sync, you sync to that.

Edit: is http://tek.blockx.info/get/chain/TekCoin correct?

No. There are at least 4 different versions of TEK blockchain right now and the only 2 nodes which are up to date in every respect - wallet version and block timestamps - are:

addnode=80.56.202.177
addnode=86.181.242.68

Node at 70.181.40.178 seems to be the only one having it's own version of blockchain and even though it seems to be up to date there are no other nodes with the same version
so it is impossible to sync to 70.181.40.178 - as said earlier, unless TEK wallet finds at least 2 nodes on same blockchain it will not sync to any node. I suggest everyone to shut
down wallet, add nodes listed above to tekcoin.conf file and then run wallet again.

Block 506732
Time 01:19:00 2014 (GMT +1)

Forget it - not gonna work, pools and PoW solo miners are way ahead of everyone else but mining on their own forks. A bit too late here for me to troubleshot others' shits, I'm out.

Alex_Koekie

newbie

Activity: 17

Merit: 0

Quote from: mmfiore on August 26, 2014, 06:49:08 PM

Can someone please post a config file my system seems to missing the file. Thanks...

A tekcoin.conf file?
Mine is like this:

listen=1
daemon=1
server=1
rpcuser=your username
rpcpassword=your password
rpcport=18514
port=8514
rpcallowip=127.0.0.1
rpcallowip=your internal network ip
rpcconnect=your internal network ip
addnode=80.56.202.177
addnode=86.181.242.68
addnode=?unsure what other nodes to use at the moment?

edit: changed the nodes to the latest posted by subSTRATA

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

My client synced up but wa s behind what someone posted earlier. If explorer is in sync, and checkpoint node is in sync, you sync to that.

Edit: is http://tek.blockx.info/get/chain/TekCoin correct?

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: subSTRATA on August 26, 2014, 06:28:06 PM

Quote from: defaced on August 26, 2014, 06:16:20 PM

Quote from: presstab on August 26, 2014, 05:44:02 PM

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.

Its not too hard to discriminate which node versions to connect to. It can and does work, not sure why it wouldn't, as I have done it.

Alex_Koekie

newbie

Activity: 17

Merit: 0

Hello to all,

Reading along in this topic for quite some time, I'm sorry to join the conversation at such a hard moment, the whole repair operation went so smooth until.......

I'm not a programmer and still learning more about how the coins work, but how do we tell which is the right fork? And if we already know, can you post a blocknumber and checksum so i can check my wallet is on the right fork?

As a solution, a new wallet rejecting old ones seems legit to me. We only have one exchange for TEK and a few important pools, so if they start to use it, the community will be forced to follow, right? If I'm wrong, continue your work, I'll continue learning.

Good luck solving the issue and greetings,
Alex_Koekie

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

Quote from: soltantgris on August 26, 2014, 06:53:52 PM

Quote from: ofeefee on August 26, 2014, 06:37:47 PM

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...

I can say Ofeefee helped us a lot when our coin forked few time ago. I would be happy if our lead dev could help you handle this situation.

Good luck guys.

Muuh respect for tek, just want to get my stake on however I can

soltantgris

hero member

Activity: 741

Merit: 500

Quote from: ofeefee on August 26, 2014, 06:37:47 PM

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...

I can say Ofeefee helped us a lot when our coin forked few time ago. I would be happy if our lead dev could help you handle this situation.

Good luck guys.

mmfiore

hero member

Activity: 808

Merit: 502

Can someone please post a config file my system seems to missing the file. Thanks...

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

I shut mine down, will check back later, once a list of good "connect" nodes are listed so we can sync, or if someone can provide a blockchain download.

Can we increment the protocol and modify so we either don't talk to the older clients, or at least don't try to sync with them?

defaced

legendary

Activity: 2184

Merit: 1011

Franko is Freedom

Quote from: subSTRATA on August 26, 2014, 06:28:06 PM

Quote from: defaced on August 26, 2014, 06:16:20 PM

Quote from: presstab on August 26, 2014, 05:44:02 PM

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.

Yea you would issue another checkpoint passed the hardfork block, make sure all the major nodes and pools are on the right one. Then release a list of addnodes on the right chain. You could also in fact make it so the newest client doesnt communicate with the old clients.

Y PPL NO UPDATE!?!?

ofeefee

legendary

Activity: 1023

Merit: 1001

Tokenize Fantasy Sports

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...

subSTRATA

legendary

Activity: 1288

Merit: 1043

:^)

Quote from: defaced on August 26, 2014, 06:16:20 PM

Quote from: presstab on August 26, 2014, 05:44:02 PM

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.

Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 226. (Read 446058 times)