Struct crate_token::Issue [−][src]
pub struct Issue<'info> {
pub crate_token: Account<'info, CrateToken>,
pub crate_mint: Account<'info, Mint>,
pub issue_authority: Signer<'info>,
pub mint_destination: Account<'info, TokenAccount>,
pub author_fee_destination: Account<'info, TokenAccount>,
pub protocol_fee_destination: Account<'info, TokenAccount>,
pub token_program: Program<'info, Token>,
}
Expand description
Accounts for crate_token::issue.
Fields
crate_token: Account<'info, CrateToken>
Information about the crate.
crate_mint: Account<'info, Mint>
Mint of the CrateToken.
Authority of the account issuing Crate tokens.
mint_destination: Account<'info, TokenAccount>
Destination of the minted tokens.
Destination of the author fee tokens.
protocol_fee_destination: Account<'info, TokenAccount>
Destination of the protocol fee tokens.
token_program: Program<'info, Token>
Token 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