optimism

Document the OP Stack protocol architecture, contracts, and rollup operations.

4|1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/hairyf/blockchain-skills --skill optimism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimism
Source: https://github.com/hairyf/blockchain-skills/tree/main/skills/optimism
Command: npx skills add https://github.com/hairyf/blockchain-skills --skill optimism

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on the OP Stack protocol, enabling developers to understand and integrate with Optimism's Layer 2 solutions.

Core Features & Use Cases

  • Protocol Deep Dive: Understand L1/L2 contracts, derivation, bridges, and fault proofs.
  • Integration Support: Facilitates building L2 nodes, batchers, bridges, and contract integrations.
  • Use Case: A developer needs to implement a custom bridge between L1 and an OP Stack-based L2. This Skill provides the necessary references on bridges, deposits, withdrawals, and cross-domain messengers to guide their implementation.

Quick Start

Explain the core architecture of the OP Stack protocol.

Frequently Asked Questions about optimism

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

FAQPage Schema
How does the OP Stack derivation pipeline work for L2 block derivation?

The OP Stack derivation pipeline processes L1 batches through sequencing windows and batch submission formats to derive L2 blocks. It interacts with the Engine API to execute blocks, ensuring L2 state matches L1 data availability constraints.

How do I build a custom bridge between L1 and an OP Stack L2?

To build a custom L1 to L2 bridge on the OP Stack, utilize the cross-domain messenger contracts and reference the bridge documentation for deposits and withdrawals. This provides the necessary framework for secure cross-chain message passing.

What is the role of the rollup node in the OP Stack protocol?

The rollup node in the OP Stack protocol manages block derivation by syncing L1 data, verifying sequencing windows, and submitting batch data. It coordinates with the Engine API to drive L2 execution and maintain chain consensus.

How do fault proofs secure the OP Stack L2 network?

Fault proofs secure the OP Stack by allowing challengers to dispute invalid state transitions through a cryptographic proving process. This mechanism ensures that any incorrect L2 state derived from L1 batches is rejected.

Can I use the OP Stack Engine API for direct L2 node integration?

Yes, you can use the OP Stack Engine API for direct L2 node integration to drive block execution and sync state. It provides the standard interface for the rollup node to communicate execution payloads and derivation updates.

What are sequencing windows and batch submission formats in OP Stack rollups?

Sequencing windows define the L1 time period for a sequencer to submit L2 batch data, while batch submission formats specify how transactions are compressed and posted to L1. These mechanisms ensure data availability and derivation ordering.