Call policy allows you to filter out transactions based on the call data and ether value.Within a policy, you can set up to 16 rules. Each rule consists of a condition, the calldata offset, and a reference value to compare.When checking a transaction, the policy checks it against every rule. For a policy to accept a transaction, every rule of that policy should pass.
The number of bytes to offset from the start (excluding the function selector).The resulting value is a hex string of 32 bytes.In other words, if the offset is 10, the compared value will be formed from the calldata with the starting index of 4 + 10 = 14 and an end index of 4 + 10 + 32 = 46.
Value to compare the calldata against.The reference value is a hex string of 32 bytes. For convenience, you can pass the hex string of a smaller length or a bigint, and the SDK will convert it for you.
You can limit the total accumulated value of a param across all session uses.This can be helpful if you want to e.g. limit the total value of tokens passed through the session.
Together with an ERC20 transfer action, this will limit the token transferred to 10 USDC per session use, and 50 USDC for a total lifespan of the session.