@chia_project
Re:Plot Filter
Instead of a Plot Filter, why not let the user configure how hard to run a deployment, and get points from the pool, proportional to effort?
Trying to make a Raspberry Pi as valuable as a Threadripper doesn’t make sense.
How many forks can be prevented by removing unnecessary parameters?
🍀
⬆️(Implicitly) Repeated i times until the target storage is mostly filled with i plots, but leaving a remainder on a simple plotter setup.
So however Bram would determine the final merge/reduce step, it would force the merge out of cached memory.
In other words, why not intentionally slow plot times down again by stepping on the neck of the bottleneck (storage bus writes to persistent storage)?
🧐 🍀
@chia_project
🧐🧌🧙♂️ Troll-CHIP-X ✨💫🌟
Re: Hard-Fork Plot-Derivation (🪨🍴🌾)
Instead of a single table sequence (per plot), why not merge M sequences of N length at the final step?
Thereby, more intermediate plotting space is required, which focuses on the desired bottleneck (storage).
Also, as a biproduct, any remaining space when the last temp space is deleted, would tend to remain, and be available for DataLayer/DIG/etc.
🫡 @hoffmang 🌱 🪙
I meant @Evergreenminer @michaeltaylor3d and everyone else remotely interested.
A flexible hardware solution might be the only way to protect the Farmer Keys… 🔐
@chia_project @Evergreen
💡🤔 Maybe for a future #PoST ⛓️if not #Chia:
If a NC requirement is to prevent the Farmer from sharing the Secret Keys (aka Private Keys) with a Pool Operator…
Why not have the Farmer use a @Tangem or equivalent to sign blocks? As long as not economically prohibitive (cards and readers), and as long as the Secret Keys can’t be exported to even the Farmer, then NC won’t be destroyed by some future incentive to hand over said Secret Keys.
— Semi-Reformed-Troll 🧌 #PoST #Grindr 🌱 🪙