# Sign in with your wallet

> Review a validator-portal login message and sign it through the browser wallet or manually.

Source: https://docs.iceroot.com/wallets/sign-messages/

A signed login message proves control of a signing identity. It does not transfer funds, pay a fee, or register a validator.

## Set up a signing identity

In the browser wallet, open **Settings → Manage signing identity**. Create or restore a Heartwood devnet identity, then keep its recovery phrase offline.

![Signing identity page showing a public devnet address and public key, with Sign a message and Copy public key actions.](https://docs.iceroot.com/screenshots/signing-identity.png)

_The public key identifies the account. This example uses a disposable devnet identity._

Your recovery phrase and wallet password stay in the wallet. The portal never needs either one.

## With the browser extension

1. Open the [validator portal](https://validators.iceroot.com/) and choose **Sign in**.
2. Select **Browser wallet**, then **Connect browser wallet**.
3. Review and approve the connection in the wallet tab.
4. Choose **Sign in wallet** in the portal.
5. Check the website, identity, network, and complete message in the wallet, then select **Sign message**.

The portal verifies the signature and opens your validator space.

## Sign manually

1. Choose **Sign manually** in the portal.
2. Paste your identity’s public key and select **Get sign-in message**.
3. In the wallet, choose **Sign a message**, paste the exact message, and select **Review message**.
4. Check the website and message, then choose **Sign message**.
5. Copy the public signature JSON back to the portal and select **Verify and sign in**.

![Wallet approval page displaying the local validator portal origin, public identity, full sign-in challenge, and Sign message button.](https://docs.iceroot.com/screenshots/signing-approval.png)

_Review the full message inside the wallet. This example targets a local development portal and authorizes no transaction._

Do not edit the copied message. Each message is tied to the portal, browser session, account, and expiry.

## If the message expires

Request a new message and sign it again. An old signature cannot approve the new message. Rejecting a request does not grant access.

Developers can read the [wallet provider guide](https://docs.iceroot.com/developers/wallet-provider/index.md) for the integration contract.
