ERC/EIP-5298 ENS Trust to hold Tokens

EIPs
7

The debate between EIP-1363 vs EIP-4524 worth a separate debate, e.g.

  1. ERC721 and ERC1155 has established safeTransferFrom as a naming convention that EIP-1363 is ignoring and create a new name transferAndCall. If the transferAndCall function is being used to only verify the recipient account being a contract account
  2. If the transferAndCall function is being used anything other than verifying the recipient account being a contract account, I think there is a lot of limitations of EIP-1363 for example, the parameter choice and implied technical direction of EIP-1363 has significant restrictions, e.g.
  • the value of transfer(to, value, data) assume it can call the to but doesn’t support specifying ether Value which makes it not able to support general case of a remote function call that includes ethers required.
  • It also doesn’t support extra data so it couldn’t make a more flexible call
  • It doesn’t support a transfer call to specific which method inside of that recipient function to call, and restricting it to only onTransferReceived, renders it much less useful other than just verifying the recipient being an account, and instead introduced a lot of risk of re-entry attack.

In short, I am a bit hesitant to consider EIP-1363 ready to be massively adopted and thus hesitant to consider EIP-5298 to depend on EIP-1363.

I do see there are some value to consider how to support a further call function after claiming. I am not sure if EIP-5298 needs to be opinionated about such call function or could just leave the choice entirely to implementor