Ledger Enterprise
Help Center
Help Center
  • Welcome to the Help Center
  • Fundamentals
    • Getting set up
      • Sign in and out
      • For Administrators
      • For Operators
  • Supported Networks
  • What's new
  • CORE
    • Workspace administration
      • Admin Rule
        • Edit the admin rule
      • Accounts
        • Create an account
        • Solana SPL token account
        • Direct Access EVM Accounts
        • Edit an account
        • Activate a view-only account
        • Generate a receiving address
      • Groups
        • Create a group
        • Edit a group
        • Delete a group
      • Whitelists
        • Create a whitelist
        • Edit a whitelist
      • Entities
        • Create an entity
        • Edit an entity
        • Delete an entity
    • Users
      • User Roles and Permissions
      • New users
      • Register on the Ledger Vault
    • Your Device
      • Initialize your Personal Security Device (PSD)
      • Update your Personal Security Device (PSD)
      • Configure the Ledger Cryptosteel
      • Device pairing: View your partition ID
    • Managing requests
      • Approve or reject a request
      • Track the status of a request
      • Recreate a rejected or failed request
    • Transactions
      • Create a transaction
      • Transaction fees & speed
      • UTXOs
      • Replace by Fee
      • Export transaction history
      • Vault Raw Signing Overview
    • Compliance capabilities
      • Proof of Reserve - Enable Message Signing on an account
      • Proof of Researve - Sign Messages
      • Address Screening and KYT
    • Using Vault Signer
      • Create a Vault Signer account
      • Connect your Signer account to the Ledger Live extension
      • Craft a transaction on Ledger Live with your Vault Signer account
    • Overview of the Ledger Enterprise API
    • Public Key Infrastructure (PKI) Implementation
    • Ledger Enterprise mobile application
      • Terms of Use
  • staking
    • Stake Cardano
      • Overview
      • Enable ADA Staking
      • Stake ADA with Figment
      • Reporting
    • Stake Cosmos
      • Overview
      • Enable ATOM Staking on your Ledger Cosmos Enterprise accounts
      • How to stake ATOM
    • Stake Ethereum
      • Overview
      • Enable ETH Staking on your Ethereum accounts
      • Stake ETH with Kiln
      • Stake ETH with Figment
      • Stake ETH with Blockdaemon
    • Stake Solana
      • Overview
      • Enable SOL Staking on your Solana accounts
      • Stake SOL with Figment
      • Solana Staking Reporting
    • Stake Polkadot
      • Overview
      • Enable DOT Staking
      • Stake DOT with Figment
    • Stake Polygon
      • Overview
      • Enable MATIC Staking
      • Stake MATIC with Figment
      • Stake MATIC with Kiln
    • Stake Tezos
      • Overview
    • Staking Providers
      • Stake with kiln
      • Stake with Figment
      • Stake with Blockdaemon
  • Web3: DeFi & NFT
    • Web3: DeFi & NFT Interactions
      • Web3 governance & configuration
        • Enable Smart Contract Interactions on EVM accounts
        • Enable Message Signatures on EVM accounts
        • Enable Contract Deployments on EVM accounts
        • Customize DApps catalog on EVM accounts
      • Vault DApps
        • DApp Provider Guide
        • Lido
        • Paraswap
        • Yearn
      • Interact with an external DApp via WalletConnect
      • Deploy a Smart Contract
      • Sign DApp messages
      • Interact with a smart contract
    • Raw Signing Best Practices
  • TRADELINK
    • Introduction
    • Best Practices
    • Run Tradelink as an Administrator
    • Operate Tradelink as a Custodian
    • Operate Tradelink as an Asset Manager
    • Operate Tradelink as an Exchange
    • Ledger Tradelink Terms of Use
  • Support
    • Troubleshooting
    • Security best practices
      • Ledger Stax Best Practices
    • Recovering your Vault Master Seed
    • Recover your Ledger Vault's master seed on a Nano S Plus
Powered by GitBook
On this page
  • Overview
  • Instructions
  1. CORE
  2. Compliance capabilities

Proof of Reserve - Enable Message Signing on an account

PreviousCompliance capabilitiesNextProof of Researve - Sign Messages

Last updated 2 months ago

This article is for Administrators only.

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.