LogoLogo
HomeTelegram
  • Welcome to Opus
  • Introduction
    • ▸ What is Opus?
      • Overview of the product
      • Vision: Automation layer for the decentralized web
      • Key verticals
      • EIP-7702
  • ▸ How Opus Works
    • Browser-based architecture (no install)
    • EIP-7702 session-based automation
    • AI agent decision-making process
    • Smart contract interaction layer
  • ⚙️ Architecture
    • ▸ System Overview
      • High-level architecture diagram
    • ▸ EIP-7702 Integration
      • Comparison vs EIP-4337 / traditional EOAs
    • ▸ Smart Contract Design
      • Core contracts:
      • Contract architecture diagrams
      • Gas considerations
  • ⚡ Use Cases
    • ▸ DeFi Automation
    • ▸ NFT Trading
    • ▸ DAO Governance
  • 🛠️ Getting Started
    • ▸ dApp Walkthrough
      • Getting Started with Opus dApp
      • Logs and automation history
  • 🧪 Developers
    • ▸ API Access
      • Endpoints for task creation, monitoring, retrieval
      • Auth via wallet signatures
    • ▸ Custom Strategies
      • DSL (Domain Specific Language) or JSON schema explanation
      • Writing your own task logic
    • ▸ Contract ABIs & Events
      • ABI snippets with examples
      • Event logs used by the platform
  • 🔐 Security & Audits
    • ▸ EIP-7702 Session Key Risks
      • Threat model
      • Session revocation mechanism
      • Time-bound delegation logic
Powered by GitBook
On this page
Export as PDF
  1. 🔐 Security & Audits
  2. ▸ EIP-7702 Session Key Risks

Time-bound delegation logic

Each session key has an expiry timestamp encoded in the signed delegation payload:

{
  "delegate": "0x1234...",
  "validUntil": 1718890000,
  "scope": {
    "contracts": ["0xExecutor"],
    "methods": ["0x09..."]
  }
}

Smart contract enforces:

require(block.timestamp < sessions[msg.sender].validUntil, "Session expired");

This ensures all sessions are finite and revocable.

PreviousSession revocation mechanism

Last updated 13 days ago