OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

Delegation Framework

Delegation Framework is an Apache-2.0-licensed Solidity contract framework for DeleGator smart accounts compatible with ERC-4337. It includes account cores, implementations, a Delegation Manager and Caveat Enforcer contracts for validating delegated onchain actions and applying restrictions.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Delegation Framework — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the framework when developing Solidity smart accounts that need delegation and ERC-4337 functionality, especially when delegated authority must be limited through caveats.

Who it is for

  • Solidity developers building delegation-enabled smart accounts.
  • Teams implementing custom DeleGator account logic or signature schemes.
  • Developers creating caveat enforcers or crafting restricted delegations for onchain actions.

Documented uses

  • Build a DeleGator smart account using its core and an implementation.
  • Share authority to invoke onchain actions through delegations.
  • Apply restrictions to delegated actions with caveats and Caveat Enforcer contracts.
  • Develop custom account implementations or contracts that meet the DeleGator Core interface.
  • Build and test the contracts with Foundry, or prepare an RPC-based deployment environment.
Before you choose

Requirements & limits

The framework is available as a public GitHub repository under the Apache-2.0 license. Its README documents Foundry and Solidity 0.8.23.

  • A DeleGator proxy uses a selected implementation, so account behavior and signature verification depend on the implementation chosen or built.
  • The README says delegations allow any onchain action by default and strongly recommends caveats to add restrictions.
  • The EIP-7702 DeleGator Core variant omits UUPS proxy functionality.
  • The README distinguishes tagged audited code releases from the working main branch.
  • Deployment preparation involves environment variables and an RPC URL; scripts using a private key require it.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a local repository branch

Fork the framework, clone your fork and create a working branch for changes.

Before you start

  • A Git installation
  • A GitHub account to fork the repository

Steps

  1. Fork the MetaMask/delegation-framework repository.

  2. Clone your fork with the command below.

    Documented command
    git clone https://github.com//delegation-framework.git

  3. Create a working branch with the command below.

    Documented command
    git checkout -b feat/example-branch

Expected outcome

A local copy of your fork checked out on a separate working branch.

Guide limitations

  • This setup sequence does not build, test or deploy the contracts.
  • The README identifies main as the working development branch and says pull requests should be based against it.
Documentation 1 ↗
Source-based practical guide

Prepare the documented deployment environment

Configure environment variables and an RPC environment before selecting a documented deployment script.

Before you start

  • Foundry
  • An .env.example file copied to .env and populated for the intended deployment scripts
  • An RPC URL; for local fork-based development, Anvil and a blockchain RPC URL
  • A private key for scripts that require it

Steps

  1. Copy .env.example to .env and populate the variables required by the deployment scripts you plan to execute.

  2. Load the environment with source .env.

  3. For local fork-based development, start Anvil with anvil -f ; otherwise obtain the RPC URL for deployment.

  4. Review the deployment documentation and select the relevant script for the contracts required.

Expected outcome

The documented environment is prepared for local fork-based development or for proceeding to a selected deployment script.

Guide limitations

  • This guide stops before executing a deployment; it does not establish that deployment will succeed.
  • The repository notes deployment may no longer be required on public chains where DeleGator is in use.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
MetaMask/delegation-framework · Official homepage title · retained in its source language
How we review sourcesSuggest a correction