Struct MultisigConfig 

pub struct MultisigConfig<'info> {
    pub config_authority: Signer<'info>,
    pub rent_payer: Option<Signer<'info>>,
    pub system_program: Option<Program<'info, System>>,
    /* private fields */
}

Fields

config_authority: Signer<'info>

Multisig config_authority that must authorize the configuration change.

rent_payer: Option<Signer<'info>>

The account that will be charged or credited in case the multisig account needs to reallocate space, for example when adding a new member or a spending limit. This is usually the same as config_authority, but can be a different account if needed.

system_program: Option<Program<'info, System>>

We might need it in case reallocation is needed.

Implementations

impl MultisigConfig<'_>

pub fn multisig_add_member( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigAddMemberArgs, ) -> Result<()>

Add a member/key to the multisig and reallocate space if necessary.

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

pub fn multisig_remove_member( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigRemoveMemberArgs, ) -> Result<()>

Remove a member/key from the multisig.

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

pub fn multisig_change_threshold( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigChangeThresholdArgs, ) -> Result<()>

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

pub fn multisig_set_time_lock( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigSetTimeLockArgs, ) -> Result<()>

Set the time_lock config parameter for the multisig.

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

pub fn multisig_set_config_authority( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigSetConfigAuthorityArgs, ) -> Result<()>

Set the multisig config_authority.

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

pub fn multisig_set_rent_collector( ctx: Context<'_, '_, '_, '_, Self>, args: MultisigSetRentCollectorArgs, ) -> Result<()>

Set the multisig rent_collector and reallocate space if necessary.

NOTE: This instruction must be called only by the config_authority if one is set (Controlled Multisig). Uncontrolled Mustisigs should use config_transaction_create instead.

Trait Implementations

impl<'info> Accounts<'info, MultisigConfigBumps> for MultisigConfig<'info>

where 'info: 'info,

fn try_accounts( __program_id: &Pubkey, __accounts: &mut &'info [AccountInfo<'info>], __ix_data: &[u8], __bumps: &mut MultisigConfigBumps, __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 MultisigConfig<'info>

where 'info: 'info,

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

program_id is the currently executing program.

impl<'info> Bumps for MultisigConfig<'info>

where 'info: 'info,

type Bumps = MultisigConfigBumps

Struct to hold account bump seeds.

impl<'info> ToAccountInfos<'info> for MultisigConfig<'info>

where 'info: 'info,

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

impl<'info> ToAccountMetas for MultisigConfig<'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.