As the title says. There WILL be a jump in stake difficulty. That is a fact. What do you think it will go to? At what point does it get ridiculous and you will stop PoS mining?
I think i read somewhere that the PoS difficulty algorithm also keeps in cosideration the last diff. So it can't really "jump", it will probably just increase with graduality.
Interesting. I thought it was a function of how many stake tickets there are in the mempool(?) I think it was called? Once that pool is full the price goes up until it reaches a point to where there are tickets available for purchase/staking again as the mempool count goes back down. Once it finds a level where the pool will still have stakes being purchased that determines the stake ticket difficulty/price. This then creates a supply/demand price based on the ROI people are willing to take. We shall see I guess. I have a feeling it is going to be a lot more than 2...
Yes, it is. I am very surprised it has not gone up at all. Maybe it has to chew through all the initial stakes purchased before block 4096 as there were more than 8192? Then it will start moving up?
what is the time frame for staking diff adjustment, like mining diff and stake rewards. They dont adjust every block so once a particular no of blocks have been added ticket price will go up and then after same no of block it will adjust again.
Well on testnet it was rather fluid. I dont remember a block count being mentioned. It was all based on the amount of tickets in the mempool for staking. I have voted 3 times already and received 6dcr reward. That is more than 1.5dcr reward. I have also not seen any sstx tickets repurchased with the reward funds.
i dont think mempool is checked every block, there should be a fixed no of blocks before it is checked to calculate new ticket price, that is why we have not seen price rise. Also i think like PoW mined blocks, PoS mined coins might not be mature before 256 blocks to buy tickets again. I should mention that i am just speculating here.
This was not the behavior I observed on testnet. I PoWd about 500dcr then stopped PoW and did only PoS up to about 1500dcr. All rewards were immediately available. I would see a vote and then on the next block an sstx would go through using the stake funds and reward. No waiting, reward dcr was immediately used. My totals now show the reward in ALL funds but not in LOCK or SPENDABLE. My LOCK total has actually gone down. Now that I look at it closer it may be that the 3x2 stake dcr has been returned, +6dcr ALL, and nothing else yet. My LOCK has gone down -6dcr as well as my stake ticket count, -3 tix, and my SPENDABLE has not increased at all. Very weird and not what happened on testnet.
I don't know what is exactly "StakeDiffWindowSize: 144", but maybe it's number of blocks before difficulty adjustment. You can see it here: https://github.com/decred/dcrd/blob/master/chaincfg/params.go#L334 So we can either wait for 4096 + 144 = 4240 block or ask davecgh
So these are the differences. MainNet: Code: TicketMaturity: 256, TicketExpiry: 40960, // 5*TicketPoolSize CoinbaseMaturity: 256, TestNet: Code: TicketMaturity: 16, TicketExpiry: 6144, // 6*TicketPoolSize CoinbaseMaturity: 16,
Well for what it is worth it appears to be working for me. I have voted 9 times so far. I am starting to see the reward come back and immediately be used for sstx again on the next block. I am liking this so far!
As long as I am still seeing sstx go through within a block or three of the reward coming back I am not going to fuck with it! It is working. Yeah your stake might get in the pool before mine by doing that. When you have a few hundred stake votes out there though does it matter if it goes in on the next block or 3 or 4 blocks later? I dont think so. Not yet at least.
then may be even i should stick to 0.05 . yeah your right it wont matter if sstx goes 3-4 blocks later .
4096 + 256 = 4352, Meanwhile block #4438 already mined and PoS difficulty still not adjusted. Anyway, devs probably see it.
Those are maturity periods for mined PoW & PoS coins. Difficulty Adjustments are different parameters.
144*20=2880 (windowsize*windows) So I think it will start to increase so it settles on a new value around block 4096+2880=6976
Formula is here and the parameters It looks at windows(20) of block size windows size(144), so 2880 blocks. For these, the target tickets is 8192*5=40960. It then calculates as % change per window in the ticket pool size. The maximum re-target is a factor of 4, so it will jump from 2 to 8 difficulty at most! (per block, that is)