Coinshift
Visit our websiteTwitterDiscord
Business
Business
  • 🌐Welcome
  • About Us
    • 🎦Introduction
    • 👁️‍🗨️Overview
    • 🧱Unified Dashboard
  • Primer & Peaks
    • 👉First Steps
    • 🌟Popular Features
  • Getting Started
    • 🛗Setting up a New Organisation
      • 🤳Request Access
      • 🎫Sign Up
      • 🏢Create a New Organisation
        • 💻Create Organisation from Coinshift Dashboard
        • 🔁Switch Organisations
      • 🗳️Add Accounts (Safes, Wallets, etc.)
        • 💸Add Existing Safes
        • 🗃️Create a New Safe
          • 💰Transfer Assets To Your Safe
    • 🤝Joining an Existing Organisation
    • 💻Logging In
    • 🔔Setup Notifications
      • ⚒️Connect Slack for an Org
      • 🛠️Connect Discord for an Org
      • 🧩Connect Slack for an Account
      • 🤖Connect Discord for an Account
      • 📩Viewing Notifications in Slack and Discord
      • ⏸️Change Account Preferences: Disconnect Notifications
      • 🔏Discord: Adding Coinshift Roles & Bot to private channels
      • ☑️Discord: Check Your Permissions
      • 👾Add Members to Discord Server & Channel
  • How-To Guides
    • 📋How to Add Accounts
    • 👥How to Add Members
    • ❄️How to make a Mass Payout
    • 📱How to interact with DeFi Apps
  • Coinshift Walkthrough
    • 📽️Overview
    • 🚻Users
    • 💹Portfolio Management
      • 💵Token Portfolio Tracking (ERC-20)
        • 🪙Add Additional Tokens
      • 🤖NFT Portfolio Tracking
    • 📈Reporting
      • 🎯Portfolio History
      • 📊Cash Flow Tracker
    • 📱Coinshift Apps
      • AAVE
      • CoW Swap
      • Hedgey
      • 1inch
      • LI.FI
      • ParaSwap
      • Request Finance
      • Superfluid
        • ⏲️Stream Payout
      • Transaction Builder
    • 🗳️Account Management
      • 🚮Remove Account
      • 🆕Add Signers
      • ✂️Remove Signers
      • 🔁Swap Signers
      • 💫Change Safe Name
      • 🎚️Change Threshold
      • ℹ️Adding a Safe as a Non-Signer
      • 🛄Filter A Safe
    • 🎛️Transaction Management
      • ☄️Proposals
        • 📬Proposal Management
        • 🔰Active And Discarded Proposals
      • 🪜Queue
      • 🔎History
      • 🛄Filter Transactions
      • ⏬Export Transactions
      • 🆕Add Labels and Notes
      • ❎On-chain Transaction Rejection
    • 📤Fund Management
      • ❄️Mass Payout
        • 🪙Mass Payout in a Single Token
        • ✨Mass Payout (Multiple Tokens)
        • ⏫Mass Payout via CSV Upload
        • 📑Duplicating Transactions
      • 🔁Recurring Payout
    • 📜Contact Management
      • 🆕Add Contact
      • ✏️Edit Contact
      • 🚮Remove Contact
      • 📝Bulk Import Contact
    • 🏷️Label Management
      • 🆕Add Label
      • ✏️Edit Label
      • 🚮Archive/ Unarchive Label
    • 👤Member Management
      • 🆕Add Member
      • 🚮Deactivate Member
      • 🔎Filter & Search Members
    • 📱Supported Wallets
      • 🔐Hardware Wallet Support
        • ☑️Prerequisite
    • ⚙️Settings
  • FAQs
    • ❔FAQ: General Information
    • ✨FAQ: Onboarding
    • 🔔FAQ: Notifications
    • 🚀FAQ: Transactions & Operations
    • 📱FAQ: Coinshift Apps
    • 🔐FAQ: Hardware Wallets
    • ❓Technical Concerns & Troubleshoot
  • Resources
    • 📖Glossary
    • 🧾Blog
    • 🌈Support and Community
Powered by GitBook
On this page
  1. FAQs

FAQ: Hardware Wallets

Find answers to some of the most commonly asked questions related to the hardware wallets here.

PreviousFAQ: Coinshift AppsNextTechnical Concerns & Troubleshoot

Last updated 1 year ago

How do I authenticate Safe transactions on my hardware wallet?

As noted in our , using Safe through a hardware wallet or a Web3 wallet offers the same features. The only difference is in how transactions are approved.

To validate Safe transactions on a hardware wallet, follow these steps:

  • Connect your hardware device to your computer and ensure it's unlocked (typically using your PIN)

  • Familiarise yourself with the necessary

  • Link your Ledger account with the Coinshift App

  • Initiate an on-chain transaction

  • Review and confirm the transaction details on your Ledger device

Voilà! Your action should now be reflected in your chosen account.

Always double-check transaction particulars prior to approval.

How to enable blind signing?

Users may receive a prompt on their device to enable Bling signing. Enabling blind signing is required to sign most of the transactions involving smart contracts. You can follow this to know more about it.

Follow the below steps to enable blind signing:

  • Connect and unlock your Ledger device

  • Open the desired application (For example- Ethereum, or Polygon)

  • Press the right button to navigate to Settings. Then press both buttons to validate.

  • Your Ledger device displays Blind Signing.

  • Press both buttons to enable transaction blind signing.

  • The device displays Enabled. You're done.

I am getting a "U2F browser support is needed for Ledger. Please use Chrome, Opera, or Firefox with a U2F extension. Also, make sure you're on an HTTPS connection" error message, what should I do now?

We have been informed that a number of users are experiencing difficulty establishing a connection between their Ledger devices and MetaMask. Please note that this issue is unrelated to Coinshift's functionality.

For assistance in resolving this issue, please consult the following resource- , . Kindly ensure that you follow the outlined steps accurately for a successful resolution.

I am encountering an error message "Wallet signature denied" or "Signing typed data is not supported by your wallet. Please sign the hash instead" while signing a Metamask transaction. What should I do?

If you are using a Ledger device in conjunction with Metamask and are facing the error message mentioned above when trying to sign a transaction, please follow the steps below to resolve the issue:

  1. Check Connection: Ensure that your Ledger device is securely connected to your computer.

  2. Select Ethereum App: Navigate to and select the Ethereum application on your Ledger device.

  3. Enable Smart Contract Data or Blind Signing : Within the Ethereum app on your Ledger device, go to the settings and enable the option for Smart Contract Data or Blind Signing. This will allow your Ledger to sign the necessary data for the transaction. Note that, this step is optional and required to be performed when prompted.

After completing these steps, try signing the transaction again through Metamask. If the problem persists, ensure that both your Ledger firmware and Metamask are updated to the latest versions. If you continue to experience issues, consider reaching out to Ledger or Metamask support for further assistance.

🔐
documentation
prerequisites
link
link 1
link 2