ChainStorageContainer.md

ChainStorageContainer

ChainStorageContainer

The Chain Storage Container provides its owner contract with read, write and delete functionality. This provides gas efficiency gains by enabling it to overwrite storage slots which can no longer be used in a fraud proof due to the fraud window having passed, and the associated chain state or transactions being finalized. Three distinct Chain Storage Containers will be deployed on Layer 1: 1. Stores transaction batches for the Canonical Transaction Chain 2. Stores queued transactions for the Canonical Transaction Chain 3. Stores chain state batches for the State Commitment Chain

Methods

deleteElementsAfterInclusive

function deleteElementsAfterInclusive(uint256 _index) external nonpayable

Removes all objects after and including a given index. Also allows setting the global metadata field.

Parameters

Name	Type	Description
_index	uint256	Object index to delete from.

get

function get(uint256 _index) external view returns (bytes32)

Retrieves an object from the container.

Parameters

Name	Type	Description
_index	uint256	Index of the particular object to access.

Returns

Name	Type	Description
_0	bytes32	32 byte object value.

getGlobalMetadata

function getGlobalMetadata() external view returns (bytes27)

Retrieves the container's global metadata field.

Returns

Name	Type	Description
_0	bytes27	Container global metadata field.

length

function length() external view returns (uint256)

Retrieves the number of objects stored in the container.

Returns

Name	Type	Description
_0	uint256	Number of objects in the container.

libAddressManager

function libAddressManager() external view returns (contract Lib_AddressManager)

Returns

Name	Type	Description
_0	contract Lib_AddressManager	undefined

owner

function owner() external view returns (string)

Returns

Name	Type	Description
_0	string	undefined

push

function push(bytes32 _object) external nonpayable

Pushes an object into the container. Function allows setting the global metadata since we'll need to touch the "length" storage slot anyway, which also contains the global metadata (it's an optimization).

Parameters

Name	Type	Description
_object	bytes32	A 32 byte value to insert into the container.

resolve

function resolve(string _name) external view returns (address)

Resolves the address associated with a given name.

Parameters

Name	Type	Description
_name	string	Name to resolve an address for.

Returns

Name	Type	Description
_0	address	Address associated with the given name.

setGlobalMetadata

function setGlobalMetadata(bytes27 _globalMetadata) external nonpayable

Sets the container's global metadata field. We're using bytes27 here because we use five bytes to maintain the length of the underlying data structure, meaning we have an extra 27 bytes to store arbitrary data.

Parameters

Name	Type	Description
_globalMetadata	bytes27	New global metadata to set.