Struct SubmitBid

pub struct SubmitBid<'info> {
    pub searcher: Signer<'info>,
    pub relayer_signer: Signer<'info>,
    pub permission: UncheckedAccount<'info>,
    pub router: UncheckedAccount<'info>,
    pub config_router: UncheckedAccount<'info>,
    pub express_relay_metadata: Account<'info, ExpressRelayMetadata>,
    pub fee_receiver_relayer: UncheckedAccount<'info>,
    pub system_program: Program<'info, System>,
    pub sysvar_instructions: UncheckedAccount<'info>,
}

Fields

searcher: Signer<'info>

relayer_signer: Signer<'info>

permission: UncheckedAccount<'info>

CHECK: this is the permission key. Often the permission key refers to an on-chain account storing the opportunity; other times, it could refer to the 32 byte hash of identifying opportunity data. We include the permission as an account instead of putting it in the instruction data to save transaction size via caching in case of repeated use.

router: UncheckedAccount<'info>

CHECK: don’t care what this looks like.

config_router: UncheckedAccount<'info>

CHECK: Some routers might have an initialized ConfigRouter at the enforced PDA address which specifies a custom routing fee split. If the ConfigRouter is unitialized we will default to the routing fee split defined in the global ExpressRelayMetadata. We need to pass this account to check whether it exists and therefore there is a custom fee split.

express_relay_metadata: Account<'info, ExpressRelayMetadata>

fee_receiver_relayer: UncheckedAccount<'info>

CHECK: this is just a PK for the relayer to receive fees at.

system_program: Program<'info, System>

sysvar_instructions: UncheckedAccount<'info>

CHECK: this is the sysvar instructions account.

Trait Implementations

impl<'info> Accounts<'info, SubmitBidBumps> for SubmitBid<'info>

where 'info: 'info,

fn try_accounts( __program_id: &Pubkey, __accounts: &mut &'info [AccountInfo<'info>], __ix_data: &[u8], __bumps: &mut SubmitBidBumps, __reallocs: &mut BTreeSet<Pubkey>, ) -> Result<Self>

Returns the validated accounts struct. What constitutes “valid” is program dependent. However, users of these types should never have to worry about account substitution attacks. For example, if a program expects a Mint account from the SPL token program in a particular field, then it should be impossible for this method to return Ok if any other account type is given–from the SPL token program or elsewhere.

impl<'info> AccountsExit<'info> for SubmitBid<'info>

where 'info: 'info,

fn exit(&self, program_id: &Pubkey) -> Result<()>

program_id is the currently executing program.

impl<'info> Bumps for SubmitBid<'info>

where 'info: 'info,

type Bumps = SubmitBidBumps

Struct to hold account bump seeds.

impl<'info> ToAccountInfos<'info> for SubmitBid<'info>

where 'info: 'info,

fn to_account_infos(&self) -> Vec<AccountInfo<'info>>

impl<'info> ToAccountMetas for SubmitBid<'info>

fn to_account_metas(&self, is_signer: Option<bool>) -> Vec<AccountMeta>

is_signer is given as an optional override for the signer meta field. This covers the edge case when a program-derived-address needs to relay a transaction from a client to another program but sign the transaction before the relay. The client cannot mark the field as a signer, and so we have to override the is_signer meta field given by the client.