If you’re about to sign a swap or an approval, first check whether the page can constrain the outcome.
Verified fact: EIP-7906 does not require transactions to include an assertion, so whoever builds the transaction can leave it out.
My take: This changes one specific choice: understanding “what it’s going to do” doesn’t mean the “minimum acceptable outcome after it’s done” is protected. Even if you see EIP-7906, don’t assume protection is already in place. First check whether the page can specify a minimum amount to receive, a maximum amount to spend, or permissions that must not change.
You can: Look for outcome constraints and permission scopes on the confirmation page. If it shows only an expected outcome, with no verifiable constraints, don’t increase the amount or expand the scope of the approval yet.
What to check: Later, see whether the wallet includes an EIP-7906 assertion in the transaction and can block execution if the outcome crosses the specified limit. If it can’t, continue treating this as something that needs verification.
Verified fact: EIP-7906 does not require transactions to include an assertion, so whoever builds the transaction can leave it out.
My take: This changes one specific choice: understanding “what it’s going to do” doesn’t mean the “minimum acceptable outcome after it’s done” is protected. Even if you see EIP-7906, don’t assume protection is already in place. First check whether the page can specify a minimum amount to receive, a maximum amount to spend, or permissions that must not change.
You can: Look for outcome constraints and permission scopes on the confirmation page. If it shows only an expected outcome, with no verifiable constraints, don’t increase the amount or expand the scope of the approval yet.
What to check: Later, see whether the wallet includes an EIP-7906 assertion in the transaction and can block execution if the outcome crosses the specified limit. If it can’t, continue treating this as something that needs verification.