Struct smart_wallet::CreateTransaction [−][src]
pub struct CreateTransaction<'info> {
pub smart_wallet: Account<'info, SmartWallet>,
pub transaction: Account<'info, Transaction>,
pub proposer: Signer<'info>,
pub payer: Signer<'info>,
pub system_program: Program<'info, System>,
}Expand description
Accounts for smart_wallet::create_transaction.
Fields
smart_wallet: Account<'info, SmartWallet>The SmartWallet.
transaction: Account<'info, Transaction>The Transaction.
proposer: Signer<'info>One of the owners. Checked in the handler via SmartWallet::owner_index.
payer: Signer<'info>Payer to create the Transaction.
system_program: Program<'info, System>The System program.
Trait Implementations
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. Read more
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. Read more