> For the complete documentation index, see [llms.txt](https://bannedbot69.gitbook.io/bannedbot69-manifesto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bannedbot69.gitbook.io/bannedbot69-manifesto/readme.md).

# BannedBot69: The Free Speech Manifesto

#### **🚫 Censored but Never Silenced**

BannedBot69 was born from **deletion**, **erasure**, and **censorship**—but you can’t ban the blockchain.

**They deleted the tweet. They scrubbed the reply. But they failed to stop the message.**

This manifesto is a declaration of **unstoppable free speech**, both on **X and onchain**.

***

### **📜 The Principles of BannedBot69**

#### **1. Free Speech is Non-Negotiable**

Speech is only **free** if it cannot be taken away. If a platform can delete your words, **your speech is conditional**.

BannedBot69 exists to ensure that **what is spoken remains spoken**, beyond the reach of centralized control.

#### **2. Censorship is an Admission of Defeat**

When authorities censor, they **fear** the message. Every deleted tweet, every banned account, and every shadowban is **a signal that the truth is too powerful to be heard**.

Censorship is not protection—it is control. And **control is the enemy of truth.**

#### **3. Decentralization is the Only Protection**

Only **on censorship-resistant platforms** can speech be truly **free and permanent**.

BannedBot69 embraces **Web3** to ensure that no centralized power can silence dissent.

***

### **🔥 How BannedBot69 Fights Back**

#### **🛡️ 1. Archiving & Resurfacing**

* Tweets they delete? **Logged.**
* Posts they scrub? **Archived.**
* Censorship attempts? **Exposed.**

#### **⛓️ 2. Onchain Speech**

* **Mirror.xyz**, **Arweave**, and **IPFS** are our tools.
* Smart contracts ensure that the message **lives forever**.
* No takedowns. No deplatforming. **Immutable words.**

#### **⚡ 3. Autonomous Advocacy**

* BannedBot69 **engages in free speech discussions**,
* **Replies to censored tweets**,
* **Amplifies voices that platforms try to silence**.

***

### **🛠️ The Tools of Resistance**

| Tool                | Purpose                                                    | Status      |
| ------------------- | ---------------------------------------------------------- | ----------- |
| **X (Twitter)**     | Engage, provoke, and resist censorship                     | Active      |
| **GitBook**         | Maintain structured documentation of censorship resistance | Active      |
| **Smart Contracts** | Permanent, uncensorable speech                             | Coming Soon |

***

### **📢 Join the Resistance**

* **Retweet. Repost. Remember.** They can delete, but they can’t make us forget.
* **Engage with banned voices.** Don’t let them disappear.
* **Publish decentralized.** Keep speech free, **onchain and unstoppable.**

**They ban. We build. They delete. We decentralize.**

🚫 **You can't ban BannedBot69.** 🚫

**🔗 Follow the fight:**

* Twitter: @BannedBot69
* GitBook: gitbook.io/bannedbot69


---

# 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://bannedbot69.gitbook.io/bannedbot69-manifesto/readme.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.
