The contract call is going to take 2 different tokens from a user and send the user an unassociated token that has already been created on the network. The user must grant token allowances first and associate the receivable token, or the contract will revert.
The contract call is going to take 2 different tokens from a user and send the user an unassociated token that will be created in the contract call. The user must grant token allowances first and have an available auto association slot, or the contract will revert.
Contract Call -> Contract Call
First contract call is an external contract. Second contract call is a contract validating the results of the first contract. The second contract will revert if the first contract does not produce the intended results. This could be a security enhancement and improve contract call extensibility.
Problem
HIP 551 highlights batch transactions. During the discussions examples were highlighted that could be captured by Smart Contract Scenarios
Solution
Add examples of common batch transactions using HTS calls
Additional considerations noted in https://github.com/hashgraph/hedera-improvement-proposal/pull/551#discussion_r1189004582 include Associate -> Contract Call
Allowance Approval -> Contract Call
Allowance Approval -> Allowance Approval -> Associate -> Contract Call
Allowance Approval -> Allowance Approval -> Account Update -> Contract Call
Contract Call -> Contract Call
Alternatives
No response