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