@juanblanco

At the integration layer it could be abstracted by matching the ABI representation (JSON or custom) to SSZ, so call data could be "easy" for an end user, but it would impossible to have a big bang approach, as it will break many applications. The only solution is to support both in parallel, the user now will need to be aware of the smart contract type (ie ERC20 ssz) they are targeting and what encoding to use. This adds a similar issue with event decoding that might require a flag to identify the format for decoding. 712, SIWE, Permit2, and just internal smart contract ABI encoding/decoding with integrations will remain the same as the ABI is used as a standard in these scenarios (packed or unpacked) as utility internally and for integration. So it will be very hard to be phased out.

0 reply

0 recast

0 reaction