This repository has been archived by the owner on Jun 6, 2023. It is now read-only.
More general actor address/code validation mechanism #178
Labels
change-behaviour
Changes behaviour or state interpretation, necessitating a network version upgrade
enhancement
New feature or request
P3
Not urgent or important
robustness
Related to correctness
The runtime currently has a few methods for validating caller address and/or code type. The runtime requires that at least one method is called. The interface would be better with a single validation method and an abstract pattern type for declaring the desired pattern.
This would also allow use of the runtime-provided matching mechanism for uses beyond caller validation, such as validating explicitly-provided addresses.
cc @icorderi who has some code for this lying around.
The text was updated successfully, but these errors were encountered: