Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
owner_address
— address of the contract owner who can update settingscontract_address
— address of the smart contract to update settings forconsume_user_resource_percent
— percentage (0-100) of caller’s resources to consumevisible
— boolean indicating whether to use visible (Base58) address format instead of hex
Response
visible
— boolean indicating whether addresses are in visible formattxID
— unique transaction ID for the setting update transactionraw_data
— raw transaction data containing:contract
— array with contract update detailsref_block_bytes
— reference block bytes for transaction validationref_block_hash
— hash of the reference blockexpiration
— transaction expiration timestamptimestamp
— transaction creation timestamp
raw_data_hex
— complete transaction data encoded in hexadecimal format
Use case
Thewallet/updatesetting
method is used for:
- Adjusting resource consumption patterns for smart contract execution.
- Optimizing contract costs by controlling user vs contract owner resource usage.
- Managing energy and bandwidth allocation between contract and users.
- Implementing different pricing models for contract interactions.
- Fine-tuning contract economics and user experience trade-offs.
- Setting up contracts to be more or less resource-friendly to callers.
Only the contract owner can update the consume user resource percentage. Setting this to 100 means all resources come from the caller, while 0 means all resources come from the contract owner. The default is typically 100.
Body
application/json
Address of the contract owner
Address of the smart contract
Percentage (0-100) of caller's resources to consume
Required range:
0 <= x <= 100
Whether to use visible (Base58) address format