User Flow
User Transaction scheme TL-B
// struct for mint_request
mint_request$_ {
message:IncomingMessage
ton_amount:uint64
prices_packed:^Cell
} = MintRequest;
// struct for mint_process
mint_process$_ {
op:uint32
query_id:uint64
sender_address:MsgAddress
prices_packed:^Cell
ton_amount:uint64
last_invoke:uint32
deposited_ton:uint64
synt_minted:uint64
} = MintProcess;
// struct for mint_success
mint_success$_ {
message:IncomingMessage
synts_amount_to_mint:uint64
last_invoke:uint32
ton_amount:uint64
next_epoch_index:uint16
next_fees_epoch_started_at:uint32
} = MintSuccess;
This scheme describes about mint body in process transaction. And we have example from transaction scanner:
Transaction can started from init mint transaction and give request to jetton_minter. So, if jetton_wallet doesn't exist jetton_minter create new Syde jetton_wallet. Native wallet can take some tons who can exist in mint transaction. If tons enough transaction successfully finish and give your synths. If tons not enough transaction bounced and tons give sender back.
This scheme describes about mint body in process transaction. And we have example from transaction scanner:
Transaction can started from init burn transaction and give request to jetton_minter. Next step is checking exist of jetton_wallet. Native wallet can take some tons who can exist in burn transaction. If tons and synth enough transaction successfully finish and give your ton's. If tons not enough transaction bounced and synth give sender back.
Last updated