Expand description
Storage backend implementations.
Structs§
- The FuelVM storage double key.
- The storage table for contract’s assets balances.
- The storage table for contract’s raw byte code.
- The storage table for contract’s hashed key-value state.
- Storage type for contract state
- The FuelVM storage double key.
- In-memory storage implementation for the interpreter.
- No-op storage used for predicate operations.
- The storage table for uploaded bytecode.
Enums§
- The uploaded bytecode can be in two states: fully uploaded or partially uploaded.
Traits§
- Storage operations for contract assets.
- When this trait is implemented, the underlying interpreter is guaranteed to have full functionality