> For the complete documentation index, see [llms.txt](https://docs.dotone.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dotone.online/slashing/slash-rules-or-dotone-smart-chain-docs.md).

# Slash Rules | Dotone Smart Chain Docs

DOTO Slash Rules

Three types of malicious behaviors can lead to slashing on the dotOne network.

## Double Sign

Anyone can submit a slash request with evidence of Double Sign. The evidence must adhere to the following rules:

* Two block headers have the same height and the same parent block hash
* Two block headers are sealed by the same validator
* Two signatures of these two blocks must not be the same
* The time of these two blocks must be within the validity of the evidence, which is 24 hours

If the evidence is valid:

1. **200DOTO** would be slashed from the **self-delegated** DOTO of the validator
2. The remaining slashed DOTO will be allocated to the credit addresses of validators participating in the next distribution
3. Set the validator `jailed` with a duration of **30 days**, and remove it from the active validator set

## Malicious Vote

Anyone can submit a slash request on dotOne with the evidence of Malicious Vote. The evidence must adhere to the following rules:

* The target number voted by two votes lags behind the block header of the canonical chain by no more than 256
* The source numbers of the two votes are both smaller than their respective target numbers
* The source hash and target hash of the two votes are both not equal
* The target number of the two votes is the same, or the span of one vote includes the span of the other vote
* The two votes are signed by the same voting key, and the verification of signatures are both passed
* The voting key used for signing is in the list sent by the last two block headers

If the evidence is valid:

1. **200DOTO** would be slashed from the **self-delegated** DOTO of the validator
2. **5DOTO** would allocate to the submitter from the system reward contract as a reward if the validator is active when the evidence is submitted
3. The remaining slashed DOTO will be allocated to the credit addresses of validators participating in the next distribution
4. Set the validator `jailed` with a duration of **30 days**, and remove it from the active validator set

## Unavailability

There is an internal smart contract that records the missed blocking metrics of each validator.

If a validator misses over 333 blocks(governable) in 24 hours, they will not receive the block reward; instead, it will be shared among other validators.

If a validator misses more than 1000 blocks(governable) in 24 hours:

1. **10DOTO**(governable) would be slashed from the **self-delegated** DOTO of the validator
2. The slashed DOTO will be allocated to the credit addresses of validators participating in the next distribution
3. Set the validator `jailed` with a duration of **2 days**, and remove it from the active validator set


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.dotone.online/slashing/slash-rules-or-dotone-smart-chain-docs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.