| Checked during execution | Approved policy stored onchain → | Users, teams, approval rules, contracts, tokens, price feeds, workflows, accounts, admin permissions, and pending changes are stored in smart contracts. |
|---|
| Checked during execution | Current approval rules → | Chainwall checks the latest onchain team membership and approval thresholds at execution. |
|---|
| Checked during execution | Approval tied to the exact action → | The operation fingerprint covers the calls, arguments, approval rule, deadline, value, operator, executor, and account where applicable. |
|---|
| Checked during execution | Only approved contracts → | Reusable workflows accept only the approved contracts recorded in the registry and stop if a required contract is missing. |
|---|
| Checked during execution | Protected account path → | Managed Safes block unsupported calls, while purpose-built Chainwall smart accounts accept execution only from their assigned Chainwall executor. |
|---|
| Configured governance | Delayed permission changes → | Sensitive settings can require extra approval and a waiting period. Anyone reviewing the registry can see whether a change is pending, ready, complete, canceled, or expired. |
|---|
| Operational assurance | Less trust in backend services → | The static browser console builds requests locally and reads onchain records, while smart contracts decide whether an action is allowed. |
|---|
| Operational assurance | Predictable contract addresses → | Chainwall calculates component addresses before deployment and refuses to finish setup if the deployed configuration produces different addresses. |
|---|