[ ] https://github.com/codex-storage/nim-codex/issues/602 More info: maxCollateralPerByte – instead of SP setting their maxCollateralPerByte, they would set their max storage size and max collateral. maxCollateralPerByte can then be calculated by storage available/collateral available. After each slot is serviced, the value would be recalculated for the next availability matching.
@emizzle I have renamed the epic ("collateral" -> "contract") as while it tackles some of the collateral issues, it also tackles some general contract related issues ;-) Let me know if you think otherwise!