Topic: [TEK] TEKcoin Hi-PoS hybrid pos/pow no premine/ipo/ico - page 246. (Read 446060 times)
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...?
i'm syncing from 0...pos diff was a lot lower then
proof-of-stake" : 0.00024414,
i put up a pull request to add netstakeweight to getmininginfo
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?
in tek -
CBigNum bnTargetLimit = bnProofOfStakeLimit;
in flt -
CBigNum bnTargetLimit = GetProofOfStakeLimit(0, nTime);
in nvc -
CBigNum bnTargetLimit = GetProofOfStakeLimit(0, nTime);
in cap -
CBigNum bnTargetLimit = bnProofOfStakeLimit;
in black -
CBigNum bnTargetLimit = fProofOfStake ? GetProofOfStakeLimit(pindexLast->nHeight) : bnProofOfWorkLimit;
in hbn -
CBigNum bnTargetLimit = bnProofOfStakeLimit;
So it's got company if this is a PoS difficulty issue problem, cap and hbn will have the same vulnerability. I don't see a high difficulty though, it's like .003xxx
{
"proof-of-work" : 133987.62952168,
"proof-of-stake" : 0.00390625,
"search-interval" : 1
}
Maybe we could all lock our wallets down and someone could open theirs and see if they can stake, see if it would start moving again.
How do you tell what the weight is on the network for stake? For instance, coins usually have getstakinginfo, or show this in getmininginfo, or somewhere right, tek doesn't seem to show this at all. Nor an estimate of how long to stake a block based on the network weight.
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?
thundertoe, do you have the master checkpoint key? is there a reason there is no sync checkpoints?
23:44:06

getcheckpoint
23:44:06

{
"synccheckpoint" : "00000eaa8dd7e902871c444aeb415673b8244c6b7b1742ca398cefa60d87c4c1",
"height" : 0,
"timestamp" : "2013-08-11 10:01:09 UTC"
}
and code doesn't have any either, except for block1. Network should work without them, but should it fork, no one is going to check it.
And only thing I see is the POS difficulty is super low, which I would expect it to cause lots of PoS orphans, but I'm not seeing that either...
Edit...and where are the explorers? they all down?
23:44:06

getcheckpoint
23:44:06

{
"synccheckpoint" : "00000eaa8dd7e902871c444aeb415673b8244c6b7b1742ca398cefa60d87c4c1",
"height" : 0,
"timestamp" : "2013-08-11 10:01:09 UTC"
}
and code doesn't have any either, except for block1. Network should work without them, but should it fork, no one is going to check it.
And only thing I see is the POS difficulty is super low, which I would expect it to cause lots of PoS orphans, but I'm not seeing that either...
Edit...and where are the explorers? they all down?
now watch it go past 0.0004 when stake goes back fully functional all these idiots who sold cheap will be chasing to buy back
to quote Wolf of wall street, Jordan Belfort: "[throwing money at the FBI agents] Fun coupons!"
now watch it go past 0.0004 when stake goes back fully functional all these idiots who sold cheap will be chasing to buy back
I'm sure we'll recover, I think the best plan of action would be to buy tons of TEK while it's cheap, we've had this trend before (cryptsy) this should be rock bottom in TEKcoins re-occuring spike trends, so buy up!
well I just came over and looked at wtf is going on as tek crashes. Come on, really, the coin held up on some staking, and you guys start dumping.
see if I can see if there's something going on, but my debug file looks nice and clean, so might just be competition, SHA blocks being found pretty regular.
see if I can see if there's something going on, but my debug file looks nice and clean, so might just be competition, SHA blocks being found pretty regular.
What he said! It's not like POS isn't slow and random with other coins or anything. Panic is a useless emotion, unless you don't do it and everyone else does.
Fuck it, what am I saying? All you "sky is falling" types enrich me.
most of my coin seems to be at a very low stake value. Don't understand why. As there should be a lot of coins ready to stake. Weight went to zero for almost all my coins. Did anybody else see this?
well I just came over and looked at wtf is going on as tek crashes. Come on, really, the coin held up on some staking, and you guys start dumping.
see if I can see if there's something going on, but my debug file looks nice and clean, so might just be competition, SHA blocks being found pretty regular.
see if I can see if there's something going on, but my debug file looks nice and clean, so might just be competition, SHA blocks being found pretty regular.
I have weight of 1778 not staked yet. Last stake on 7/28
I had a Stake hit last week
the weight was over 3800 before it staked
None of mine have ever staked with less than a weight of 2500
Only been in TEK ~ 1½ months
Novacoin currently has around 900k coins in circulation (since feb 2013) with a price of 0.002 per coin but Tek has a much more aggressive coin emission/minting rate
From Novacoin Wiki
Proof-of-Work block reward can be calculated using formula nBlockReward = 100 / (nMaxTarget / nCurrentTarget) ^ (1/6). It means, that reward cut a half every 64x multiply of difficulty.
Proof-of-Stake block reward based on CoinAge parameter and Proof-of-Stake difficulty. Interest can be calculated using formula nRewardCoinYear = 1 / (nMaxPoSTarget / nCurrentPoSTarget) ^ (1/6). It means, that interest starts from 100% per year and cut a half every 64x multiply of difficulty.
Anyone know how TEK is configured?
TEK pow currently is 1 coin per block for infinity-1440 coins per day- never changing, is this correct?
How is Pos configured?
Proof-of-Work block reward can be calculated using formula nBlockReward = 100 / (nMaxTarget / nCurrentTarget) ^ (1/6). It means, that reward cut a half every 64x multiply of difficulty.
Proof-of-Stake block reward based on CoinAge parameter and Proof-of-Stake difficulty. Interest can be calculated using formula nRewardCoinYear = 1 / (nMaxPoSTarget / nCurrentPoSTarget) ^ (1/6). It means, that interest starts from 100% per year and cut a half every 64x multiply of difficulty.
Anyone know how TEK is configured?
TEK pow currently is 1 coin per block for infinity-1440 coins per day- never changing, is this correct?
How is Pos configured?
current difficulties

{
"proof-of-work diff" : 155689.79121328,
"proof-of-stake diff" : 0.00390625,
}
does pos diff change on a per wallet basis when staking?I'm currently not staking any coins

{
"proof-of-work diff" : 155689.79121328,
"proof-of-stake diff" : 0.00390625,
}
does pos diff change on a per wallet basis when staking?I'm currently not staking any coins
I've been reading up on the novacoin code (which TEK incorporates) and looking at the numbers. I suspect it's not actually stuck, but has hit a really high difficulty due to a lot of staking. The coin has ramped up production significantly (as it's design would suggest) and I suspect that the code has responded accordingly. Give it a couple more days before panicking. Then don't panic anyway, because it's a useless emotion.
the way i see it Tek will go one of two ways if it stays in its current format based on current public information of the coins code/parameters including unlimited coins
1 the price per coin will become so low that pow will cease by its own volition (due to negative profits) and TEK will become pos only (hope the code can handle this)
2 the price per coin will sustain pow mining and early adopters will be staking millions of dollars worth of TEK per month to sell on the open market
Wonder which one is most likely
Probably be a good idea to publish on the opening page what happens to stake rates etc as coded in the coin as more TEK are minted
1 the price per coin will become so low that pow will cease by its own volition (due to negative profits) and TEK will become pos only (hope the code can handle this)
2 the price per coin will sustain pow mining and early adopters will be staking millions of dollars worth of TEK per month to sell on the open market
Wonder which one is most likely
Probably be a good idea to publish on the opening page what happens to stake rates etc as coded in the coin as more TEK are minted
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.
So no one is actually actively developing Tek then ? just down to coinholders
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.
Jump to: