Managing ONCHAINID

On the blockchain, stakeholders are represented by an identity smart contract called the ONCHAINID. This open source protocol is the chosen implementation for the decentralised identity framework. It is mandatory for any person (physical or moral) receiving ERC-3643 tokens to have this ONCHAINID deployed as it is the technology used to perform:

• KYC and AML checks
• Eligibility checks
• Transfer compliance checks

Deploying an ONCHAINID

Pre-requisites

At this time, a deployed ERC-3643 is required to deploy an ONCHAINID via Tokeny's API.

Investors

Having previously collected all the required information to create your investor Identity (see below), you can then call the whitelisting endpoint to:

1. Create the identity on Tokeny's Identity Provider
2. Deploy the ONCHAINID
3. Authorize your investor on the token

Currently, you can only deploy an ONCHAINID in the context of an existing and deployed ERC3643.

Agents

An ONCHAINID for an agent will be deployed automatically when you create an agent access.

Managing identity data and onchain credentials

Common identity data

Tokeny's Identity Provider defines the Standard Schema for an Identity to be valid. Below, you can see a breakdown of this Standard Schema:

Common fields (both for Individuals and Corporates)

[{
    "address": "string, valid eth address",
    "alias": "string, less than 40 characters"
}]

[{
    "exposed": "true or false",
    "details": "string"
}]

Individuals

Institutional

[{
    "first_name": "string",
    "last_name": "string",
    "gender": "Male or Female",
    "birthday": "ISO Date",
    "nationality": "ISO Country",
    "institution_admin_title": "String",
    "institution_admin_relation": "String",
    "email": "String",
    "phone": "String",
    "passport_number": "String",
    "id_number": "String"
}]

Occupation and sector of activities

The following values are available for the ONCHAINID Standard Schema for occupations and activities:

• Electricity companies
• Finance
• Insurance
• Bank
• Traders
• Confectionery
• DIY
• Post, mail and deliveries
• Medical equipment and health products
• Drink
• Dairy products
• Cosmetics
• Consumer Consumption
• Agriculture
• Seeds
• Brewery
• Pharmacy
• Tobacco
• Rail transport
• Wind turbine manufacturers
• Energy
• Health
• Consumer Electronics
• Cement
• Aeronautics, Aerospace and Defense
• Agribusiness
• Cruises
• Appliances
• Electrical equipment
• Industrial machinery
• Entertainment & Media
• IT technologies and services
• Entertainment
• Music Production (Majors)
• Programming & Software
• Information and Communication Technologies
• Telecommunications operators
• Advertising
• Sporting equipment manufacturers
• Luxury
• Catering
• Distribution
• Large distribution
• Heavy industry (excluding energy)
• Computer equipment
• Tires
• Automobile Manufacturers
• Building, construction and public works
• Mobile phones
• Telecommunication and Network Equipment Manufacturers
• Chemistry
• Mining activities
• Oil companies
• Airlines
• Shipping of goods
• Transportation

As an appointed agent of an ERC-3643 consuming this Identity, you can fetch the data of the investors you manage.

Offering-specific identity data

In addition to the Standard Schema, you can also create offering specific data. To set them up, please contact your Account Manager.

Onchain credentials

Identities follow the Decentralised Identity framework. On top of the ONCHAINID as the Decentralised Identifier (DID), Tokeny also enables the easy management of Verifiable Credentials.

Those credentials represent the proof of data onchain, signed by a Trusted Issuer (KYC agent, bank, crypto exchange, etc.). They are a hashed version of the data, containing the schema of validated data for you to be able to compare what you have with the issued proof (credential).

You have several ways to consume those data:

1. Proof only
2. Compare your own data against the proof
3. Request data

Consuming the credentials

If you only need the proof of data, not the data itself (KYC/AML check, nationality, majority...), you can directly rely on the credential(s) you find on the ONCHAINID.

Compare your data against the proof

If you want to compare the data your received against the emitted proof, perform the following actions.

Step 1: Get the type of credential

First, you need to fetch the identifier of the credential you're looking. You can find below a list of standard credential types.

Step 2: Get the credential

Once you have the identifier, you can directly get the value from the ONCHAINID.

Step 3: Fetch the proof schema and signing algorithm

On top of the actual data proof, a credential is represented by the proof schema: the list of data validated by the Trusted Issuer.

Step 4: Sign your data

The proof schema gives you the list of fields you need to sign to match with the signature. Use whatever cryptographic library you're comfortable with to sign the data with the signing algorithm.

You can then check if the result of this operation matches the credential fetched on step 1. If it is not the case, it means that part or entirety of the data you have is not the one that was verified by the credential.