UNS Resolver Fields
Introduction
Resolver fields are information attached to a name that can have different types and properties depending on the rules defined below.
Resolver Field Model
Field | Type | Allowed Values | Description |
---|---|---|---|
field_id | String | UUID format | ID of the resolver field |
key | String | RESOLVER_FIELDS_ENUM | Type of the resolver field within the allowed ones |
scope | String | SCOPE_ENUM | Scope of privacy of the resolver field |
value | String | - | Value of the resolver field |
display_value | String | - | Display value of the resolver field, the same as value by default. |
{
"key": "BIO",
"scope": "PUBLIC",
"field_id": "39252d38-27c8-5790-9b92-cbe47c1ec644",
"value": "ABC",
"display_value": "ABC"
}
Resolver fields rules
The table below specifies the rules for each type of resolver field.
ALLOWED_PRIVACY is the most exposed that type of field can be, with public being the most exposed and private being the least exposed.
ALLOWED_VALUE specifies if there is a specific format needed for that field to be created, in case the cell is left blanks it means there are no restrictions on string format
ALLOWED_NUMBER specifies the maximum amount of fields of that type a NAME can have, in case the cell is left blank it means there is no limit.
KEY | ALLOWED_PRIVACY | ALLOWED_VALUE | ALLOWED_NUMBER |
---|---|---|---|
PUBLIC | |||
PHONE_NUMBER | TYPE_ONLY | ||
PUBLIC | |||
GLOBAL_ID | PUBLIC | ||
PUBLIC | |||
WALLET | PUBLIC | ||
NAME | PUBLIC | ||
BIO | PUBLIC | ||
URL | PUBLIC | ||
DATE_OF_BIRTH | TYPE_ONLY | ISO 8601 String | 1 |
ADDRESS | PUBLIC |
Updated about 1 year ago