I was talking about whether a single contract should be able to handle multiple address spaces. And my opinion at the moment is that the answer is no (at least in the short/medium term). What I was suggesting is that contracts should usually be able to migrate their user data to newer versions of the same contract anyway, so we could just as well say that each contract has an address space in the epoch where it was originally created and even that should be acceptable. You’re right though, there might be even better options, like auto-migrate the entire contract storage address space to a newer epoch when all individual items have been updated and present in more recent state trees. If it’s not a lot of complexity then that’s even better. Still, my point is that (at least in the first version) we should go with some version of (1), one contract should have one address space based in a single epoch.
↧