Author

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

legendary
Activity: 2184
Merit: 1011
Franko is Freedom
If you are a tekpool op

Code:
git pull origin

and resync with the blockchain above to cut down your sync time.

Windows wallets will be out soon.
legendary
Activity: 2184
Merit: 1011
Franko is Freedom
version 1.9 will create forks everytime someone stakes due to an overlook in the code. same thing used to happen with bottlecaps.
legendary
Activity: 2184
Merit: 1011
Franko is Freedom
Before anyone does anything else, just stop ^_^

Update your client to the latest update. When you do "getinfo" it will look similar to this

Code:
{
    "version" : "v2.0.1.0-gf96a5a-TEK",
    "protocolversion" : 60007,
    "walletversion" : 60000,
    "balance" : 1704.28190100,
    "newmint" : 0.00000000,
    "stake" : 2568.20805900,
    "blocks" : 506608,
    "moneysupply" : 1868796.74635500,
    "connections" : 43,
    "proxy" : "",
    "ip" : "74.196.63.95",
    "difficulty" : 34026.30075343,
    "testnet" : false,
    "keypoololdest" : 1399997248,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

This protocol makes it so PoS and PoW difficulties are calculated correctly which was over looked during the original update and the reason why as soon as anyone staked they created their own fork.

https://www.dropbox.com/s/b7cooz2yewxk2ns/tekcoin-bootstrap.zip

Code:
addnode=74.196.63.95
addnode=64.188.164.77
addnode=94.220.6.66
legendary
Activity: 1288
Merit: 1043
:^)
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?
legendary
Activity: 1033
Merit: 1005
Current peer list @ 484k blocks remaining:

Quote
[
{
"addr" : "95.165.128.192:8514",
"services" : "00000001",
"lastsend" : 1409147217,
"lastrecv" : 1409147217,
"conntime" : 1409146989,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 507035,
"banscore" : 0
},
{
"addr" : "108.59.185.202:8514",
"services" : "00000001",
"lastsend" : 1409147142,
"lastrecv" : 1409147000,
"conntime" : 1409146995,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506636,
"banscore" : 0
},
{
"addr" : "74.196.63.95:8514",
"services" : "00000001",
"lastsend" : 1409147013,
"lastrecv" : 1409147051,
"conntime" : 1409147013,
"version" : 60007,
"subver" : "/tekcoin:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506608,
"banscore" : 0
},
{
"addr" : "75.90.67.140:8514",
"services" : "00000001",
"lastsend" : 1409147081,
"lastrecv" : 1409147208,
"conntime" : 1409147081,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 507033,
"banscore" : 0
},
{
"addr" : "110.174.169.110:8514",
"services" : "00000001",
"lastsend" : 1409147287,
"lastrecv" : 1409147286,
"conntime" : 1409147103,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 184330,
"banscore" : 0
},
{
"addr" : "143.238.193.60:8514",
"services" : "00000001",
"lastsend" : 1409147229,
"lastrecv" : 1409147234,
"conntime" : 1409147228,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506823,
"banscore" : 0
},
{
"addr" : "68.145.176.204:8514",
"services" : "00000001",
"lastsend" : 1409147278,
"lastrecv" : 1409147280,
"conntime" : 1409147278,
"version" : 60006,
"subver" : "/tekcoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 507355,
"banscore" : 0
},
{
"addr" : "37.59.31.185:8514",
"services" : "00000001",
"lastsend" : 1409147293,
"lastrecv" : 1409147294,
"conntime" : 1409147290,
"version" : 60006,
"subver" : "/tekcoin:1.1.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 506664,
"banscore" : 0
}
]

Will the 1.9.1 and 2.0.0 screw my download up?  I thought the config file with listen=0 sets it to connect to only nodes supplied...
newbie
Activity: 17
Merit: 0
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  Grin

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.


OK, it did add portforwarding for 8514 and 18514 now, but if it does the trick? My config is like the one above.
legendary
Activity: 1288
Merit: 1043
:^)
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!
legendary
Activity: 1033
Merit: 1005
Ok.  I'm redownloading the block chain with wallet locked to prevent PoS... Also with a good backup of my wallet before the fork.
legendary
Activity: 1288
Merit: 1043
:^)
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!
legendary
Activity: 1288
Merit: 1043
:^)
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  Grin

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.
legendary
Activity: 1033
Merit: 1005
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.
newbie
Activity: 17
Merit: 0
@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_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXE

Awaiting further instructions!  Wink

Can your node accept incoming connections? If yes please post your IP so I can add it to list.

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.
legendary
Activity: 1288
Merit: 1043
:^)
@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_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXE

Awaiting further instructions!  Wink

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.
newbie
Activity: 17
Merit: 0
@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_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXE

Awaiting further instructions!  Wink
legendary
Activity: 1288
Merit: 1043
:^)
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.
legendary
Activity: 1148
Merit: 1000
I sent few coins to cryptsy yesterday and they haven't posted there yet, so are they lost?

Coins do not get lost, they are on the fork that is chosen.

So you send coins they don't show up, most likely they are on wrong fork/chain.  When you resync to the proper chain your coins were not moved so they are back in your balance.

If you stakes on a bad chain, and you resync the chain, the coins that staked have not staked on thie good hain and will be ready.  Wallet is going to have a lot of uncomfirmed transaction but everything matches back up as it should

Thanks for clearing it up
full member
Activity: 274
Merit: 122
I will confirm that the sync started immediately.  I will let you know once this is complete.
legendary
Activity: 1288
Merit: 1043
:^)
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.
legendary
Activity: 1023
Merit: 1001
Tokenize Fantasy Sports
I sent few coins to cryptsy yesterday and they haven't posted there yet, so are they lost?

Coins do not get lost, they are on the fork that is chosen.

So you send coins they don't show up, most likely they are on wrong fork/chain.  When you resync to the proper chain your coins were not moved so they are back in your balance.

If you stakes on a bad chain, and you resync the chain, the coins that staked have not staked on thie good hain and will be ready.  Wallet is going to have a lot of uncomfirmed transaction but everything matches back up as it should
legendary
Activity: 1148
Merit: 1000
I sent few coins to cryptsy yesterday and they haven't posted there yet, so are they lost?
Jump to: