Address & Asset Sharing

📘

In This Article

This article will cover the following.

• How to programatically share an address or asset with a participant of the Taurus Network.

Prerequisites

• Completing this Guide requires access to two PROTECT tenants that are both connected to the Taurus Network (TN).
• To complete this guide you will need to be comfortable programatically signing for approval. Please read the relevant SDK & Integration guide for Signing for Approval.

Introduction

Before transferring funds, pledging or initiating settlements, shared addresses must be established with the participant of the network. Once an address has been shared, the Taurus Network counter party will see a whitelisted asset request which they will need to sign. Once signed, the participant will have a verified address which they will be able to sent funds to. In addition to visual queues in the GUI, shared addresses will include a tnParticipantID when querying address related endpoints (list addresses, get an address, etc...).

Address Sharing Workflow

1. Share an address (participant)
2. Verify & Sign whitelisted asset request (counterparty)

Sharing an Address (Participant)

1. Identify the necessary parameters:
   1. the ID of the address you want to share.
   2. The Taurus Network (TN) participant ID. You can query participants with the List Participants endpoint.
   3. Optionally, any attributes you wish to override.
2. Call the Share an Address endpoint
3. A 200 Response indicates the request was created. At this point, the counterparty will have a whitelisted address request with your participant ID listed in addition to visual indications in the GUI that this is a taurus network request.

Verify & Sign (Counterparty)

❗️

Important: Verify Before Signing

It is extremely important that you always confirm that the Taurus Network (TN) participant ID belongs to the expected counterparty before signing. An incorrect ID could result in transferring assets to the wrong party as well as significant loss of funds.

Once signed, the address will show a verified label in the PROTECT GUI and will be marked as a trusted address.

This flow is the same as signing any other whitelist address request.

1. Verify the address is from the expected counterparty (see warning below!).
2. Sign the Whitelisted Address (WLA) request. Taurus Network (TN) requests pending signature are treated like any other request signature. Therefor, when you are signing via API, you will sign the request hash just as you would for any other request.