Mt Pelerin
AppWebsiteGithub
Bridge Protocol
Bridge Protocol
  • Introduction
  • Bridge Protocol
    • Overview
    • Bridge token
    • Rule engine
    • Compliance registry
  • Security and audits
  • Changes from v1 to v2
  • Guides
    • Creating a new token
      • 1. Choosing a network
      • 2. Connecting an address
      • 3. Managing aliases
      • 4. Generating the token contract
    • Managing a token
      • Sending tokens
    • KYC/AML provider workflow
Powered by GitBook
On this page
  • Creating a new alias
  • Importing aliases
  1. Guides
  2. Creating a new token

3. Managing aliases

Tutorial on how to use Bridge Protocol to configure and deploy a new tokenized asset - Part 3: Managing aliases

Previous2. Connecting an addressNext4. Generating the token contract

Last updated 4 years ago

With aliases, Bridge Protocol lets you give human-readable names to the multiple addresses contained in your seed phrase.

With this system, you can organize names for different addresses according to the needs of your workflow and facilitate your overall interaction with Bridge Protocol.

Creating a new alias

To create a new alias, click on the alias icon at the bottom left of the screen, then on the "Add new alias" button.

ID (first address): This will display the first address of the default derivation path of your hardware wallet / seed phrase. That address will serve as the identifiant for the whole hardware wallet / seed phrase.

Alias: Here you can give any name that you want to the address.

Derivation path: Choose a new derivation path to get a new address.

Address: The address that is derived from the derivation path chosen above.

You can add, edit and delete aliases at any time.

Importing aliases

You can import aliases with a JSON file structured like this example:

[{"derivePath":"m/44'/1'/0'/0/0","id":"0x11f248151c4843c9fd02eb372f6eb7d319197d9e","address":"0x11f248151c4843c9fd02eb372f6eb7d319197d9e","name":"Signer address"},{"derivePath":"m/44'/1'/0'/0/01","id":"0x11f248151c4843c9fd02eb372f6eb7d319197d9e","address":"0xc03460a8e0b97099edba59078574154548eb6142","name":"Owner address 1"},{"derivePath":"m/44'/1'/0'/0/02","id":"0x11f248151c4843c9fd02eb372f6eb7d319197d9e","address":"0x9a5c42fedef3bcee281d8df2e54a0442ff04a63f","name":"Compliance manager 1"}]
Example of aliases