Protected smart accounts
Create a smart account per client, product or agent. Use a signer of your choice: MPC, multisig, cold or hot wallet.
Set your control and execution layer with protected smart accounts, catalog of authorized actions and policy rules for how assets can move.
Uses the public Chainwall demo catalog. Funding and execution are simulated in your browser.
Try a team treasury or a stablecoin protocol with the official Chainwall CLI skill.
Give two operators approved lending actions. Require a risk review for each operation and both admins for changes to the rules.
We are a team of 5: 2 admins, 2 treasury operators, and 1 risk reviewer. We want to earn onchain yield on 1,000,000 USDC through Aave and Morpho on Arbitrum One. Use the official Chainwall CLI and its chainwall-operations skill to prepare an account, approved lending actions, spending limits, and approval rules. Build and test the setup before asking us to approve deployment or funding.
The full brief includes five team roles, concrete rules, fork tests, and a deployment review.Separate Alice and Ben's admin powers, Cara and Diego's operations, and Erin's risk approvals.
Verify Aave and Morpho deployments, fix the account receiving assets, and bound token allowances.
Require an operator and Erin for lending actions. Test per-operation and daily limits across both protocols.
Test deposits, withdrawals, rejected calls, and recovery on a fork before reviewing live transactions.
Create a smart account per client, product or agent. Use a signer of your choice: MPC, multisig, cold or hot wallet.
Create an onchain registry of authorized users, groups, policies, and an onchain catalog of pre-approved actions. Use timelocks for sensitive system changes.
Use scripts to program constraints, add restriction rules into your policies. Program authorized action bundles for atomic execution, limit dust and protect from MEV.
Use the libraries, documentation, and deployment skill to set up your account and rules.
Main repo includes the Registry for authorized users, groups, catalog, contracts, policies, and actions management, the Execution Layer that verifies each action against current policy before execution, and timelocked governance for sensitive changes.
GitHubUse the CLI and agent skill to deploy your Chainwall instance on Arbitrum One mainnet. Set approved contracts, policies, and waiting periods for sensitive changes.
GitHubCopy a setup brief into your coding agent. It guides instance deployment on Arbitrum One, account setup, permissions, and tests. Review the configuration and transactions before deployment.
For configured execution paths, Chainwall checks the operator, approved contracts, exact action, and current approval rules. Sensitive changes can require separate approval and a waiting period. Approved protocols, your strategy code, and key custody still carry risks. Account configuration must prevent paths that bypass these checks.
Chainwall supports EVM chains. The CLI and agent skill linked here target Arbitrum One mainnet (chain ID 42161).
Chainwall provides its own smart account with programmable policies, so a new vault can start there. If you already use Safe, Chainwall also supports a protected Safe configuration. Teams comparing a Safe setup with Zodiac Roles Modifier can evaluate Chainwall for the account, approvals, and reusable operations together.
Chainwall provides the underlying account and controls for strategy operations. You add the ERC-4626 contract and its accounting, deposits, and withdrawal logic. That integration still needs tests and review.
Yes. MPC can remain your signing setup, and simulations can help you review transactions. Chainwall checks the configured policies onchain at execution. It does not require an MPC subscription.
Chainwall can be used under the Business Source License 1.1 (BUSL-1.1). Follow the license terms when using, modifying, or creating derivative works. Production use is permitted through official factories and their unmodified deployments, as defined in the license. Other production uses require a separate commercial license while BUSL applies. Under the current protocol terms, Chainwall charges no protocol service fees. You remain responsible for network gas and any third-party fees. Chainwall also offers a subscription plan for standard procurement, support, and deployment help.
Supported by