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
{{ message }}
This repository has been archived by the owner on Apr 27, 2022. It is now read-only.
Define the role of "owner" of the contract, which is expected to appoint and dismiss solvers.
Define the role of "solver", who can call the settle function.
The text was updated successfully, but these errors were encountered:
Could implement a contract exposing a function canSolve(address) -> bool that the settlement contract can call into to determine is the solver is allowed. Sort of like a curated list. This could eventually be replaced with a staking and slashing mechanism
@josojo and I have a brief discussion on Slack, this is how we imagined it:
We have a contract called SolverAllowList. This contract can have any owner and maybe even a proxy infrastrucutre. The dao is the owner and manages all solvers within this SolverAllowList contract.
The settlement contract has a modifier onlySolver and this modifier calls into the SolverAllowList
to check whether a solver is allowlisted.
In this case, the settlement contract does not have an owner at all.
Define the role of "owner" of the contract, which is expected to appoint and dismiss solvers.
Define the role of "solver", who can call the
settle
function.The text was updated successfully, but these errors were encountered: