> For the complete documentation index, see [llms.txt](https://docs.1337bridge.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1337bridge.tech/introduction-and-foundation/why-is-it-called-1337-bridge.md).

# Why is it called "1337 Bridge"?

For us, 1337 is not just a number. It is a symbol.

Derived from "Leet" (Elite), the term originated in the early days of hacker culture and the open internet: an era defined by anonymity, meritocracy, and freedom from centralized control. In that world, your identity didn't matter; your skill and your code did.

We chose this name because we are bringing that spirit back to DeFi.

In a landscape increasingly cluttered with KYC walls, surveillance, and restrictions, 1337 Bridge represents a return to true decentralization. We believe that moving assets should be permissionless. The "1337" ethos dictates that the system should work for the user, not the other way around.

No KYC. No bureaucracy. Just code.


---

# 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.1337bridge.tech/introduction-and-foundation/why-is-it-called-1337-bridge.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.