Investigate whether we can create a second MASP epoch tracker

[cwgoes]

h/t @gavinly

Investigate whether we can create a second MASP epoch, where masp_epoch = regular_epoch % n (mod n), where n could be, for example, 4 - the objective being to allow faster epochs without letting the conversion table grow too much.

[cwgoes]

@grarco any idea of how difficult this is?

[grarco]

We are still waiting for a confirmation on whether this is actually needed

[cwgoes]

A confirmation from whom?

[grarco]

@gavinly

[gavinly]

i'm ambivalent about prioritizing an epoch time decrease: it doesn't have to be a priority, but i'm concerned that it could be stuck like this forever, once it's the default (politically and/or dev priority). is there some in-between option that wouldn't require creating a second MASP epoch?

[cwgoes]

I don't think there's an in-between option. I also don't think this change is particularly complicated in principle, but it might be annoying in practice - @grarco do you have a rough idea (hours? days? weeks?)

[grarco]

I agree there's no other option. I'd say it takes a few days (but hard to say for certain until I start to work on this)

[cwgoes]

Let's revaluate this again next week after other definitely necessary work is completed.

[cwgoes]

@grarco to evaluate this in more detail today.