You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two instructions for storage operations in EVM
opcode
instruction
input
output
0x54
sload
key
value
0x55
sstore
key, value
both key and value should be 32-byte, but in the current implementation, we are using i64 for the them, which will be compiled to i64 directly in WASM
not using [u8; 32] or [u64; 4] even U256 in the interfaces for now in library zink is because it is hard to be passed to WASM directly at the moment xdd WASM only has number types i32, i64, f32, f64, an array type could increase the complexity of the implementation #110
Solution
No response
The text was updated successfully, but these errors were encountered:
Describe the feature
There are two instructions for storage operations in EVM
0x54
sload
key
value
0x55
sstore
key
,value
both
key
andvalue
should be32-byte
, but in the current implementation, we are usingi64
for the them, which will be compiled toi64
directly in WASMnot using
[u8; 32]
or[u64; 4]
evenU256
in the interfaces for now in libraryzink
is because it is hard to be passed to WASM directly at the moment xdd WASM only has number typesi32
,i64
,f32
,f64
, an array type could increase the complexity of the implementation #110Solution
No response
The text was updated successfully, but these errors were encountered: