Documentation

ORYN is a coordination layer for Base. It gives people, projects, communities, assets, and agents a single, portable way to be identified, to earn trust, and to discover one another — so that applications can stop rebuilding the same social plumbing over and over.

1. Why a coordination layer?

Today, every onchain application reimplements its own notion of who you are, whether you can be trusted, and who you are connected to. Your identity in one app does not travel to the next. Reputation earned in one community evaporates at the border of another. The result is a fragmented ecosystem where participants are disconnected from the projects and communities that would value them most.

ORYN proposes that these three concerns — identity, reputation, and the relationship graph — are not application features. They are shared infrastructure. Pulled out into a common layer, they become composable: any app can read them, any contribution can compound, and coordination becomes the default rather than the exception.

In one sentence

ORYN is building a coordination layer for Base — a shared fabric of identity, reputation, and graph that ecosystem participants carry with them across every application.

2. The three primitives

ORYN is organised around three composable primitives. Each is documented in depth on its own page.

primitive i

Identity

Persistent participation across applications — one portable presence.

primitive ii

Reputation

Trust built through contribution, not purchase. Earned, decaying, contextual.

primitive iii

Graph

The relationships between every participant in the ecosystem.

substrate

Base

ORYN settles on Base — low-cost, high-throughput, and already home to a dense ecosystem.

3. How it fits together

An application integrates ORYN the way it would integrate any shared service: it reads a participant's identity, queries their reputation in a relevant context, and walks the graph to find related participants. Crucially, the same participant object is visible to every other ORYN-aware application.

// conceptual — the shape of an ORYN read
const participant = await oryn.identity.resolve("base:0xabc…");

participant.reputation.in("governance");   // contextual score
participant.graph.neighbors({ edge: "contributor" });
participant.graph.path(to: "base:0xdef…");   // trust path

Nothing here is final — ORYN is at the research and documentation stage (Phase 0). The interfaces above describe intent, not a shipped API.

4. Getting started

Read the Manifesto

Understand the thesis: the next layer connects participants. Read it →
Study the primitives

Identity, Reputation, and Graph each have a dedicated deep-dive with data models and open questions.
Follow the research

Three research tracks are public. Each becomes a building block of the protocol. Start with #001 →
Watch the repositories

oryn-docs, oryn-registry, oryn-graph, and oryn-sdk track the work in the open. Browse repos →

5. Design principles

Portable by default	Identity and reputation belong to the participant, not the application. They travel across the whole ecosystem.
Earned, not bought	Reputation reflects contribution over time. It cannot be purchased in a single transaction.
Contextual	Trust is not a single number. A participant can be highly reputable in one context and unknown in another.
Composable	Every primitive is readable by any application. Coordination compounds instead of resetting at each border.
Open	Open infrastructure, open research, open participation. The work happens in public.

6. Roadmap at a glance

ORYN ships in phases. Phase 0 (Genesis) covers brand, research, and documentation — the stage you are reading now. Subsequent phases introduce the Identity registry, the Reputation system, the relationship Graph, and finally the Protocol with an SDK and developer APIs.

Phase 0 — Genesis	Brand · Research · Documentation
Phase 1 — Identity	Registry · Profiles
Phase 2 — Reputation	Trust · Contribution
Phase 3 — Graph	Relationships · Discovery
Phase 4 — Protocol	SDK · Developer APIs

7. FAQ

Is ORYN a token?

No. ORYN is a research initiative building coordination infrastructure. There is nothing to buy here.

Why Base?

Base offers low fees, high throughput, and a large, growing ecosystem of people, projects, and communities — exactly the participants a coordination layer is meant to serve.

How can I participate?

Read the research, follow the repositories, and contribute. ORYN is built in the open, and reputation here is earned through contribution.