Comment on page
Import from Parity Signer or Polkadot Vault
These are the docs for the app called Polkadot Vault, if you're using an old version of Parity Signer, the process will be slightly different. We will provide more details in the future but please get in touch if you need any help.
What follows is a guide on how to use Polkadot Vault with Talisman to safely secure your accounts, without compromising on your experience in the multi-chain Paraverse.
To sign transactions on a substrate blockchain like Polkadot, the signing device needs access to some information about the chain. We'll refer to this information as the metadata.
Without the metadata, the device would be limited to only signing a few specific transaction types on a few specific chains (as is the case with Ledger cold wallets - no crowdloans and no staking!).
With Polkadot Vault, the chain metadata can be transmitted to the device by scanning a QR code.
But we want to be sure that the metadata hasn't been tampered with.
As a Polkadot Vault and Talisman user, you have the choice to place your trust in either the metadata portals above, or alternatively in the security of your Talisman wallet itself.
The pros and cons of each approach are as follows:
Option 1: Trust the Metadata Portals
- Pro: At the time of writing, this is the ecosystem default
- Pro: For existing Polkadot Vault users, this doesn't require you to change your Vault at all
- Con: Doesn't support some parachains
- Con: Each metadata update must be signed by a human, which can mean after each chain runtime upgrade you will be unable to sign transactions for a short while
If you would prefer to use the metadata portals (or if you're already using Polkadot Vault with other wallets and you're just looking to use it with Talisman too), you can skip straight to Step 2 to continue setting up Polkadot Vault for use with Talisman.
Option 2: Trust the Talisman
- Pro: Works for every parachain, all the time
- Pro: Once set up, is very easy to use (the core team uses this approach as they prefer the UX)
- Con: You can only use Talisman to update your metadata, unless you reset your Polkadot Vault (so there is some wallet lock-in)
- Con: Requires some initial set-up (which is detailed below)
If you would like to try our preferred approach, you must first remove the pre-installed Verifier Certificate which ships with Polkadot Vault.
Instead, you will be signing your own metadata updates via some open sourced code in the Talisman wallet.
To remove the default verifier certificate, first BACK UP ANY ACCOUNTS YOU HAVE CREATED ON THE DEVICE. Removing the certificate will reset your Vault (and remove your accounts).
This bears repeating, so:
🚨 BACK UP ANY ACCOUNTS YOU HAVE CREATED ON THE DEVICE BEFORE PROCEEDING 🚨
Next, follow along with these steps:
Removing the Verifier Certificate
That's all that you need to do on your Polkadot Vault device.
The signer for your chainspecs and chain metadata QR codes will be the first account created when you set up your Talisman wallet.
If you reset your Talisman wallet, you will need to set it up with the same seedphrase again in order to keep using your Polkadot Vault. If you set it up with a different seedphrase, you will also have to reset your Polkadot Vault.
We will be adding the option to select from any of your accounts for signing QR codes in a future version of the wallet.
Add Key Seton the app and then:
Add new Key Setif you would like to set up a new account with a new seedphrase, or
Recover Key Setif you already have a seedphrase you would like use.
Follow the prompts to set up your account.
Open your Talisman and go to the Add Account section. Select Import Polkadot Vault and then Turn on Camera.
Next, scan the QR code on the Polkadot Vault app which is shown when you select your key set and then the Polkadot network account:
Scan the QR code from this section of your Polkadot Vault
You will then be presented with a screen in your Talisman to enter a name for your account, and you will be given the option whether or not to restrict the account to a single network.
You should turn this option on if you use a different derivation path for each network. If you don't, or if you don't know what a derivation path is, it is best to leave this option turned off. More information on the difference between these options can be found in the appendix.
This next step begins with the sign transaction prompt, so you will need to create a transaction to continue!
Pick your favourite dapp, or if you don't have one then you can use the send funds feature of your Talisman wallet. In this example we're going to send 1 DOT from one account to another.
Select a token
Select a sender
Select a recipient
Enter an amount
Open the QR code prompt
Select Add Network
Select Update Metadata
Scan QR code
Scan QR code
Congratulations! You're now using Polkadot Vault and Talisman to secure your seedphrase!
We've seen this error intermittently on the Send Funds confirm screen, but have been unable to determine its cause yet. Our recommendation for now is to try and send the tokens again, it's likely to work on the second attempt.
Your device has no metadata for the network you're trying to sign a transaction on. This metadata is required in order for the device to add your signature into the transaction payload, which will be submitted to the chain.
If you see an error titled
Something has gone wrongand the description includes a message like so:
Network polkadot is verified by the general verifier which currently is public key: c46a22b9da19540a77cbde231975fd90485c72b4ecf3c599ecca6998f39bd57, encryption: sr25519. Received load_metadata message is verified by public key: <key-here>, encryption: sr25519. Changing the general verifier or changing the network verifier to custom would require wipe and reset of Vault.
This error occurs when you try to update the metadata for a chain using a different method to the one you used to set that chain up.
Vice versa, if you tried using a QR code from a metadata portal or one with a Parity/Nova Wallet logo in the middle, try switching to the
Talismanoption by using the dropdown:
Switching from the Parity-signed QR code to the Talisman-signed QR code
When using Parity Signer or Polkadot Vault, there are two approaches you can take to organising your accounts on the signing device.
Talisman supports both approaches, but there are some caveats to consider, so we recommend a quick read through this guide to ensure a smooth and confusion-free experience.
Method 1 is more straightforward than method 2, but it requires more manual account management on your part. If the idea of using a single account for all chains sounds appealing to you, skip through to method 2.
The first method is to use a different account derivation path for each chain.
For example, your Kusama account might use the derivation path
//kusama, while your Basilisk account might use
When using this method, it's best to import each account with the 'Restrict account to
Network Namenetwork' option switched on to prevent confusion and errors.
Turn this on for single-chain accounts
This will tell your Talisman wallet to only show each account when interacting with the chain it is configured for, which will help you avoid two possible error scenarios:
- 1.You won't be able to create invalid transactions (i.e. transactions on the wrong chain) with this account. These are transactions which if scanned by the signing device it will refuse to sign them.
- 2.Because the
Receive fundsview will only show this account for the one chain, you won't accidentally send tokens to this account on the wrong chain. You would want to avoid this, because as you cannot sign transactions on other chains with this account, if you send it some tokens on the wrong chain you won't be able to access them.
Alternatively, a single derivation path can be used for all networks with the 'Restrict account to
Network Namenetwork' option switched off.