Menyemak sokongan bacaan suara pada pelayar ini…
Bacaan ini kini tersedia dalam bahasa Inggeris. Antara muka menggunakan bahasa pilihan anda.
Baca teks asal bahasa Inggeris →Prepare a TRC-20 interaction
Inspect contract identity, spender allowances and resource requirements before trading.
An application can ask for permission to use a token before it asks for a swap.
An allowance names a spender
TRC-20's approve, allowance and transferFrom methods govern spender access to token amounts. An approval changes permission; it is not the swap. Review the token contract, spender and amount instead of accepting a broad allowance on the strength of a familiar ticker.
Check resources before a contract action
A contract call consumes Energy as well as transaction Bandwidth. How those costs are paid depends on available resources and the call's conditions. Read a current estimate and leave unanswered resource questions visible. Holding the intended trading token does not prove the account can pay for the contract interaction.
Review a fictional approval
Use a mock record with a token contract, spender and allowance. Do not sign it.
- Mark which address identifies the token and which would receive spending permission.
- Compare a limited intended amount with a much larger proposed allowance.
- List the Energy, Bandwidth and current cost checks needed before a later real action.
Permission scope and transaction cost are separate parts of a trade preparation.
Identify the contract, inspect the spender and understand resource costs before signing.
Kemajuan disimpan pada peranti ini.
Perpustakaan sumber
Disemak