Bitcoin Forum
October 16, 2017, 10:41:32 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 316 »
  Print  
Author Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico  (Read 429649 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 10:37:47 PM
 #1721

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...
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
defaced
Legendary
*
Offline Offline

Activity: 1596


Franko is the Future.


View Profile WWW
August 26, 2014, 10:39:56 PM
 #1722

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!?!?

Fortune favors the brave. - Publius Terence
Fair, Scarce, and Fast. Meet Franko
Franko ★  Expanse To The Moon NewsJoin the Expanse SlackHow to get free bitcoins
ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 10:44:42 PM
 #1723

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?
mmfiore
Hero Member
*****
Offline Offline

Activity: 677



View Profile
August 26, 2014, 10:49:08 PM
 #1724

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

       ▄▄▀▀▀▀▀▀▀▀▀▄▄
    ▄█▀ ▄▄██▀▀▀██▄▄ ▀█▄
  ▄█▀ ▄███▀     ▀███▄ ▀█▄
 ▄▀ ▄███▀   ▄█▄   ▀███▄ ▀▄
▄█ ███▀   ▄█▀████▄  ▀███ █▄
█ ▄██▄   ▀█▄▄  ▀███▄▄███▄ █
█ ██████▄   ▀█▄   ▀██████ █
█ ▀███▀▀███▄  ▀▀█▄   ▀██▀ █

▀█ ███▄  ▀████▄█▀   ▄███ █▀

 ▀▄ ▀███▄   ▀█▀   ▄███▀ ▄▀

  ▀█▄ ▀███▄     ▄███▀ ▄█▀

    ▀█▄ ▀▀██▄▄▄██▀▀ ▄█▀

       ▀▀▄▄▄▄▄▄▄▄▄▀▀
SLVR█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
[ WHITEPAPER ]
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
[ TECH  PAPER ]
▄█████████████████████████▄
██████████████    █████████
█████    █████    ▀▀▀▀█████
█████    ▀▀▀▀         █████
██▀▀▀              ▄▄▄█████
██        ▄▄▄███    ███████
██▄▄▄▄█    █████    █▀▀▀▀██
███████    ██▀▀▀         ██
█████▀▀▀              ▄▄▄██
████         ▄▄▄██    █████
█████▄▄▄▄    █████    █████
█████████    ██████████████
▀█████████████████████████▀
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
!
soltantgris
Hero Member
*****
Offline Offline

Activity: 619


Connecting the dots


View Profile
August 26, 2014, 10:53:52 PM
 #1725

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.

ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 11:00:04 PM
 #1726

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 Smiley
Alex_Koekie
Newbie
*
Offline Offline

Activity: 17


View Profile
August 26, 2014, 11:03:28 PM
 #1727

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
presstab
Legendary
*
Online Online

Activity: 1288


Pivx Core Developer - HyperStake Founder


View Profile
August 26, 2014, 11:07:48 PM
 #1728

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.

presstab's Block Explorer Service | Only $10/mo for most coins! | Richlist w/ Address Claim | Market Cap Charts | Stake Weight Tracking | PoS % Rate Tracking
PIVX - Private Instant Verified Tx | HyperStake - Fun & Easy High Reward Staking
ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 11:09:20 PM
 #1729

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?
Alex_Koekie
Newbie
*
Offline Offline

Activity: 17


View Profile
August 26, 2014, 11:13:43 PM
 #1730

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
subSTRATA
Legendary
*
Offline Offline

Activity: 938


Enjin Coin - Smart Cryptocurrency for Gaming.


View Profile
August 26, 2014, 11:14:02 PM
 #1731

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.

ryanb
Legendary
*
Offline Offline

Activity: 1134



View Profile
August 26, 2014, 11:22:36 PM
 #1732

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

https://bitcoinfundingteam.com/ref/SatoshiTeam
turn 0.1 BTC to 80BTC week after week!!!
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1050


View Profile WWW
August 26, 2014, 11:28:27 PM
 #1733

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

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 11:32:54 PM
 #1734

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
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1050


View Profile WWW
August 26, 2014, 11:38:41 PM
 #1735

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

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
mellorbo
Hero Member
*****
Offline Offline

Activity: 579



View Profile
August 26, 2014, 11:42:47 PM
 #1736

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

mmfiore
Hero Member
*****
Offline Offline

Activity: 677



View Profile
August 26, 2014, 11:44:47 PM
 #1737

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

       ▄▄▀▀▀▀▀▀▀▀▀▄▄
    ▄█▀ ▄▄██▀▀▀██▄▄ ▀█▄
  ▄█▀ ▄███▀     ▀███▄ ▀█▄
 ▄▀ ▄███▀   ▄█▄   ▀███▄ ▀▄
▄█ ███▀   ▄█▀████▄  ▀███ █▄
█ ▄██▄   ▀█▄▄  ▀███▄▄███▄ █
█ ██████▄   ▀█▄   ▀██████ █
█ ▀███▀▀███▄  ▀▀█▄   ▀██▀ █

▀█ ███▄  ▀████▄█▀   ▄███ █▀

 ▀▄ ▀███▄   ▀█▀   ▄███▀ ▄▀

  ▀█▄ ▀███▄     ▄███▀ ▄█▀

    ▀█▄ ▀▀██▄▄▄██▀▀ ▄█▀

       ▀▀▄▄▄▄▄▄▄▄▄▀▀
SLVR█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
[ WHITEPAPER ]
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
[ TECH  PAPER ]
▄█████████████████████████▄
██████████████    █████████
█████    █████    ▀▀▀▀█████
█████    ▀▀▀▀         █████
██▀▀▀              ▄▄▄█████
██        ▄▄▄███    ███████
██▄▄▄▄█    █████    █▀▀▀▀██
███████    ██▀▀▀         ██
█████▀▀▀              ▄▄▄██
████         ▄▄▄██    █████
█████▄▄▄▄    █████    █████
█████████    ██████████████
▀█████████████████████████▀
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
!
mellorbo
Hero Member
*****
Offline Offline

Activity: 579



View Profile
August 26, 2014, 11:45:08 PM
 #1738

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

ofeefee
Hero Member
*****
Offline Offline

Activity: 830


View Profile
August 26, 2014, 11:48:21 PM
 #1739

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.



mmfiore
Hero Member
*****
Offline Offline

Activity: 677



View Profile
August 26, 2014, 11:51:11 PM
 #1740

how about trying to delete the peers.dat and modifying the tekcoin.conf file. Just add the nodes you want and remove the old nodes then restart the wallet.

       ▄▄▀▀▀▀▀▀▀▀▀▄▄
    ▄█▀ ▄▄██▀▀▀██▄▄ ▀█▄
  ▄█▀ ▄███▀     ▀███▄ ▀█▄
 ▄▀ ▄███▀   ▄█▄   ▀███▄ ▀▄
▄█ ███▀   ▄█▀████▄  ▀███ █▄
█ ▄██▄   ▀█▄▄  ▀███▄▄███▄ █
█ ██████▄   ▀█▄   ▀██████ █
█ ▀███▀▀███▄  ▀▀█▄   ▀██▀ █

▀█ ███▄  ▀████▄█▀   ▄███ █▀

 ▀▄ ▀███▄   ▀█▀   ▄███▀ ▄▀

  ▀█▄ ▀███▄     ▄███▀ ▄█▀

    ▀█▄ ▀▀██▄▄▄██▀▀ ▄█▀

       ▀▀▄▄▄▄▄▄▄▄▄▀▀
SLVR█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
[ WHITEPAPER ]
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
[ TECH  PAPER ]
▄█████████████████████████▄
██████████████    █████████
█████    █████    ▀▀▀▀█████
█████    ▀▀▀▀         █████
██▀▀▀              ▄▄▄█████
██        ▄▄▄███    ███████
██▄▄▄▄█    █████    █▀▀▀▀██
███████    ██▀▀▀         ██
█████▀▀▀              ▄▄▄██
████         ▄▄▄██    █████
█████▄▄▄▄    █████    █████
█████████    ██████████████
▀█████████████████████████▀
█████
█████
█████
▄▄▀▀
█████
█████
▄▄▀▀
█████

█████

▄▄▀▀

█████

█████

█████
!
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 316 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!