# Docs ## Docs - [Deployments](/deployments) - [Introduction](/introduction): [Drosera Trap Explorer](https://app.drosera.io) | [View Pricing & Deploy Traps](https://app.drosera.io/early-supporters-initiative) - [Litepaper](/litepaper): The Drosera Litepaper provides a high-level overview of Drosera and its core components. It is intended to give readers a basic understanding of the Drosera protocol and its use cases. The Litepaper is a living document and will be updated as the Drosera protocol evolves. - [Orange Paper](/orangepaper): The Drosera Orange Paper is a 2 page overview of the Drosera protocol and its vision. - [Use Cases](/use-cases): There are infinite possibilities! - [Executing Traps πŸͺ€](/operators/executing-traps): Executing traps is a crucial part of the Drosera ecosystem. Traps are smart contracts that define the conditions for detecting on-chain invariants and performing on-chain responses. Operators are responsible for executing Traps and performing on-chain response actions, ensuring the security and stability of the network. - [Installation πŸ“€](/operators/installation): The Drosera Operator runs on Linux. - [Monitoring πŸ“Š](/operators/metrics): The Operator Node can be configured to send Opentelemetry metrics, logs and traces to an OpenTelemetry Collector. The OpenTelemetry Collector can then be configured to send the metrics to a variety of backends such as Prometheus, Grafana, or other monitoring tools. - [Monitoring Stack](/operators/metrics): `drosera_process_cpu_usage`: The CPU usage of the Operator Node process - [Operator Rewards 🦾](/operators/operator-rewards): Incentivizing operators to monitor protocols. - [πŸš€ How to Launch Our Template on Railway](/operators/railway): Follow these simple steps to deploy the Drosera Operator template on **railway.app**: - [Register as an Operator πŸ—³οΈ](/operators/register): To run the Drosera Operator Node, you must first register as an Operator. This process involves registering a public BLS public key with the Drosera contracts. This can be achieved by running the following command: - [πŸš€ Run the Operator on a VPS](/operators/run-on-vps): Install dependencies - [Run the Drosera Operator Node πŸ’»](/operators/run-operator): Running the Drosera Operator Node is a simple process. This guide will walk you through the steps to run the Operator Node, enabling you to begin executing Traps and earning rewards. - [πŸš€ Run the Operator with Docker](/operators/run-with-docker): Install dependencies - [Running multiple operators on one machine](/operators/run-with-docker): Install dependencies - [Testnet Guide πŸ§ͺ](/operators/testnet-guide): This guide is for the Protocol level Whitelisted operators. - [Boosting a Trap πŸš€](/trappers/boosting-a-trap): Drosera allows anyone to provide operators with gas reimbursement for taking on-chain actions by leveraging the Bloom Boost mechanism. By depositing ETH, a Trap's response action will automatically reimburse the operator based on the cost of the response and priority to be included on-chain as soon as possible. This allows for lightning-fast incident response times to be achieved while reimbursing the operator. - [Configuring Alerts](/trappers/configuring-alerts): Alerts allow your trap to notify you when specific conditions are met. When an operator executes your trap's `shouldAlert` function and it returns `true`, an alert is sent to your configured notification channels (Slack, or webhooks). - [Creating a Trap 🌱](/trappers/creating-a-trap): The section below outlines the anatomy of a Trap and how to deploy a Trap to the Drosera Network. - [Drosera CLI πŸ–₯️](/trappers/drosera-cli): The Drosera CLI is a command line tool used to create, manage, and monitor Traps on the Drosera Network. It utilizes a configuration file to manage your Traps and their configurations. It can be installed by following the getting started guide [here](/trappers/getting-started#installing-droseraup). - [Dryrunning a Trap ⛓️](/trappers/dryrunning-a-trap): Ideally you would be able to test your trap with real block/state data before deploying it for real, on-chain. Well, with the `dryrun` command you can. In normal trap operation, a trap will be "monitored" by one or more opted-in operators, but with the `dryrun` command you can easily test two lifecycles (a bootstrap and a normal lifecycle) of this same process on your local machine with what is for all intents and purposes, a locally spun-up ad-hoc operator. - [Getting Liveness Data 🩺](/trappers/getting-liveness-data): This command allows you to check current liveness of operators opted in to a trap. - [Getting Started ⚑](/trappers/getting-started): Before diving into the technical setup, check out our [pricing plans](https://app.drosera.io/early-supporters-initiative) to choose the right subscription for you. Subscriptions are not required for testnet testing. - [Project Setup with Foundry](/trappers/getting-started): If you’re on Windows, you will need to install and use WSL, as your terminal, since Droseraup currently does not support the Windows OS. - [Hydrating a Trap πŸ’§](/trappers/hydrating-a-trap): Drosera acts as a marketplace between Trappers and Operators. Operators are looking for the most incentivized traps to run, while Trappers are looking for Operators to run their traps. Hydration Streams are the main reward mechanism in the Drosera protocol. When a User creates a hydration stream, they fund the trap with any amount of Drosera's native token, and then the hydration balance is streamed out from the trap over-time to operators that have opted-into the trap. - [Kicking an Operator πŸ₯Ύ](/trappers/kicking-an-operator): If you would like to remove an operator from the set of operators running/monitoring your trap, you can kick them with the `kick-operator` command. - [Private Traps πŸ”’](/trappers/private-traps): The default for a trap is to be public (i.e. `private_trap = false` in your `drosera.toml`). In this configuration, the only operators who can opt in to your trap and run it are protocol-level operators. - [Recovering Your drosera.toml File πŸ€·β€β™‚οΈ](/trappers/recover-drosera-toml): The `drosera.toml` file is your local reference to all of your traps (typically under one keypair). It specifies how you want them configured, the paths to the compiled trap code on your local computer, the response functions and contracts, the Ethereum RPC you choose to use, etc. So this file is important, but life can happen and the file may be deleted, corrupted, etc by accident or no fault of your own. - [Setting Bloomboost Percentage πŸͺ„](/trappers/setting-bloomboost-percentage): Only applicable on Ethereum at the moment - [Purchasing A Subscription πŸ‘‘](/trappers/subscribing): Purchasing a Drosera subscription provides access to utilize the protocol for your automation, security, and alerting use-cases. Specifically, it allows you to deploy and update traps. - [Updating a Trap βš™οΈ](/trappers/updating-a-trap): After a Trap has been deployed to the Drosera Network, it is possible to update the Trap's bytecode and other configuration values such as the response contract and function. This is useful when a Trap needs to be updated with new logic or bug fixes.