Builder intent

secure a service with restaking

EigenCloud (the EigenLayer restaking platform) is the default when the goal is to give a service cryptoeconomic security rather than to build the service's app logic itself. It supplies restaking, operator sets, and slashing so a new AVS can inherit Ethereum-anchored security; Ethereum L1 is where that stake and slashing settle, Safe handles operator/treasury controls, and The Graph indexes operator and slashing activity. Interop layers like Hyperlane or LayerZero and appchain stacks like Orbit are listed as things that consume restaked security, not substitutes for it.

Also available as JSON · Markdown

Recommended stack

supporting_protocol76

EigenCloud

Use EigenCloud (the EigenLayer restaking platform) as the restaking and operator layer: define an AVS, an operator set, and slashing conditions to inherit Ethereum-anchored cryptoeconomic security. Restaking contracts and the operator/quorum set live on Ethereum L1, where stake, registration, and slashing are settled.

supporting_protocol80

Safe

Use a Safe multisig for operator/treasury operations and admin controls around the service.

indexing_and_data80

The Graph

Index operator registrations, restaked stake, AVS activity, and slashing events for dashboards and agent-readable state.

Considered and excluded

hyperlane — Hyperlane provides interoperability and interchain security modules but is not itself the restaking/economic-security layer; it can consume restaked security rather than replace EigenCloud.
arbitrum-orbit — Orbit gives you an appchain, not a restaking/AVS security primitive; pair the two (Orbit chain + EigenLayer-secured component) rather than substitute.

Risks

Restaking carries slashing exposure and correlated risk across every service an operator secures.
AVS tooling, slashing, and redistribution semantics evolve quickly; verify the current operator-set model and slashing conditions before production.
Bootstrapping a trustworthy operator set and sufficient restaked stake is a real go-to-market problem, not just an integration.
Core restaking is anchored to Ethereum L1; cross-chain consumption of that security adds its own trust assumptions.

Next steps

Decide your role: restaker, operator, or AVS developer.
Specify the operator set, quorum thresholds, and slashing conditions for the service.
Build the AVS against the EigenLayer middleware and test on a testnet before mainnet.
Define monitoring for operator behavior, stake, and slashing events.

Agent-facing output

What the agent receives

The intent page exposes the same structured recommendation shape agents should use: matched intent, stack roles, readiness scores, difficulty, risks, next steps, and registry version.

agent output · application/jsonstructured

{
  "intent": "I want to give my service, appchain, bridge, or oracle cryptoeconomic security (or build an AVS) using Ethereum restaking",
  "matched_intent": "secure-a-service-with-restaking",
  "recommended_stack": [
    {
      "slug": "eigencloud",
      "name": "EigenCloud",
      "role": "supporting_protocol",
      "readiness_score": 76,
      "integration_difficulty": "high",
      "reason": "Use EigenCloud (the EigenLayer restaking platform) as the restaking and operator layer: define an AVS, an operator set, and slashing conditions to inherit Ethereum-anchored cryptoeconomic security. Restaking contracts and the operator/quorum set live on Ethereum L1, where stake, registration, and slashing are settled."
    },
    {
      "slug": "safe",
      "name": "Safe",
      "role": "supporting_protocol",
      "readiness_score": 80,
      "integration_difficulty": "low",
      "reason": "Use a Safe multisig for operator/treasury operations and admin controls around the service."
    },
    {
      "slug": "the-graph",
      "name": "The Graph",
      "role": "indexing_and_data",
      "readiness_score": 80,
      "integration_difficulty": "medium",
      "reason": "Index operator registrations, restaked stake, AVS activity, and slashing events for dashboards and agent-readable state."
    }
  ],
  "excluded_candidates": [
    {
      "slug": "hyperlane",
      "reason": "Hyperlane provides interoperability and interchain security modules but is not itself the restaking/economic-security layer; it can consume restaked security rather than replace EigenCloud."
    },
    {
      "slug": "arbitrum-orbit",
      "reason": "Orbit gives you an appchain, not a restaking/AVS security primitive; pair the two (Orbit chain + EigenLayer-secured component) rather than substitute."
    }
  ],
  "risks": [
    "Restaking carries slashing exposure and correlated risk across every service an operator secures.",
    "AVS tooling, slashing, and redistribution semantics evolve quickly; verify the current operator-set model and slashing conditions before production.",
    "Bootstrapping a trustworthy operator set and sufficient restaked stake is a real go-to-market problem, not just an integration.",
    "Core restaking is anchored to Ethereum L1; cross-chain consumption of that security adds its own trust assumptions."
  ],
  "next_steps": [
    "Decide your role: restaker, operator, or AVS developer.",
    "Specify the operator set, quorum thresholds, and slashing conditions for the service.",
    "Build the AVS against the EigenLayer middleware and test on a testnet before mainnet.",
    "Define monitoring for operator behavior, stake, and slashing events."
  ],
  "generated_with": "composewith.eth",
  "registry_version": "2026.07.02-5a6fd5e"
}