Struct add_decimals::InitializeWrapper
source · [−]pub struct InitializeWrapper<'info> {
pub wrapper: Account<'info, WrappedToken>,
pub wrapper_underlying_tokens: Account<'info, TokenAccount>,
pub underlying_mint: Account<'info, Mint>,
pub wrapper_mint: Account<'info, Mint>,
pub payer: Signer<'info>,
pub rent: Sysvar<'info, Rent>,
pub system_program: Program<'info, System>,
}Expand description
Accounts for initializing a new wrapper.
Fields
wrapper: Account<'info, WrappedToken>The WrappedToken account.
wrapper_underlying_tokens: Account<'info, TokenAccount>Token account containing the underlying tokens.
underlying_mint: Account<'info, Mint>Mint of the underlying token.
wrapper_mint: Account<'info, Mint>Mint of the wrapper.
payer: Signer<'info>Payer of the newly created decimal wrapper.
rent: Sysvar<'info, Rent>Rent sysvar. Required for initialization.
system_program: Program<'info, System>System program. Required for initialization.
Implementations
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