Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 245. (Read 446060 times)
POS does not work - reducing the coins sold on the stock exchange. The price can go up rapidly.
i have small ammnount of coin, on 17.0 coin is now 10 weight at which weight the POS?
You're certain of the dates and the weight? I've been three days into stake now, but the weight is gaining normally. I would start by redownloading the blockchain were it me, as that just seems odd. The PoS function is messed up right now, but the coins should be gaining weight if they are into the eligibility period.
Of course my understanding is limited. I don't know how to code worth a damn, so it's possible I'm wrong. But redownloading the blockchain surely won't harm anything.
I have 30 plus 3 days old coins in a wallet, but no stake. Weigt of coin is 0. Wallet unlock and still online. Where is the problem? Thanks for the advice. 
You're certain of the dates and the weight? I've been three days into stake now, but the weight is gaining normally. I would start by redownloading the blockchain were it me, as that just seems odd. The PoS function is messed up right now, but the coins should be gaining weight if they are into the eligibility period.
Of course my understanding is limited. I don't know how to code worth a damn, so it's possible I'm wrong. But redownloading the blockchain surely won't harm anything.
It's highly variable. If you're gaining weight, the system is working.
However, right at the present moment, we have a problem with the POS being frozen. Dev is on it, we know how to solve it, so it's not terribly worrisome. As long as your coins are gaining weight, they will eventually stake and at the correct interest for the moment that they stake. Prior to this speed bump, my coins have staked between 300-400 weight. I'm currently at 434, which is the highest I've personally seen. I've been told of people having weights in the thousands before they stake, though. It will happen.
i have small ammnount of coin, on 17.0 coin is now 10 weight at which weight the POS?
You're certain of the dates and the weight? I've been three days into stake now, but the weight is gaining normally. I would start by redownloading the blockchain were it me, as that just seems odd. The PoS function is messed up right now, but the coins should be gaining weight if they are into the eligibility period.
Of course my understanding is limited. I don't know how to code worth a damn, so it's possible I'm wrong. But redownloading the blockchain surely won't harm anything.
I have 30 plus 3 days old coins in a wallet, but no stake. Weigt of coin is 0. Wallet unlock and still online. Where is the problem? Thanks for the advice.
You're certain of the dates and the weight? I've been three days into stake now, but the weight is gaining normally. I would start by redownloading the blockchain were it me, as that just seems odd. The PoS function is messed up right now, but the coins should be gaining weight if they are into the eligibility period.
Of course my understanding is limited. I don't know how to code worth a damn, so it's possible I'm wrong. But redownloading the blockchain surely won't harm anything.
I have 30 plus 3 days old coins in a wallet, but no stake. Weigt of coin is 0. Wallet unlock and still online. Where is the problem? Thanks for the advice.
You're certain of the dates and the weight? I've been three days into stake now, but the weight is gaining normally. I would start by redownloading the blockchain were it me, as that just seems odd. The PoS function is messed up right now, but the coins should be gaining weight if they are into the eligibility period.
Of course my understanding is limited. I don't know how to code worth a damn, so it's possible I'm wrong. But redownloading the blockchain surely won't harm anything.
I have 30 plus 3 days old coins in a wallet, but no stake. Weigt of coin is 0. Wallet unlock and still online. Where is the problem? Thanks for the advice.
can not download the chain
qt is fubar?
qt is fubar?
Other than the staking issue that's being worked on, no. Not sure what's going wrong for you, but the chain is fine.
can not download the chain
qt is fubar?
qt is fubar?
so to stake coins do you just leave them in your TEKcoin wallet? is there a special selection or setting to stake coins? I have always traded TEK and never actually left it in my wallet.
Look at GetNextTargetRequired() closer. Do the math, the tipping point isn't at nactualspacing=0. Although setting nactualspacing to bottom out at 0 does solve the problem.
presstab - I do appreciate you trying to help get this problem solved.
Thanks,
Jason
Just my 10 cent:
As far as I can tell, the last two proof-of-stake blocks were 467226 and 467227.
Block 467226 was set two hours into the future, i.e.
467225 blocktime 07/30/14 07:47:33 (PoW)
467226 blocktime 07/30/14 09:47:05 (PoS)
467227 blocktime 07/30/14 07:47:32 (PoS)
Presumably whoever mined that block had a system clock that was way off...
in main.cpp, nActualSpacing is calculated as the time that passed between the last two PoS blocks (which in this case would be negative!)
This value is then used for calculating block difficulty bnNew.
I'm not that much into the mechaincs of block difficulty, but I could imagine that this leads to an insanely high block difficulty for PoS minting (bnTargetLimit?)
Perhaps we need a failsafe for negative time between last two PoS blocks?
As far as I can tell, the last two proof-of-stake blocks were 467226 and 467227.
Block 467226 was set two hours into the future, i.e.
467225 blocktime 07/30/14 07:47:33 (PoW)
467226 blocktime 07/30/14 09:47:05 (PoS)
467227 blocktime 07/30/14 07:47:32 (PoS)
Presumably whoever mined that block had a system clock that was way off...
in main.cpp, nActualSpacing is calculated as the time that passed between the last two PoS blocks (which in this case would be negative!)
This value is then used for calculating block difficulty bnNew.
I'm not that much into the mechaincs of block difficulty, but I could imagine that this leads to an insanely high block difficulty for PoS minting (bnTargetLimit?)
Perhaps we need a failsafe for negative time between last two PoS blocks?
It can not be difficulty is calculated based on just 2 last blocks, that would be foolish. All cryptocoins use at least few hundred blocks for PoW and PoS difficulty retargeting.
And I totally doubt it took 467226 blocks for the first ever occurence of PoS block with timestamp in future.
Look at GetNextTargetRequired() closer. Do the math, the tipping point isn't at nactualspacing=0. Although setting nactualspacing to bottom out at 0 does solve the problem.
It can not be difficulty is calculated based on just 2 last blocks, that would be foolish. All cryptocoins use at least few hundred blocks for PoW and PoS difficulty retargeting.
And I totally doubt it took 467226 blocks for the first ever occurence of PoS block with timestamp in future.
Well, tranz' fix addresses just that by setting it to zero when it gets negative.And I totally doubt it took 467226 blocks for the first ever occurence of PoS block with timestamp in future.
Since it also does some other calculations, it does not yet have a huge impact when it's only slightly negative.
OK, so I was definately wrong about Tranz's response being related to the block decode error 22 when using nomp. Can anyone shed light on what is causing that?
Just my 10 cent:
As far as I can tell, the last two proof-of-stake blocks were 467226 and 467227.
Block 467226 was set two hours into the future, i.e.
467225 blocktime 07/30/14 07:47:33 (PoW)
467226 blocktime 07/30/14 09:47:05 (PoS)
467227 blocktime 07/30/14 07:47:32 (PoS)
Presumably whoever mined that block had a system clock that was way off...
in main.cpp, nActualSpacing is calculated as the time that passed between the last two PoS blocks (which in this case would be negative!)
This value is then used for calculating block difficulty bnNew.
I'm not that much into the mechaincs of block difficulty, but I could imagine that this leads to an insanely high block difficulty for PoS minting (bnTargetLimit?)
Perhaps we need a failsafe for negative time between last two PoS blocks?
As far as I can tell, the last two proof-of-stake blocks were 467226 and 467227.
Block 467226 was set two hours into the future, i.e.
467225 blocktime 07/30/14 07:47:33 (PoW)
467226 blocktime 07/30/14 09:47:05 (PoS)
467227 blocktime 07/30/14 07:47:32 (PoS)
Presumably whoever mined that block had a system clock that was way off...
in main.cpp, nActualSpacing is calculated as the time that passed between the last two PoS blocks (which in this case would be negative!)
This value is then used for calculating block difficulty bnNew.
I'm not that much into the mechaincs of block difficulty, but I could imagine that this leads to an insanely high block difficulty for PoS minting (bnTargetLimit?)
Perhaps we need a failsafe for negative time between last two PoS blocks?
It can not be difficulty is calculated based on just 2 last blocks, that would be foolish. All cryptocoins use at least few hundred blocks for PoW and PoS difficulty retargeting.
And I totally doubt it took 467226 blocks for the first ever occurence of PoS block with timestamp in future.
so after some discussion about how this will go down, we need to try and calc how long its going to tak this pos block to pop at max posdiff. If we don't wait for it and do a rollback it will be much much more painful to many involved.
Hi thundertoe,I don't see the need for a rollback - can't we just hard-fork in n blocks?
Thanks to this being a hybrid coin, we still have PoW blocks, so we can comfortably fork at any point in the future, no?
Kind regards
Mike
so after some discussion about how this will go down, we need to try and calc how long its going to tak this pos block to pop at max posdiff. If we don't wait for it and do a rollback it will be much much more painful to many involved.
Thank you Tranz for the info on the fix.
Thanks Tranz...
I really appreciate the insight to the cause here. So do you know which stratum proxy does work with TEK at this time? I know that there are pools out there, just not sure what they are running.
I really appreciate the insight to the cause here. So do you know which stratum proxy does work with TEK at this time? I know that there are pools out there, just not sure what they are running.
Here is your answer.
https://github.com/rat4/blackcoin/commit/faec3751a07a657cdc4a2652fed85c52d053d4dc
This is the import part.
This fix will require a hard fork. It needs to be scheduled and old clients need altered. If there is no alert key, then enough time should given to get people on the right fork.
I also suggest full testnet and mainnet testing before issuing it. No I will not issue the fork myself, so please do not PM me about it. The lead developer needs to do this.
Good luck all.
https://github.com/rat4/blackcoin/commit/faec3751a07a657cdc4a2652fed85c52d053d4dc
This is the import part.
Quote
int64 nActualSpacing = pindexPrev->GetBlockTime() - pindexPrevPrev->GetBlockTime();
if (nActualSpacing < 0)
nActualSpacing = nTargetSpacing;
if (nActualSpacing < 0)
nActualSpacing = nTargetSpacing;
This fix will require a hard fork. It needs to be scheduled and old clients need altered. If there is no alert key, then enough time should given to get people on the right fork.
I also suggest full testnet and mainnet testing before issuing it. No I will not issue the fork myself, so please do not PM me about it. The lead developer needs to do this.
Good luck all.
block decode error 22 on submitblock.
I am running nomp and I have other PoS coins working fine such as BCX. I really want to get TEK up and running but I am not able to submit blocks as each one results in the error above. Was hoping one of the devs could point me at a cause if possible? I believe it is set to use text messages instead of json but I have tried both with the same results.
Kind of at a loss now but I have a good group of guys that want to mine this coin with me and help to promote if further. Basically we love TEK.
Thanks for any assistance with this.
I am running nomp and I have other PoS coins working fine such as BCX. I really want to get TEK up and running but I am not able to submit blocks as each one results in the error above. Was hoping one of the devs could point me at a cause if possible? I believe it is set to use text messages instead of json but I have tried both with the same results.
Kind of at a loss now but I have a good group of guys that want to mine this coin with me and help to promote if further. Basically we love TEK.
Thanks for any assistance with this.
Damn! What happened last night? Lowest trade of 0.00002??? Where's Thundertoe? Maybe some presence from the dev team might help? Maybe he can explain what's gone on here...?
Staking appears it may be have stalled or even be stuck. A few people i know are looking at it. If anyone has an idea of who might be able to figure it out feel free to call in a favor, or start a bounty for them to check it out.
Apparently Thundertoe doesnt know how to fix the staking issues. He's having people look at it.
Jump to: