Struct squads_multisig_program::accounts::ConfigTransactionExecute

pub struct ConfigTransactionExecute {
    pub multisig: Pubkey,
    pub member: Pubkey,
    pub proposal: Pubkey,
    pub transaction: Pubkey,
    pub rent_payer: Option<Pubkey>,
    pub system_program: Option<Pubkey>,
}

Generated client accounts for ConfigTransactionExecute.

Fields

multisig: Pubkey

The multisig account that owns the transaction.

member: Pubkey

One of the multisig members with Execute permission.

proposal: Pubkey

The proposal account associated with the transaction.

transaction: Pubkey

The transaction to execute.

rent_payer: Option<Pubkey>

The account that will be charged/credited in case the config transaction causes space reallocation, for example when adding a new member, adding or removing a spending limit. This is usually the same as member, but can be a different account if needed.

system_program: Option<Pubkey>

We might need it in case reallocation is needed.

Trait Implementations

impl BorshSerialize for ConfigTransactionExecutewhere Pubkey: BorshSerialize, Option<Pubkey>: BorshSerialize,

fn serialize<W: Write>(&self, writer: &mut W) -> Result<(), Error>

fn try_to_vec(&self) -> Result<Vec<u8, Global>, Error>

Serialize this instance into a vector of bytes.

impl ToAccountMetas for ConfigTransactionExecute

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.