(address: string): Promise<void>

setKeystore

Proof Structure

The resulting update MUST have a block number equal to element.block.

After executing the transactions against all updates, the client MUST verify that the resulting state updates are all equivalent.

Next, the client MUST find all previously verified state updates that intersect with the range on the transations and where update.verifiedBlockNumber is equal to element.block - 1.

The provided transactions are used to compute the newer state update

This process effectively finds any state updates covered by the implicit range and “bumps up” the block to which they’re considered valid

This process will leave the client with a set of state updates that are entirely covered by the implicit range and ones that no longer intersect.

We’re only interested in these state updates because the implicit proof only applies to the element.block but not any previous blocks.

The client SHOULD check their local database for the deposit before querying Ethereum.

Otherwise, a client may not have the necessary information to verify a specific state transition.