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

# The anchor

*What YuCROWN holds — and what it deliberately does not.*

Earth LinC is an open protocol. Most of it needs no one's permission: anyone can open a station, receive a NaviStar, hold a Realm, read the chain, or build a new surface on the same standard. That openness is the point.

But one thing cannot be open-and-trustless: the question of whether a real-world action **actually happened**. Someone accountable has to stand behind that answer. On Earth LinC, that someone is **YuCROWN Corporation** — the nonprofit that initiated and anchors the protocol. *Anchored, never owned.*

## What YuCROWN anchors

* **The missions.** Every mission a mint can carry is attested by YuCROWN: real, verifiable work for the earth.
* **The verification.** YuCROWN holds the rule — *verified before recorded* — and ensures every verified-fact layer rests on an independent, accountable confirmation.
* **The charitable rail.** When a station is minted carrying a YuCROWN mission, that payment is a Drop — received by YuCROWN, a 501(c)(3) nonprofit, **in full**, and applied to verified ecological action. One payment, one destination; never commingled with commercial revenue.
* **The public trust.** When you read "verified" on Earth LinC, YuCROWN is the institution accountable for that word.

## What YuCROWN does not do

* It does **not** own the protocol. The standard is open; the objects live on a public chain; anyone can build on them without asking.
* It does **not** own your station, your Realm, or your NaviStars. They are sovereignly yours, under the rules of the chain itself.
* It does **not** build or operate the product. The build is undertaken and funded by a separate commercial company (named in the legal documents); YuCROWN funds none of it, operates none of it, and receives nothing but mission-mint Drops.
* It does **not** gatekeep participation. Broadcasting is free and open; reading and building are permissionless.

## Why an anchor at all

A protocol with no anchor must pretend that everything can be trustless — and "verified ecological action" cannot be. A platform with no openness asks you to trust it for everything. Earth LinC does neither: **open everywhere openness is possible, anchored at exactly one point — physical truth — by an accountable nonprofit.** Anchored, never owned. If YuCROWN disappeared tomorrow, every Realm and every NaviStar would remain on-chain, readable and yours. What would need replacing is the anchor — because the one thing that can't be automated is standing behind the truth.

***

*Part of Trust & Verification: How verification works · The anchor · Transparency & impact.*


---

# 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://earthlinc.gitbook.io/protocol/trust-and-verification/the-anchor.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.