Add "data" parameter to all mint/transfer methods

[awrichar]

When performing token transfers, it's often beneficial to include additional data alongside the transfer. This can be to indicate the reason for the transfer, to tie it to an off-chain transaction, or to provide special instructions to derived token variants without altering the original contract interface.

One way to achieve this is by adding a bytes data parameter to the method signature, which is common in the Ethereum community and was codified in ERC-5750. Many existing standards, including ERC-721, ERC-1155, and ERC-1400 (specifically the ERC-1594 component) all conform to this pattern.

I'd like to propose that Zeto also adopt this pattern and add bytes data to each of its mint/transfer methods and events. This does represent a change to the signatures.

Note: There are other ways to allow similar functionality without changing the existing signatures (such as with method overloading, or emitting multiple events instead of only one) - but in my opinion the proposed route would be the cleanest and most consistent with other current token standards.

[jimthematrix]

ERC 5750 seems to suggest that a overloading pattern of having and not having the data parameter for the same function is recommended. But I agree with Andrew that it feels overly complicated. If an application does not make use of the data parameter, passing "0x" is simply enough and incurs close to zero cost.