> 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/build/build-on-earth-linc.md).

# Build on Earth LinC

*One protocol, infinite surfaces. Here's how to make yours speak it.*

Earth LinC is a protocol, not a platform: an open standard on a public chain (Polygon · ERC-1155 + ERC-721 + ERC-6551), permissionless to read and build on. `earthlinc.earth` is one implementation. Yours can be another — a surface for an event, for an organization, for a context we haven't imagined. *One protocol meeting infinite surfaces, never a product matrix.*

## What you can build

* **A surface** — your own application that composes stations, mints them, Casts NaviStars, and renders Realms for your audience or community.
* **A reader** — anything that reads the open record: Realm viewers, constellation maps, research tools. Reading is fully permissionless.
* **An agent** — an AI capability that extends the compose layer, giving activities new kinds of living form (see *Bring an AI agent*).
* **A mission integration** — connecting verified earth action so mints can carry it (see *Bring a mission*).

## The shape of the protocol

Three acts (**Broadcast · mint · Cast**), two on-chain assets (the **minted station** and the **NaviStar**), one space per holder (the **Realm**: Signet → ERC-6551 account → stars), and one linking structure (the **constellation**). The full formal definition — objects, lifecycle, interfaces — is the **Protocol Specification**; read it first. Defaults worth knowing: gasless transactions (ERC-2771) and custody-by-default with optional self-custody, so your users never need crypto to receive.

## The invariants — binding on every surface

Whatever you build must honor the Specification's Part C, in full:

1. **No market infrastructure on the Service.** Users are strictly prohibited from constructing, hosting, listing, or operating any marketplace, auction house, clearinghouse, or secondary trading order book **within the Service or utilizing the platform's proprietary infrastructure**. While Stations and NaviStars are inherently transferable by their sovereign holders as a matter of property fact, the platform's infrastructure and hosted services may not be subverted to facilitate commercial trading, exchange coordination, or liquidity pooling.
2. **Custody-by-default → optional self-custody** — receiving must work with nothing but an email.
3. **The AI integrity boundary** — AI composes authored expression only; it never generates, alters, or asserts verified fact.
4. **Verified-before-recorded** — no physical-world claim is recorded without an independent, accountable source.
5. **One payment, one destination — never split** — a mission mint is a Drop, in full, to the anchor; everything else is ordinary commerce that touches no charitable funds.

The Specification states the *why* of each rule — read those too; surfaces that understand the reasons don't route around them.

## Getting started

1. Read the **Protocol Specification** (this section's source of truth).
2. Read **Contracts & reference implementation** for the substrate and what's published when live.
3. Building an agent or bringing a mission? Those have their own doors — the next two pages.
4. Questions: **<support@earthlinc.earth>** (say "building" in the subject).

***

*A protocol anchored by YuCROWN Corporation · 501(c)(3) — anchored, never owned.*


---

# 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/build/build-on-earth-linc.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.