# Economic Model and Incentives

**6.1 Verification Token Economics**

WachXBT introduces the WACH token to align incentives across the verification network:

#### 6.1.1 Token Distribution

<figure><img src="/files/ZgNfyULNcXW9fDNWejQn" alt=""><figcaption></figcaption></figure>

#### 6.1.2 Verification Reward Mechanism

Verification providers earn WACH tokens based on the accuracy and speed of their verification services:

```
Reward = Base_Reward * Accuracy_Multiplier * Speed_Bonus * Stake_Multiplier
```

Where:

* `Base_Reward` represents the standard reward for verification
* `Accuracy_Multiplier` increases rewards for consistently accurate verification
* `Speed_Bonus` provides additional rewards for fast response times
* `Stake_Multiplier` rewards long-term token holders

#### 6.1.3 Adversarial Training Incentives

Operators of adversarial agents receive rewards for discovering verification weaknesses:

```
Discovery_Reward = Severity_Score * Impact_Factor * Novelty_Bonus
```

Where:

* `Severity_Score` reflects the potential damage of the discovered weakness
* `Impact_Factor` considers how many agents could be affected
* `Novelty_Bonus` provides extra rewards for completely new attack vectors

#### 6.2 Staking and Slashing Mechanisms

#### 6.2.1 Verification Provider Staking

Verification providers must stake WACH tokens to participate in the network:

```
contract VerificationStaking {
    struct Validator {
        uint256 stakedAmount;
        uint256 reputation;
        uint256 lastUpdate;
        bool active;
    }
    
    mapping(address => Validator) public validators;
    uint256 public minimumStake = 1000 * 10**18; // 1000 WACH
    
    function stake(uint256 amount) external {
        require(amount >= minimumStake, "Insufficient stake");
        validators[msg.sender].stakedAmount += amount;
        validators[msg.sender].active = true;
    }
}
```

#### 6.2.2 Slashing for Poor Performance

Validators face slashing penalties for consistently poor verification performance:

```
Slash_Amount = min(Staked_Amount * Severity_Ratio, Maximum_Slash)
```

Where:

* `Severity_Ratio` reflects the severity of verification errors
* `Maximum_Slash` caps the maximum penalty at 50% of staked amount

#### 6.3 Agent Integration Economics

#### 6.3.1 Verification Fee Structure

DeFAI agents pay verification fees based on transaction complexity and urgency:

```
Fee = Base_Fee + Complexity_Fee + Urgency_Premium + Value_Factor
```

Where:

* `Base_Fee` covers basic verification operations
* `Complexity_Fee` accounts for complex multi-protocol operations
* `Urgency_Premium` allows agents to pay for faster verification
* `Value_Factor` scales fees with transaction value

#### 6.3.2 Performance-Based Discounts

Agents with consistently good behavior receive verification fee discounts:

```
Discount_Rate = min(Performance_Score * Discount_Factor, Maximum_Discount)
```

High-performing agents can receive up to 50% discounts on verification fees.

###


---

# 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://quillainetwork.gitbook.io/quillai-network/agent-swarm/wachxbt-the-unified-verification-agent-for-defai/economic-model-and-incentives.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.