Identity Resolution

Different entities may choose to use different pseudonyms (in our case Ethereum addresses), some of these identifiers are reused and some are not. For those entities who chose to reuse a pseudonym, they may want wish for these resources to be identified. Examples of such resources could be a shipping line wallet, multi-sig wallet or eBL token registry. Read more about identifier resolution framework here.

TradeTrust's address resolution#

For TradeTrust, currently there are 2 ways of resolving identities, 1 is through a local address book, the other is via 3rd party resolver API. These are accessible from the gear icon on the far right of the top navigation bar on TradeTrust website.


Address Book (Local)#

Address Book is like a local phone book. The data is in a csv/excel format, where the minimal amount of columns are:

  • identifier (refers to the ethereum address)
  • name (refers to the resolved name that the company defined in their csv/excel sheet).


After importing the csv/excel sheet, previously ethereum addresses (where resolvable) should now be resolved to recognizable identities as defined within the imported sheet.

Address Resolver (Third party)#

In the settings page you can add your third party address resolver. It enables you to add a third party's endpoint to resolve Ethereum addresses to their entity's name. With Ethereum addresses being cryptic to end users, this Address Resolver will act as a digital "yellow pages", allowing end users to see familiar identifiers such as ABC Pte Ltd. Once the Address Resolver endpoint has been added, when you verify a document with an identifiable Ethereum address, it will look like the following:


You can see that the entity's name, resolver details and source will also be displayed above the resolved Ethereum address.

Note: There is a difference between "Resolved by" and "Source" parameters. Resolved by refers to the naming of the 3rd party resolver that the user has set in the settings page. Source (an optional field) refers to information that is verified by another party. For example, in NDI Myinfo, they have verified information from different agencies.

How to setup a 3rd party Address Resolver#

We will need to specify the following fields in the API:

  • Identifier (The ethereum address of the entity)
  • Name (The name of the entity)
  • Source (Optional:The source of the information)

A reference implementation of this service can be found at

How to add a 3rd party Address Resolver#

Clicking the "+ Add" button in the settings page will show you following:


We will need:


The "Name" input refers to the name of the address resolver that contains all the mappings of entities and their respective Ethereum address. For example, "BANKS.SG" could be the address resolver for all banks in Singapore.


The "Endpoint" input refers to the endpoint that will be called to resolve an Ethereum Address. A hosted endpoint is available at

API Header and API Key#

For the API to know that you are an authorised user, an API Key is required and you will need to pass it in through an API Header. An example would be x-api-key for the API Header and DEMO for the API Key.