https://github.com/chrisfranko/TEK/commit/c225c596e900defd4074626a973e391089b6bccb
git pull origin and tell me what happens
Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 219. (Read 446058 times)
OR
should be
Code:
CBigNum inline GetProofOfStakeLimit(int nHeight, unsigned int nTime)
{
if(fTestNet) // separate proof of stake target limit for testnet
return bnProofOfStakeLimit;
if(nTime > TARGETS_SWITCH_TIME || nHeight >= HARDFORK_1) // 18 bits since 20 July 2013
return bnProofOfStakeLimitV2;
if(nHeight + 1 > 15000) // 24 bits since block 15000
return bnProofOfStakeLimit;
if(nHeight + 1 > 14060) // 31 bits since block 14060 until 15000
return bnProofOfStakeHardLimit;
return bnProofOfWorkLimit; // return bnProofOfWorkLimit of none matched
}
{
if(fTestNet) // separate proof of stake target limit for testnet
return bnProofOfStakeLimit;
if(nTime > TARGETS_SWITCH_TIME || nHeight >= HARDFORK_1) // 18 bits since 20 July 2013
return bnProofOfStakeLimitV2;
if(nHeight + 1 > 15000) // 24 bits since block 15000
return bnProofOfStakeLimit;
if(nHeight + 1 > 14060) // 31 bits since block 14060 until 15000
return bnProofOfStakeHardLimit;
return bnProofOfWorkLimit; // return bnProofOfWorkLimit of none matched
}
should be
Code:
CBigNum inline GetProofOfStakeLimit(int nHeight, unsigned int nTime)
{
if(fTestNet) // separate proof of stake target limit for testnet
return bnProofOfStakeLimit;
if(nTime > TARGETS_SWITCH_TIME || nHeight >= HARDFORK_1) // 18 bits since 20 July 2013
return bnProofOfStakeLimitV2;
if(nHeight + 1 > 15000) // 24 bits since block 15000
return bnProofOfStakeLimit;
if(nHeight + 1 > 14060) // 31 bits since block 14060 until 15000
return bnProofOfStakeHardLimit;
return bnProofOfStakeLimit; // return bnProofOfStakeLimit of none matched
}
{
if(fTestNet) // separate proof of stake target limit for testnet
return bnProofOfStakeLimit;
if(nTime > TARGETS_SWITCH_TIME || nHeight >= HARDFORK_1) // 18 bits since 20 July 2013
return bnProofOfStakeLimitV2;
if(nHeight + 1 > 15000) // 24 bits since block 15000
return bnProofOfStakeLimit;
if(nHeight + 1 > 14060) // 31 bits since block 14060 until 15000
return bnProofOfStakeHardLimit;
return bnProofOfStakeLimit; // return bnProofOfStakeLimit of none matched
}
Found the issue
https://github.com/maxxine/TEK/blob/f982faeb6a580d5f6030fc460b9e3dce1b8461b0/src/main.cpp#L981
CBigNum bnTargetLimit = GetProofOfStakeLimit(0, nTime);
should be
CBigNum bnTargetLimit = GetProofOfStakeLimit(15001, nTime);
https://github.com/maxxine/TEK/blob/f982faeb6a580d5f6030fc460b9e3dce1b8461b0/src/main.cpp#L981
CBigNum bnTargetLimit = GetProofOfStakeLimit(0, nTime);
should be
CBigNum bnTargetLimit = GetProofOfStakeLimit(15001, nTime);
so, i have stop all connection and the stratum server. until there is a correct blockcain downloaded
Wow - well I'm a little overwhelmed
I updated my wallet last week, checked my wallet last night, saw it staked and was fully sync'd and thought all was good. I checked the forum this am and saw there were 5 new pages of posts (uhhhh that's a bad sign)
Now my wallet says - out of sync
(I'm no noob, but ... let's just start from there)
OK - so what am I supposed to do? I read all of the posts. I don't know what I'm supposed to be doing at the moment. Can we get a consensus, and clear direction?
I updated my wallet last week, checked my wallet last night, saw it staked and was fully sync'd and thought all was good. I checked the forum this am and saw there were 5 new pages of posts (uhhhh that's a bad sign)
Now my wallet says - out of sync
(I'm no noob, but ... let's just start from there)
OK - so what am I supposed to do? I read all of the posts. I don't know what I'm supposed to be doing at the moment. Can we get a consensus, and clear direction?
looking into that now also.
ayayayayay
ayayayayay
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat 0ms
mapBlockIndex.size() = 497030
nBestHeight = 490259
setKeyPool.size() = 102
mapWallet.size() = 1514
mapAddressBook.size() = 3
maybe that will help? it's from my debug.log
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.
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
xhabit
I am sure we are going to lose some of the blocks mined on your pool. I have told all of the guys in my group to stop mining for now, we will be back once things are fixed.
JK9694
I am sure we are going to lose some of the blocks mined on your pool. I have told all of the guys in my group to stop mining for now, we will be back once things are fixed.
JK9694
so, i'take a beer now ... and smoke a cigaret 
looking into that now also.
ayayayayay
ayayayayay
so the blockcain download stop with this:
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
i run into the same issue
on top of that, when i removed my block chain then used defaced blockchain my balance goes to 0
OK, So Defaced I am with you. Lets do what you said. I will make the decision.... 
ok, so If I understand what you are saying is this;
if we backup to your blockchain from yesterday, use the "latest" source you are working on right now to rebuild our wallets, orphan what blocks were mined between now and then we will have both PoW and PoS working correctly. YES??
if we backup to your blockchain from yesterday, use the "latest" source you are working on right now to rebuild our wallets, orphan what blocks were mined between now and then we will have both PoW and PoS working correctly. YES??
yes
so the blockcain download stop with this:
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
I seen that a few times in my sync also, it will eventually get to where you need to be.
Sitting in corner quietly, wallet shutdown, waiting patiently for a consensus and proven fix.
Jason
Jason
ok, so If I understand what you are saying is this;
if we backup to your blockchain from yesterday, use the "latest" source you are working on right now to rebuild our wallets, orphan what blocks were mined between now and then we will have both PoW and PoS working correctly. YES??
if we backup to your blockchain from yesterday, use the "latest" source you are working on right now to rebuild our wallets, orphan what blocks were mined between now and then we will have both PoW and PoS working correctly. YES??
so the blockcain download stop with this:
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
received block 00000000007a42d4fdee
Postponing 499 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 0000000000dbab7ac12d..0000000000dbab7ac12d
REORGANIZE: Connect 1 blocks; 0000000000dbab7ac12d..12abf6d9bfa4c2870cce
ERROR: ConnectInputs() : e11c094661 stake reward exceeded
ERROR: Reorganize() : ConnectBlock 12abf6d9bfa4c2870cce failed
InvalidChainFound: invalid block=00000000007a42d4fdee height=48224 trust=16825696 date=10/09/13 17:41:00
InvalidChainFound: current best=0000000000dbab7ac12d height=47724 trust=47725 date=10/09/13 09:56:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 0 addresses to peers.dat 4ms
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.
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.
my ip: 212.21.68.60
but in the moment listen=0 until have download the blockcain.
the download log: show ...
ProcessBlock: ACCEPTED
received block 00000000005da29be13d
SetBestChain: new best=00000000005da29be13d height=32176 trust=32177 date=09/28/13 11:57:23,block hash= 00000000005da29be13da8c49f4a7d17ff804da76140842424db07f9be8be77b
ProcessBlock: ACCEPTED
received block 000000000008dda057e9
SetBestChain: new best=000000000008dda057e9 height=32177 trust=32178 date=09/28/13 11:57:47,block hash= 000000000008dda057e96669a28c33ee9538c00708f1b84b261ddb8e32d5dee8
ProcessBlock: ACCEPTED
received block 0000000000519797e2a1
SetBestChain: new best=0000000000519797e2a1 height=32178 trust=32179 date=09/28/13 11:59:02,block hash= 0000000000519797e2a18cd5e4d09c4560c575e9b2f7109ed2b5cc202dc4d924
ProcessBlock: ACCEPTED
received block 000000000038ba1173cc
SetBestChain: new best=000000000038ba1173cc height=32179 trust=32180 date=09/28/13 11:59:12,block hash= 000000000038ba1173ccbc2a6485f5eca3a8a530228d89da42c90559aad7bd85
ProcessBlock: ACCEPTED
received block 00000000003c2eca8141
SetBestChain: new best=00000000003c2eca8141 height=32180 trust=32181 date=09/28/13 12:00:12,block hash= 00000000003c2eca8141152e6993a192da661bd403cdae1db0a35a2e9394277a
ProcessBlock: ACCEPTED
received block 00000000004603eb0009
but in the moment listen=0 until have download the blockcain.
the download log: show ...
ProcessBlock: ACCEPTED
received block 00000000005da29be13d
SetBestChain: new best=00000000005da29be13d height=32176 trust=32177 date=09/28/13 11:57:23,block hash= 00000000005da29be13da8c49f4a7d17ff804da76140842424db07f9be8be77b
ProcessBlock: ACCEPTED
received block 000000000008dda057e9
SetBestChain: new best=000000000008dda057e9 height=32177 trust=32178 date=09/28/13 11:57:47,block hash= 000000000008dda057e96669a28c33ee9538c00708f1b84b261ddb8e32d5dee8
ProcessBlock: ACCEPTED
received block 0000000000519797e2a1
SetBestChain: new best=0000000000519797e2a1 height=32178 trust=32179 date=09/28/13 11:59:02,block hash= 0000000000519797e2a18cd5e4d09c4560c575e9b2f7109ed2b5cc202dc4d924
ProcessBlock: ACCEPTED
received block 000000000038ba1173cc
SetBestChain: new best=000000000038ba1173cc height=32179 trust=32180 date=09/28/13 11:59:12,block hash= 000000000038ba1173ccbc2a6485f5eca3a8a530228d89da42c90559aad7bd85
ProcessBlock: ACCEPTED
received block 00000000003c2eca8141
SetBestChain: new best=00000000003c2eca8141 height=32180 trust=32181 date=09/28/13 12:00:12,block hash= 00000000003c2eca8141152e6993a192da661bd403cdae1db0a35a2e9394277a
ProcessBlock: ACCEPTED
received block 00000000004603eb0009
I say we jump back to defaced's blockchain and orphan those who don't pay enough attention to update. (Yes I know this may suck for some, but it is what it is) I am losing as well as many, and I will recoup. lets do this.. 
yes this look nice ...
Jump to: