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 →Budget permissions and storage
Identify token registration and key permissions before a first DeFi interaction.
An app can ask for more than a token amount. Understand its storage and permission requests too.
Know the token contract
NEAR's fungible token standard records token balances in a token contract, rather than in one universal native balance field. Contracts use storage management for account registration where required. Identify the token contract and whether the receiving account is registered before assuming a displayed token can be transferred or used by an app.
Separate storage from execution
Native tokens back stored state through storage staking; execution gas is separate. Check the application's current storage charges and refunds. Independently review any requested access key, pausing if you cannot explain its scope.
Prepare a registration review
Read a token contract's public documentation without connecting a wallet.
- Record the token contract ID and the network.
- Find its account-registration or storage-management instructions.
- Write separate questions about storage cost, gas and the requested key permission.
Separate questions make a combined app prompt easier to assess.
Check the token contract, storage terms and permission scope before first use.
Kemajuan disimpan pada peranti ini.
Perpustakaan sumber
Disemak