morph-7702

Manage EIP-7702 EOA delegations and execute atomic delegated transactions on Morph L2.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill morph-7702
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morph-7702
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/morph/vendor/morph-7702
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill morph-7702

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, eth_account, eth_abi, eth_utils, and includes scripts (resource) components.

What problem does it solve?

Enables externally owned accounts (EOAs) on Morph L2 to delegate authority and execute authorized transactions atomically using EIP-7702, removing manual multi-tx workflows and simplifying approve+swap+transfer operations while preserving replay protection and delegation lifecycle control.

Core Features & Use Cases

  • Delegation Detection: Inspect an address to determine whether it is delegated (on-chain code prefix and delegate address decoding).
  • Offline Authorization Signing: Produce signed authorization objects for delegate contracts without broadcasting transactions.
  • Delegated Execution & Atomic Batches: Send single delegated calls or atomically execute multiple calls (approve + swap + transfer) using SimpleDelegation and tx type 0x04.
  • Revocation & Safety: Revoke delegations by authorizing address(0) and follow explicit safety rules for confirmation and local key handling.
  • Use Case: Retrieve swap calldata from a DEX skill, then execute an atomic approve+swap+transfer in one delegated transaction to reduce front-running and ensure all-or-nothing execution.

Quick Start

Run the provided morph-7702 script from the repository to inspect delegation status or to sign and send delegated calls, supplying a local private key when performing send, batch, or revoke operations.

Frequently Asked Questions about morph-7702

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute atomic batch transactions like approve and swap on Morph L2?

You can execute atomic batch transactions on Morph L2 by applying EIP-7702 EOA delegations and using tx type 0x04. This enables multiple calls, such as an approve and swap sequence, to be grouped into a single delegated transaction for all-or-nothing execution.

What is EIP-7702 EOA delegation and when do I need it for batch calls?

EIP-7702 EOA delegation allows an externally owned account to authorize a delegate contract to execute transactions on its behalf. You need it when executing atomic batch calls like approve+swap+transfer sequences on Morph L2, removing the need for manual multi-transaction workflows.

How do I sign offline authorization for delegated transactions without broadcasting?

Offline authorization signing produces signed authorization objects for delegate contracts without broadcasting transactions. This requires local private key signing for mutating operations, ensuring the signed authorization can be safely generated and stored before delegated execution.

Do I need a local private key to sign and send delegated calls on Morph L2?

Yes, a local private key is required to sign and send delegated calls on Morph L2. The Skill mandates local private key signing for all mutating operations, including single delegated calls, batch execution, and delegation revocation, while following explicit safety rules for key handling.

How can I check if an address is already delegated on Morph L2?

You can check delegation status by inspecting the address on Morph L2 to determine if it is delegated. The process detects on-chain code prefixes and decodes the delegate address, allowing you to verify if an EOA currently has an active EIP-7702 delegation.

What are the limitations when revoking EIP-7702 delegations on Morph L2?

Revoking EIP-7702 delegations on Morph L2 requires authorizing address(0) to clear the delegation. Limitations include following explicit safety rules for confirmation and local key handling, and avoiding mutually exclusive handling with alternative fee transaction types during the revocation process.