> For the complete documentation index, see [llms.txt](https://docs.rubyscore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubyscore.io/how-rubyscore-works/on-chain-confirmation.md).

# On-chain confirmation

#### 1) Multichain Reputation Score (MRS)

* **What it is:** a record in a specialized on-chain data registry reflecting your current multichain score.
* **How it works:** MRS can be **minted and updated for free**, fixing the current value (with a change history available via on-chain events).

#### 2) Score Level

* **What it is:** levels (tiers) that confirm a wallet’s on-chain achievements **within a specific ecosystem**. **There are 10 levels (1–10)**, each corresponding to a defined activity range.
* **How it works:** each **level mint** is a **step-by-step confirmation** of a reached threshold; levels are cumulative and can be upgraded as activity grows.
* **Properties:** levels are issued as **SBTs (soulbound tokens)** — **non-transferable**, verifiable on-chain proofs of progress.

#### 3) PoH ID (Proof-of-Human ID)

* **What it is:** an **SBT (soulbound token)** — a one-time “passport” **for a specific ecosystem**, based on your on-chain actions within it.
* **How it works:** PoH ID is minted once upon meeting the ecosystem’s requirements (rules and thresholds set by the project); it can be accompanied by local levels/badges.
* **Properties:** **non-transferable**, serves as on-chain proof of “human-ness” based on your on-chain contribution.

#### 4) Reputation Domain (linked to MRS)

* **What it is:** a human-readable reputation name/domain associated with your **Multichain Reputation Score (MRS)**.
* **How it works:** minting the domain binds a display name to your wallet and **references the current MRS**. When MRS is updated, the domain reflects the new score. The domain record is stored in the **data registry alongside your reputation score**.

#### 5) Vote (favorite network voting)

* **What it is:** an on-chain vote that captures a user’s preference for a specific network/ecosystem.
* **How it works:** the user submits a vote for their “favorite network”; the vote is recorded on-chain, can appear in the user’s profile, and can be aggregated into **network ranking** metrics.


---

# 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:

```
GET https://docs.rubyscore.io/how-rubyscore-works/on-chain-confirmation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
