To simplify significantly the implementation of the Immutable Storage, I suggest enforcing these rules upon each Template:
Each Template must have Storage Layout Section #0. Its usage is to describe the Immutable Storage of each Account. If there is no Immutable Storage then the Storage Layout will be empty (but it'll still exist).
There'll be exactly one Storage Layout Section targeting the Immutable Storage of each future Account spawned out of this Template.
To simplify significantly the implementation of the
Immutable Storage
, I suggest enforcing these rules upon each Template:Each Template must have
Storage Layout Section #0
. Its usage is to describe theImmutable Storage
of eachAccount
. If there is noImmutable Storage
then theStorage Layout
will be empty (but it'll still exist).There'll be exactly one
Storage Layout Section
targeting theImmutable Storage
of each futureAccount
spawned out of thisTemplate
.This issue extends the code under
Runtime::validate_deploy
to assert the above https://github.com/spacemeshos/svm/blob/6edb73de199fafce0953f82af061ca1090ff911c/crates/runtime/src/runtime/runtime.rs#L521