perf: optimizing parameters sizing

[AuHau]

I ran into yet another instance where we were using uint256 for a time interval (duration, expiry, etc.), which does not make sense and makes working with these parameters in nim-codex more annoying, so my patience ran out, and I scaled down all the time relevant params to uint64. And since I was at it, I also started to look into others like slotSize and slots. I scaled those to uint64 as well. The slots (eq. number of slots in storage request) is IMHO fine having uint64, but the slotSize gives us 16 exabytes, which is IMHO also fairly alright.

I would like to point out, that with these changes and the reshuffling of the order in Ask we are saving 3x uint256, as the 4*uint64 will fit into one "word" (eq. uint256).

Let me know what you think about these changes ;-)

[markspanbroek]

Nice, thanks for fixing this @AuHau!

[AuHau]

@markspanbroek I did more optimisations, could you please re-review? Since I will be going over nim-codex anyhow, I would prefer to do it in one complex sweep so we do not have to return to this later on.

[markspanbroek]

Nice, looks good @AuHau!

[emizzle]

Thanks for doing this, Adam. It's a long overdue change.

Agree with Mark's comment on changed requestEnd. And two other function signature updates (both _slotPayout overloads).

Will approve as these are small changes.

[emizzle]

Ready to merge @AuHau ?

[AuHau]

No, there is no nim-codex counterpart yet.