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
      • Policies
    • 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
      • How to use the app
      • FAQ
  • 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
  • General best practices
  1. Web3: DeFi & NFT
  2. Web3: DeFi & NFT Interactions
  3. Web3 governance & configuration

Enable Smart Contract Interactions on EVM accounts

PreviousWeb3 governance & configurationNextEnable Message Signatures on EVM accounts

Last updated 2 months ago

This article is for Administrators only.

Overview

Smart contracts are autonomous programs running on Ethereum & other EVM blockchains. Smart contracts are the technology underlying decentralized finance (DeFi), non-fungible tokens (NFTs), and many more decentralized applications (DApps).

To interact with a smart contract, user accounts submit specific transactions that execute a function defined on the smart contract, such as a token mint function on an NFT contract, or a token swap function on a Decentralized Exchange (DEX) contract.

You can enable smart contract interactions for any Ethereum or EVM account (Polygon, BSC, etc.). The step 4 web3 rules of the account creation or edition procedure now lets you activate and configure a rule to govern smart contract interactions for the account. Activate the feature by clicking on the Toggle button, and configure your Smart Contract governance rule according to your needs.

Interacting with smart contracts can put funds at risk. We advise users to educate themselves about smart contract risks before activating smart contract interactions.

Instructions

  1. Select creator to define which operators can create smart contract transactions. You can select up to 20 operators or a single group.

  2. (optional) Click Add amount range . Note that the Amount parameter only applies to the amount of crypto you are sending to the contract. It does not impact the ERC20 token amounts transferred to or from your account due to the smart contract interaction

  3. (optional) Click Add whitelist to restrict interactions to whitelisted smart contracts which you trust. You can select up to four smart contract whitelists from the drop-down. Then, click Add whitelist to confirm.

    • Only whitelists of the Smart Contract type are listed. Note that if a DApp contract is not included in any of the selected whitelists, operators won’t be able to interact with the DApp. This is also true for ERC20 token contracts.

    • Note that Whitelists pending creation or edition approvals aren't listed.

  4. Use the approval workflow section to define which Operators must review and approve smart contract interactions created in the account. You can define up to three steps.

  5. Confirm the creation of your Smart Contract Interaction rule and review the rule on your Personal Security Device. Once all required Administrators have reviewed and approved the account creation or edition request, according to your workspace's admin rule , the Smart Contract Interaction rule will be effective for the account.

Please note that Creators are allowed to perform all the smart contract interactions initiated by Vault DApps. Some of these interactions (e.g. swap DAI for MATIC) can move funds on ERC20 children accounts. Creators should be chosen carefully, as DApps will effectively let them perform operations on all ERC20 children accounts.

General best practices

  • Do not enable Smart Contract Interactions for an account holding higher amounts of funds than what you intend to use with Smart Contracts.

  • Try segregating Smart Contract accounts with one account per smart contract or DApp you wish to interact with. For example

  • One account dedicated to Paraswap trading, which you top up before trades and withdraw from after trades

  • One account dedicated to ETH liquid staking on Lido

  • One account dedicated to to NFT trading on NFT marketplaces

  • Although Vault DApps features smart contracts which have been audited by multiple independent third-party firms, we encourage you to carry out your own due diligence before interacting with any smart contract.