Treat encoded swap calldata as a versioned artifact

Encoded swap calldata should travel through an application as a versioned artifact. Editing a byte sequence because an address or amount appears inside it can corrupt offsets, signatures or nested commands.

The Solidity ABI specification explains that encoded data requires a schema to interpret it and that dynamic values use offsets. Even a correctly decoded outer function may contain opaque nested bytes governed by another encoding.

Separate inspection from modification

Use a decoder matched to the target deployment and interface version when you need to inspect arguments. Record which decoder produced the interpretation. A failed decode means the application lacks an interpretation; it does not prove the transaction is harmless or malicious.

For a normal API integration, request changed terms from the provider rather than patching the returned payload. A new recipient, minimum output or route generally belongs in a new build request.

Validate what surrounds the bytes

Check chain, execution destination, sender and native value against the active quote. Confirm that the payload has the expected hexadecimal form and that its association with the user-reviewed request has not changed.

Some protocols explicitly require a documented assembly step, such as attaching a signature. Isolate that step in a versioned adapter with byte-level fixtures. Its existence is not permission to rewrite other parts of the payload.

Use integrity records carefully

A local digest can detect accidental mutation between review, simulation and submission. It cannot prove the underlying transaction is safe. Store the digest with the quote generation and execution envelope so it describes the complete reviewed artifact.

Test a changed destination with identical calldata, an altered native value, truncation and a stale decoder version. These cases demonstrate why a familiar function selector or unchanged byte length is insufficient validation.