> For the complete documentation index, see [llms.txt](https://gabriel-j-shapiro.gitbook.io/metalex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gabriel-j-shapiro.gitbook.io/metalex-docs/web-app-using-the-apps/profile.md).

# Your profile

Your **profile** (`profile.metalex.tech`) is your MetaLeX identity. It is tied to your wallet and is shared across all the apps — when a founder reviews your Expression of Interest, or your name appears on a certificate, it comes from here.

A profile is **optional but recommended**. You can also stay anonymous.

## Creating your profile (onboarding)

1. Connect your wallet.
2. Choose **Setup profile**. This runs a one-time **Authenticate** step (a free Sign-In With Ethereum signature) which creates your profile record.
3. Pick a profile picture and enter a name.

Prefer not to? **Stay anonymous** skips the whole step.

## Your profile page

Your profile page is a public-facing card showing your picture, name, an optional founder title, bio, social links, your **LeXcheX accreditation status**, and your wallet address and any multisigs.

To edit it, **Authenticate**, then open the edit form:

* **Name and bio.**
* **Accreditation** — shows your LeXcheX status, with a link out to [LeXcheX](/metalex-docs/web-app-using-the-apps/lexchex.md) to get accredited. Until you are accredited, public rounds are not open to you.
* **Socials** — verify your X/Twitter account (via its sign-in) and your Telegram (via the Telegram login widget).
* **Website and additional info.**
* **Privacy** — each field has a public/private control, so you decide what is shown.

Saving your profile is a plain save — no transaction, no gas.

## Delegation

The **delegation** page is for people who sign on behalf of a **Safe multisig**. Collecting multisig signatures for every legal agreement is slow, so delegation lets a Safe grant agreement-signing authority to a single wallet.

To set it up: pick the chain, enter your Safe address (it must be a multisig that lists you as an owner), and set an expiry date. **Sign delegation** proposes a Safe transaction — you then complete it from your Safe's own interface, where your co-signers approve it.

After that, the delegated wallet can sign cyberAgreements on the Safe's behalf until the delegation expires.

> **Under the hood.** Delegation registers the delegate against the protocol's agreement layer, so a signature from the delegate counts as a signature from the Safe when executing a cyberAgreement. Background: [CyberAgreementRegistry](/metalex-docs/protocol-reference/contracts/cyberagreementregistry.md) and [Sign a cyberAgreement](/metalex-docs/protocol-how-to-guides/sign-a-cyberagreement.md).

## Notifications

A **notifications** page exists but is **not yet functional** — it is a placeholder for a future release.

## Good to know

* Your profile follows your wallet. If you act from a different wallet, that wallet has its own (or no) profile.
* Verifying socials and accreditation builds trust with founders reviewing your investments — worthwhile if you intend to invest in founder-approval rounds.


---

# 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://gabriel-j-shapiro.gitbook.io/metalex-docs/web-app-using-the-apps/profile.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.