Skip to content
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

Open
anorth opened this issue Feb 18, 2020 · 1 comment
Open

More general actor address/code validation mechanism #178

anorth opened this issue Feb 18, 2020 · 1 comment
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

Comments

@anorth
Copy link
Member

anorth commented Feb 18, 2020

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.

@anorth anorth added enhancement New feature or request P3 Not urgent or important labels Feb 18, 2020
@anorth
Copy link
Member Author

anorth commented Jun 29, 2020

#94 suggests a declarative mechanism rather than the current procedural one.

@ZenGround0 ZenGround0 added change-behaviour Changes behaviour or state interpretation, necessitating a network version upgrade robustness Related to correctness labels Oct 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Projects
None yet
Development

No branches or pull requests

2 participants