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

[defaced]

addnodes from my post

[1714181995]

1714181995

[1714181995]

1714181995

[1714181995]

1714181995

[x3maniac]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

[defaced]

Can we use the build from yesterday to sync up to this?  But we cannot pos or pow on it?

When are we getting the windows build so we can enable pos to test the latest github fix?

one from yesterday will cause forks

[defaced]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

notice your protocolversion isnt 60007

[ofeefee]

Can we use the build from yesterday to sync up to this?  But we cannot pos or pow on it?

When are we getting the windows build so we can enable pos to test the latest github fix?

one from yesterday will cause forks

I saw you posted while I was typing, I see you said soon, will keep checking back.

[x3maniac]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

notice your protocolversion isnt 60007

yea i just saw on to that. i'm doing a git pull origin right now and recompiling to see how it goes

[jk9694]

So I did as above and deleted everything except for my wallet.dat and conf file.  

Added the two nodes only using connect instead of addnode

Remove all other and set listen to 0

However when i do getinfo I get:


"version" : "v1.1.0.0-gf96a5a-TEK",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 5.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 265983,
"moneysupply" : 433714.51779900,
"connections" : 1,
"proxy" : "",
"ip" : "74.136.236.120",
"difficulty" : 45573.60129880,
"testnet" : false,
"keypoololdest" : 1393909672,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""

Seems that the protocolversion is still not correct.  Am I right?

[x3maniac]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

notice your protocolversion isnt 60007

yea i just saw on to that. i'm doing a git pull origin right now and recompiling to see how it goes

just updated and trying to reload the blocks from my PRE forked chain. and my balances are not showing up

{
    "version" : "v2.0.1.0-gf96a5a-TEK",
    "protocolversion" : 60007,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 4.00010000,
    "stake" : 0.00000000,
    "blocks" : 470925,
    "moneysupply" : 1831606.80465500,
    "connections" : 1,
    "proxy" : "",
    "ip" : "67.212.70.84",
    "difficulty" : 154291.18138764,
    "testnet" : false,
    "keypoololdest" : 1408877948,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

and ideas?

[xhabit]

So, download is running ...  

[defaced]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

notice your protocolversion isnt 60007

yea i just saw on to that. i'm doing a git pull origin right now and recompiling to see how it goes

just updated and trying to reload the blocks from my PRE forked chain. and my balances are not showing up

{
    "version" : "v2.0.1.0-gf96a5a-TEK",
    "protocolversion" : 60007,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 4.00010000,
    "stake" : 0.00000000,
    "blocks" : 470925,
    "moneysupply" : 1831606.80465500,
    "connections" : 1,
    "proxy" : "",
    "ip" : "67.212.70.84",
    "difficulty" : 154291.18138764,
    "testnet" : false,
    "keypoololdest" : 1408877948,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

and ideas?

i hope you didnt delete your wallet file.

if you didnt, you can just rescan and your balance will return

[jk9694]

So where is the correct windows download at?  I pulled the latest from a previous post and if that is still not correct....

[x3maniac]

i can't tell if i'm on the right chain or not.


{
    "version" : "v1.1.0.0-gf96a5a-TEK",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 507077,
    "moneysupply" : 1873569.90170400,
    "connections" : 0,
    "proxy" : "",
    "ip" : "23.249.161.254",
    "difficulty" : 250768.75421742,
    "testnet" : false,
    "keypoololdest" : 1381518108,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

the connection comes and goes with 1, and it will download 1 block or so everytime. but its still behind the block you stated

notice your protocolversion isnt 60007

yea i just saw on to that. i'm doing a git pull origin right now and recompiling to see how it goes

just updated and trying to reload the blocks from my PRE forked chain. and my balances are not showing up

{
    "version" : "v2.0.1.0-gf96a5a-TEK",
    "protocolversion" : 60007,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 4.00010000,
    "stake" : 0.00000000,
    "blocks" : 470925,
    "moneysupply" : 1831606.80465500,
    "connections" : 1,
    "proxy" : "",
    "ip" : "67.212.70.84",
    "difficulty" : 154291.18138764,
    "testnet" : false,
    "keypoololdest" : 1408877948,
    "keypoolsize" : 102,
    "paytxfee" : 0.00010000,
    "errors" : ""
}

and ideas?

i hope you didnt delete your wallet file.

if you didnt, you can just rescan and your balance will return

i wouldn't have cause you can see that new mint is active. but i'll run a tekcoind --rescan

[x3maniac]

when "ip" : "0.0.0.0", does that mean my IP is ban?

[defaced]

we are currently testing the windows wallet now.

[defaced]

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

bump

[subSTRATA]

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.

[4x13]

will someone also please post a Mac OS X version of the wallet too when they post the new windows version.

Thanks!!

[defaced]

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.

[xhabit]

i'm really interests witch balance stay later in the wallet here ... i'hope all members of our pool will not lost so mutch or in the best case nothing, lost.

[defaced]

i'm really interests witch balance stay later in the wallet here ... i'hope all members of our pool will not lost so mutch or in the best case nothing, lost.

Well any blocks mined after block 506608 would be lost by updating to my client and chain. BUT you will be able to stake fine with out an forks.

You could keep the original client and eventually stake will pop, but so far everyone has been waiting for a month, which is why this update was even proposed.

The update that first got released allowed staking but the difficulty was being calculated sort of randomly which caused everyone to fork their own chain. Proof of work however still worked, because it was never broken.

This update, you can do it two ways, you can just accept that some blocks are orphaned, or you can completely ignore anything ive done and continue the work chain and hope everyone connects to yours in the end.