
Governance adapter
Market listings, oracle rotations, and supply-cap changes accept calls only from a small contract built for those actions and reached through an approved workflow.
Keep the protocol focused on its core job by exposing approved admin calls through small adapter contracts. Chainwall checks who may use them, which contracts they depend on, what approval is required, and whether a delay has passed.
Core contracts accept admin calls from a few limited entry points, where Chainwall checks whether the action and caller meet the current rules.

Market listings, oracle rotations, and supply-cap changes accept calls only from a small contract built for those actions and reached through an approved workflow.

Fee sweeps use a limited adapter that accepts only the recipient approved in the registry.

Emergency pause checks whether the caller currently holds one specific onchain permission, so the role can change without hard-coding a permanent admin address.
Give important dependencies a stable name in the registry: governance and treasury accounts, workflow runners, tokens, price feeds, and adapters. Changing the address behind a name becomes a visible, reviewable admin action.
northstar/dao-safenorthstar/treasury-safenorthstar/miniscriptnorthstar/wethnorthstar/oracle-maincap.northstar.pauseGive each admin task a transaction path with the permissions and checks it needs.
Use a MiniScript workflow for recurring actions such as listing markets, rotating oracles, and setting caps, with approved contracts and dependencies checked at execution.
Approve the precise calls for a fee sweep, treasury migration, position unwind, or reward transfer, naming a specific executor when needed.
In the test, an operator proposes a WETH market and an approver in the risk group authorizes it. The listing still fails because the catalog has no approved token record containing WETH and its registered price feed.
Scroll to explore the diagram →
Registered
Approved
Rejected
Admin change
Timelocked period
Retry
These tests exercise the real Chainwall contracts for approved policy, execution, workflows, account protection, approval rules, and delayed changes.
Guarded account bypass testA Safe protected by Chainwall rejects a direct proposal call that tries to skip the approved execution path.
Token + feed approval testA listing approved by two groups stays blocked until a separate write adds the token record with its registered price feed after operations and risk approval and a one-day wait.
Executor binding testThe treasury plan permits only the executor named in the approval to complete the sweep.
Put configurators, proxy admins, oracle admins, pause guardians, and rewards controllers behind Chainwall-protected accounts or limited adapters.
Give important tokens, price feeds, routers, rate models, treasuries, and adapters stable names in the registry.
Keep the protocol integration small: look up one approved address, check one permission, or trust one limited adapter.
Use reusable workflows for routine actions and exact plans for one-off actions.
Require stronger approval and real waiting periods when contracts, tokens, feeds, workflows, modules, or permissions change.
Name the executor when the identity of the final caller matters.
Protect the managed account so Safe owners and signers cannot bypass the reviewed path.
Monitor changes and waiting queues independently from the interface used to submit them.
What Chainwall checks, how it works with existing accounts, and how teams deploy it.
A protocol can integrate through a limited adapter, an approved-address lookup, or one dedicated permission check, with Chainwall handling approvals, waiting periods, and workflows.
A limited adapter exposes only the admin actions intended for that path. The Safe continues to hold funds and approvals, while Chainwall checks which adapter call, arguments, contracts, and approval rules are allowed.
Token review and price-feed approval establish facts beyond contract-address approval, and a market-listing workflow can require all three before execution.
Identify the admin calls, contracts, approval rules, waiting periods, and accounts that should sit behind a small Chainwall adapter or dedicated permission.