How gasp-xyz/gasp-monorepo works
Major Components
• Ethereum/Layer 1 Contracts:
– Include the “Gasp ETH Contract” from the contracts directory, plus the Eigen ETH contracts (in contracts/lib/eigenlayer-contracts). Indicate that these smart contracts handle ERC20 deposits/withdrawals and manage critical state (e.g., Merkle roots, operator lists).
• Sequencer:
– Represent the “sequencer/” service that processes transactions and submits them to the collator.
• Collator:
– Use a node labeled “Gasp Node” (from gasp-node/) to show the block builder powered by Substrate.
• Updater:
– Include the “updater/” service that monitors the Eigen Layer and submits on-chain results, ensuring smart contract states are synchronized.
• Aggregator & Task Manager:
– Show the “avs-aggregator/” module that generates tasks and aggregates operator outputs.
• Gasp AVS Operators:
• Ferry Services:
– Include “ferry-deposit/” and “ferry-withdrawal/” — these handle cross-chain asset transfers.
• Stash (Data Management):
• External Infrastructure & Tooling:
– Optionally, represent the Docker Compose setup (ops/ directories), Helm charts, and monitoring (Grafana) which handle deployment and observability.
• Development & Toolchain:
– You may add an “Infrastructure & Tooling” block mentioning Proto, Moon, Husky, and commitlint that help synchronize toolchain versions across the monorepo.
Establish Relationships and Data Flow
• The Task Generator (within avs-aggregator) publishes new tasks to the Aggregator.
• Aggregator collects BLS signatures from the AVS operators (in gasp-avs) and then posts aggregated responses.
• The Updater monitors Eigen Layer activity and updates the Ethereum contracts.
• The Sequencer processes transactions and interacts with the collator (Gasp Node) to build L2 blocks.
• Ferry Services interact with smart contracts on Ethereum as well as external chains to handle asset deposits and withdrawals.
• Stash (data management) aggregates data coming from multiple services (for example, scraping, metrics, transaction history) and might expose APIs to external dashboards.
Architectural Patterns and Technologies
• Microservices Architecture: Represent each service (written in Go, Rust, or Node.js) as an independent module communicating over well-defined APIs.
• Layered Architecture: Separate the blockchain layer (contracts and on-chain functions), service layer (sequencer, updater, aggregator, ferry services), and management/data layer (stash).
• That the system uses container orchestration (Docker Compose) and multiple toolchain guarantees (Proto, Moon).