> For the complete documentation index, see [llms.txt](https://docs.fetcch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fetcch.xyz/universal-identity-layer/how-it-works/specifications.md).

# Specifications

Fetcch's Identity Layer offers a Unified Address System that merges numerous blockchain addresses into a singular, chain-agnostic identity. By using easily recognizable identifiers like "satyam\@metamask", users can effortlessly represent their identities across multiple platforms like Ethereum, Polygon, Solana, and BSC. With a staunch commitment to universal protocols, Fetcch Identities seamlessly integrate with the DID (Decentralized Identifier) standard, ensuring broad recognition and interactivity. Above all, emphasizing user-centricity, Fetcch guarantees full ownership through its non-custodial framework.

*Let’s take a closer look on the Idenitifiers:*

#### **Identity Structure**

Fetcch Identity's construct revolves around three core components:

* **Identifier**: Essentially, it's the unique tag picked by users, like "satyam" in "satyam\@metamask".
* **Delimiter**: Represented by "@", it acts as a bridge between the identifier and the provider.
* **Provider**: Refers to the specific blockchain or platform linked with the user, say "metamask" in the provided example.

#### **Address Framework**

With Fetcch Identity, users can tie multiple addresses, segmented into:

* **Default**: The go-to address for all activities triggered by the user.
* **Secondary**: Steps in as a backup, ensuring actions don't hit a roadblock when the default isn't usable.

#### **Identity Configuration**

Alongside the address setup, Fetcch Identity boasts an 'Identity Config', enhancing user flexibility:

* **Transaction Paths**: Users can set preferred transaction routes. Take "forcedSameChainPayment" - if turned on, it sidesteps bridge routes, tapping into secondary addresses when needed.
* **Token Choice**: For cross-chain transactions, the default pick is a stablecoin. Yet, users can tweak this based on their leanings.

In essence, these technical specs of Fetcch Identity are engineered for simplicity and efficiency, ensuring users navigate without a hitch.


---

# 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.fetcch.xyz/universal-identity-layer/how-it-works/specifications.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.