Struct dharitri_wasm::contract_base::SendWrapper

pub struct SendWrapper<A>
where
    A: SendApi + ManagedTypeApi + StorageReadApi + BlockchainApi,
{ /* private fields */ }

API that groups methods that either send MOAX or DCT, or that call other contracts.

Implementations

impl<A> SendWrapper<A>

where A: SendApi + ManagedTypeApi + StorageReadApi + BlockchainApi,

pub fn dct_system_sc_proxy(&self) -> DCTSystemSmartContractProxy<A>

pub fn contract_call<R>( &self, to: ManagedAddress<A>, endpoint_name: ManagedBuffer<A> ) -> ContractCall<A, R>

pub fn direct_moax<D>( &self, to: &ManagedAddress<A>, amount: &BigUint<A>, data: D )

where D: ManagedInto<A, ManagedBuffer<A>>,

Sends MOAX to a given address, directly. Used especially for sending MOAX to regular accounts.

pub fn direct<D>( &self, to: &ManagedAddress<A>, token: &TokenIdentifier<A>, nonce: u64, amount: &BigUint<A>, data: D )

where D: ManagedInto<A, ManagedBuffer<A>>,

Sends either MOAX, DCT or NFT to the target address, depending on the token identifier and nonce

pub fn transfer_dct_via_async_call<D>( &self, to: &ManagedAddress<A>, token: &TokenIdentifier<A>, nonce: u64, amount: &BigUint<A>, data: D ) -> !

where D: ManagedInto<A, ManagedBuffer<A>>,

Performs a simple DCT/NFT transfer, but via async call.
As with any async call, this immediately terminates the execution of the current call.
So only use as the last call in your endpoint.
If you want to perform multiple transfers, use self.send().transfer_multiple_dct_via_async_call() instead.
Note that MOAX can NOT be transfered with this function.

pub fn transfer_multiple_dct_via_async_call<D>( &self, to: &ManagedAddress<A>, payments: &ManagedVec<A, DctTokenPayment<A>>, data: D ) -> !

where D: ManagedInto<A, ManagedBuffer<A>>,

pub fn change_owner_address( &self, child_sc_address: ManagedAddress<A>, new_owner: &ManagedAddress<A> ) -> ContractCall<A, ()>

Sends a synchronous call to change a smart contract address.

pub fn call_local_dct_built_in_function( &self, gas: u64, endpoint_name: &ManagedBuffer<A>, arg_buffer: &ManagedArgBuffer<A> ) -> ManagedVec<A, ManagedBuffer<A>>

Allows synchronously calling a local function by name. Execution is resumed afterwards. You should never have to call this function directly. Use the other specific methods instead.

pub fn dct_local_mint( &self, token: &TokenIdentifier<A>, nonce: u64, amount: &BigUint<A> )

Allows synchronous minting of DCT/SFT (depending on nonce). Execution is resumed afterwards. Note that the SC must have the DCTLocalMint or DCTNftAddQuantity roles set, or this will fail with “action is not allowed” For SFTs, you must use self.send().dct_nft_create() before adding additional quantity. This function cannot be used for NFTs.

pub fn dct_local_burn( &self, token: &TokenIdentifier<A>, nonce: u64, amount: &BigUint<A> )

Allows synchronous burning of DCT/SFT/NFT (depending on nonce). Execution is resumed afterwards. Note that the SC must have the DCTLocalBurn or DCTNftBurn roles set, or this will fail with “action is not allowed”

pub fn dct_nft_create<T: TopEncode>( &self, token: &TokenIdentifier<A>, amount: &BigUint<A>, name: &ManagedBuffer<A>, royalties: &BigUint<A>, hash: &ManagedBuffer<A>, attributes: &T, uris: &ManagedVec<A, ManagedBuffer<A>> ) -> u64

Creates a new NFT token of a certain type (determined by token_identifier).
attributes can be any serializable custom struct.
This is a built-in function, so the smart contract execution is resumed after. Must have DCTNftCreate role set, or this will fail with “action is not allowed”. Returns the nonce of the newly created NFT.

pub fn sell_nft( &self, nft_id: &TokenIdentifier<A>, nft_nonce: u64, nft_amount: &BigUint<A>, buyer: &ManagedAddress<A>, payment_token: &TokenIdentifier<A>, payment_nonce: u64, payment_amount: &BigUint<A> ) -> BigUint<A>

Sends thr NFTs to the buyer address and calculates and sends the required royalties to the NFT creator. Returns the payment amount left after sending royalties.