# Permissionless Challenger

The Fiamma Bridge operates under a fundamental trust assumption: **at least 1 out of N challengers must be honest**. This means the larger the value of **N**, the more secure the bridge becomes.

Although the challenger role is permissionless, we strive to minimize barriers to entry to encourage broad participation. By ensuring a large and diverse pool of challengers (**N**), we enhance the bridge’s security, making Fiamma the safest Bitcoin bridge.

To achieve this, we’ve designed the permissionless challenger system with three key principles:

**1. Accessibility**

* **Easy to Run**: We provide a user-friendly challenger frontend for seamless operation. For details, refer to the [Challenger Guide](/our-product-suite/pragmatically-trustless-bitvm-bitcoin-bridge/user-guides/testnet-beta/how-to-run-a-challenger.md).
* **Low Capital Requirements**:
  * **Collateral**: Only **0.0001 BTC**.
  * **Challenge Cost**: At most **0.001 BTC** per challenge.

**2. Incentives**

* **Regular Rewards**: Challengers earn rewards for verifying each proof submitted by operators.
* **High Stakes Rewards**: If a challenger successfully identifies and slashes a malicious operator, they can earn up to $**1,000**.

By combining low entry barriers with strong incentives, we foster a robust and decentralized challenger network, ensuring the highest level of security for users.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fiammalabs.io/our-product-suite/pragmatically-trustless-bitvm-bitcoin-bridge/core-components/permissionless-challenger.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.