The same storage declaration will be able to call the storage interfaces of solidity contracts, this is for writing zink as tests of solidity contracts
reserve first 64 bytes instead of 96 bytes, however whatever 96 or 64 bytes could be a dynamic solution in the future, if the contract only has storage value, the reserved memory should be 32, if the contract has no storage, reserved memory should be zero, etc.
Changes
[x] re-order hash key components of mappings
[x] re-order hash key components of double key mappings
Resolves #242 ref #166
96
or64
bytes could be a dynamic solution in the future, if the contract only has storage value, the reserved memory should be32
, if the contract has no storage, reserved memory should be zero, etc.Changes