The danger of putting too much weight on the latest block:
Lets put it to an extreme and you use only the last 1 or 2 blocks. A pool can easy cherry pick those blocks, leave for 2 blocks, come back... and repeat. The diff would jump up and down like crazy.
So it is important to fine tune the settings and find a good path between instant reaction and smoothing the diff changes.
I would never recommend a 1-2 block focus. That would be crazypants thinking.
I seriously think 6 is a nice even number, and it falls in line with about the average number of blocks that Clever rapes at any given time. You put more focus on those 6 blocks, instead of 24 evenly, and you'll see a big change in Clever's ability to own 90% of the network.
Of course, GJ has some code on the table right now. I guess we'll all just need to wait to see what it looks like before we try to push one way or another.
-Fuse
I'm with CED and Fuse in this, I would say three / four blocks minimum because otherwise the diff will be all over the place. I'm also missing some structure in this discussion. I did put down a list yesterday with strange diff values imho thats problem uno, if we don't solve that problem every solution will probably show the same weird behaviour as KGW and DGW are showing.
Second, if you want to modify the algo you need to identify the problem properly and with the problem description you can work out a solution. Without a proper problem description there is a huge risc of drifting away from the goal. Why take 6 blocks or 10 or 24? Because thats the number of doors in your office? Or is it the blocks that are being mined fast? So in my opinion the path could look like this:
phase1
- identify the cause of the swings more than 3 and 1/3
- work out a solution for point 1 first
- if the fix for point 1 is outside DGW code see if DGW is acting as expected in the first place
phase 2
- identify the problem and descibe it properly (yeah I know it's jumppool, but whats really the undelying thing that causes the trouble)
- work out a modification of the algo by testing it on past hashrate swings and see if it smoothens out those.
- test the modification thorough for vulnerabilities and flaws
- implement it