# Proof of Reserve - Enable Message Signing on an account

{% hint style="success" %}
This article is for Administrators only.
{% endhint %}

## Overview

As a Ledger Enterprise user, you will now be able to define and use **Message Sigining** capabilities across all supported networks. This enables you to sign **Proof of Ownership** messages, should you require it for Compliance purposes. Indeed, signing messages with a private key can be used to prove that an institution controls the private keys that correspond to its public addresses.

You can enable **Messge Signing capabilities** for any account, across any supported networks. For EVM networks, the step 4 **web3 rules** of the account creation or edition procedure already let you activate and configure a rule to govern message signatures for the account. Activate the feature by clicking on the Toggle button, and configure your Message Signing governance rule according to your needs.

For non-EVM accounts (Bitcoin, Tezos or even Vault Signer accounts), you can now also create a Message Signaure rule to leverage these capabilities:

* For accounts tha do not support Staking, such as Bitcoin or Ripple, the Message Signature rule will appear at the **4th step** of the account creation flow;
* For accounts that do support Staking, such as Tezos or Solana, the Message Signature rule will appear at the **5th step** of the account creation flow.

Note that signing a Message is a fully off-chain operation that do not let you send funds. However, on smart-contract enabled networks, the signature provided can be used to perform advanced on-chain operations, such as granting a Token Approval.

## Instructions

1. During the creation or editing of an account of relevant chains, Step 4 allows you to activate the **Message Signature** feature. 
2. Select **creator** to define which operators can **create message signature requests**. You can select up to 20 operators or a single group. The selected operators will be able to initiate a message signature process through through the UI (or DApps for EVM accounts). See Sign Messages for details.
3. (*Optional)* Use the approval workflow section to define which Operators must **review and approve** message signature requests. You can define up to three steps.
4. Confirm the creation of your **Message Signature rule** and review the rule on your Personal Security Device. Once you've reviewed the rule on your PSD and confirmed, an account creation or edition request is created.
5. Once all required Administrators have reviewed and approved the account creation or edition request, according to your workspace's admin rule , the **Message Signature rule will be effective for the account**.

<figure><img src="/files/sKXScgom6BFVWhEziKAB" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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://help.enterprise.ledger.com/help-center/core/compliance-capabilities/proof-of-reserve-enable-message-signing-on-an-account.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.