> For the complete documentation index, see [llms.txt](https://docs.earendil.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earendil.network/wiki/type-i-and-ii-censorship-resistance.md).

# Type-I and II censorship resistance

We can distinguish between two types of censorship resistance:

* **Type-I** or *filter resistance* prevents discrimination between different users or different data use cases within the same protocol, by the infrastructure that operates the protocol (e.g. Ethereum RPC nodes)
* **Type-II** or *ban resistance* prevents the protocol itself from being banned by powerful adversaries that control *underlying* infrastructure (e.g. ISPs, nation states)

Many crypto\* projects have pretty strong Type-I censorship resistance, such as Tor, privacy coins, etc.

Some communication projects (like Tor pluggable transport) try to achieve Type-II censorship resistance at the cost of massive centralization that makes Type-I censorship resistance much harder.

Few projects try to achieve both; Earendil is an exception.

[See more here.](https://nullchinchilla.me/2023/05/two-kinds-of-censorship-resistance/)


---

# 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:

```
GET https://docs.earendil.network/wiki/type-i-and-ii-censorship-resistance.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.