You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When EIP-7002 was designed, client teams had the option of calling an enshrined contract, or implementing it directly against state. When this was implemented, we chose the option of a direct implementation against the state. Since then, we've realized offering teams that choice opens up the potential for bugs, and when EIP-7251 is implemented it should be via the enshrined contract.
For consistency purposes, we should go back over the EIP-7002 implementation and alter it to be more consistent with future "requests" that are implemented via enshrined contracts.
Acceptance Criteria
EIP-7002 depends on enshrined contract.
The text was updated successfully, but these errors were encountered:
When EIP-7002 was designed, client teams had the option of calling an enshrined contract, or implementing it directly against state. When this was implemented, we chose the option of a direct implementation against the state. Since then, we've realized offering teams that choice opens up the potential for bugs, and when EIP-7251 is implemented it should be via the enshrined contract.
For consistency purposes, we should go back over the EIP-7002 implementation and alter it to be more consistent with future "requests" that are implemented via enshrined contracts.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: