Requests
As mentioned in the Overview, Strategists must write their own code for interacting with Steward leveraging the protobuf definitions. The main request type in the Steward API is ScheduleRequest
, which is used to pass call data parameters to Steward which will then be built into the actualy contract call data. The request proto defintion can be found here.
Definition
Fields
block_height
: The Sommelier block height at which a bridge transaction will be created. This is when the bridging process begins, not when the EVM transaction is executed. There is an inherent delay between the time of this height and actualy transaction execution on the target contract.call_data
: The payload of contract call parameters. A detailed reference of theCellarV2_5
type and its function definitions can be found in the Cellar Functions section.cellar_id
: The ID of the target Cellar, which is its EVM address. The address does not need to be checksummed (EIP-55) as the chain ID will provide target chain information.chain_id
: For non-Ethereum Cellars only. The EVM ID of the chain where the target Cellar resides. The default is 1, which is Ethereum Mainnet. Axelar provides a reference for other Mainnet chain IDs here.deadline
: For non-Ethereum Cellars only. This is the unix timestamp deadline for the contract call to be executed by Axelar. If Axelar fails to relay the transaction before the deadline it will not be executed. This field will be ignored for Ethereum Cellars.
Last updated