Drosera

• Name: Drosera
• URL: https://drosera.io/
• Category: decentralized onchain monitoring / incident-response / agent-automation network
• Tags: ethereum-ecosystem
• Summary: Drosera is trap-based EVM monitoring and response automation. The useful cut is not decentralized agents; it is that operators run Solidity-defined checks and can trigger alerts or onchain responses.
• What it does:
  • Lets developers write Trap contracts with collect, shouldRespond, and shouldAlert logic to monitor onchain conditions and define response behavior
  • Uses operator nodes to execute Trap logic every block, store collected data off-chain on operator nodes, and decide when alerts or response-contract calls should fire
  • Ships a CLI installer (droseraup), a Foundry template for bootstrapping Trap projects, and example repositories showing security and automation use cases
  • Supports event-log-driven monitoring via trap event filters and exposes test/deployment flows for simulating incidents and deploying Trap contracts to the network
  • Frames the network as useful for DeFi security, treasury monitoring, protocol automation, and broader autonomous onchain workflows
• Key claims:
  • The public GitHub organization describes Drosera as “a EVM native and decentralized agent layer” that enables developers to create Traps which monitor onchain data and trigger automated onchain responses
  • Official Trap-anatomy docs explain that collect runs every block, shouldRespond evaluates recent collected data to determine if a response should execute, and shouldAlert provides notification-oriented logic with the same pattern
  • Getting-started docs show a concrete developer workflow around Foundry, the Drosera CLI, trap templates, testnet/mainnet deployment, and alert integrations
  • The examples repo frames Traps as references for detecting incidents and protecting protocols, with an architecture where operators run trap logic continuously and feed the Drosera Protocol plus user-specified response contracts
  • Public repos and release pages suggest Drosera is shipping not only documentation but also operator/node binaries, templates, and integration proofs of concept including ERC-7579 wallet-related work
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Drosera’s official site, developer docs, GitHub organization, examples repository, and trap template repository; see ../whitepapers/drosera-primary-sources-2026-04-25.md.
• Sources:
  • https://drosera.io/
  • https://dev.drosera.io/
  • https://dev.drosera.io/trappers/getting-started/
  • https://dev.drosera.io/trappers/creating-a-trap/
  • https://github.com/drosera-network
  • https://github.com/drosera-network/examples
  • https://github.com/drosera-network/trap-foundry-template

Internal linkages

• Best monitoring-and-response anchors: forta and hypernative.
• Keep the note on trap logic, operator execution, and response automation rather than on generic agent marketing.

Control surface

• Practical authority sits in operator participation, trap code, offchain collected state, alert routing, and the permissions around any response contract the trap can call.

• Read Drosera as monitoring-and-response infrastructure with a decentralized operator story, not as a general-purpose autonomous-agent platform.

• Last reviewed: 2026-08-13 UTC