v0 source realm
View source
gno.land/r/nym-moultest123/config
The manager list for moul's realms: one place that answers "may this address administer my contracts", so the other realms do not each carry their own whitelist.
It is a thin realm around p/moul/authz. All state is
the single Authorizer.
1func AddManager(cur realm, addr address) error
2func RemoveManager(cur realm, addr address) error
3func TransferManagement(cur realm, newAuthority authz.Authority) error
4func ListManagers(cur realm) []address
5func HasManager(cur realm, addr address) bool
init refuses to run unless the caller is an EOA (cur.Previous().IsUserCall())
and seeds the authority with that address. AddManager and RemoveManager
only work while the authority is a MemberAuthority; once
TransferManagement hands control to something else (a DAO, a contract), they
return an error rather than silently bypassing the new authority.
Consumers should call HasManager and gate on the result. It is a read, so it
costs nothing beyond the cross-realm call.
Part of moul/gno-contracts — moul's versioned gno.land contracts. See the repository for the full catalog, build/test tooling, and usage.
Dependency graph:
⚠️ Disclaimer: provided as-is, without warranty; not security-audited. Full disclaimer: DISCLAIMER.
1
4
func AddManager
crossing ActionAddManager adds a new address to the list of authorized managers. This only works if the current authority is a MemberAuthority. The caller must be authorized by the current authority.
func HasManager
crossing Actionfunc RemoveManager
crossing ActionRemoveManager removes an address from the list of authorized managers. This only works if the current authority is a MemberAuthority. The caller must be authorized by the current authority.
func TransferManagement
crossing ActionTransferManagement transfers the authority to manage keys to a new authority. The caller must be authorized by the current authority.
Imports 2
/r/nym-moultest123/config/v0
