Tezos Domains for Developers
  • Introduction
  • Integrating Tezos Domains
    • Client Libraries
    • GraphQL
      • Mainnet
  • Smart Contract Design
    • Smart Contract Overview
    • Top-Level Domain Registrar
    • Ownership Scheme
    • Domain Data
  • Contract Interoperability
    • Proxy Contracts
    • Name Resolution
    • Buys & Renewals
    • Auction Operations
    • Domain Operations
    • .tez TLD
    • Domains as NFTs
    • Affiliated Buys & Renewals
  • Deployed Contracts
    • Mainnet
    • Ghostnet
  • Audits
    • Audit by Quantstamp
    • Audit by Inference
Powered by GitBook
On this page
  • Reserved Keys
  • Tezos Domains
  • Etherlink
  • Web
  • OpenID
  • Gravatar
  • Social media
  • Developer accounts
  • Source control

Was this helpful?

  1. Smart Contract Design

Domain Data

PreviousOwnership SchemeNextProxy Contracts

Last updated 9 months ago

Was this helpful?

All records allow for storing arbitrary information in the "data" map:

type data_map = (string, bytes) map
map %data string bytes

All entries have:

  • A key that should have a unique meaning. There is a set of reserved keys for typical use, but users are free to create new keys.

  • A value which must be represented in JSON () and encoded in UTF-8.

Reserved Keys

Tezos Domains

All keys with the prefix td: are reserved for Tezos Domains-related metadata. We currently recognize:

Key

Meaning

Type

Example

td:ttl

The time-to-live of the record and an associated reverse record, if any (in seconds). If defined, it specifies the maximum time the record should be stored in caches and other secondary-storage mechanisms.

number

600

Etherlink

All keys with the prefix etherlink: are reserved for Etherlink-related metadata. We currently recognize:

Key

Meaning

Type

Example

etherlink:address

Your etherlink address.

string

0x0000000000000000000000000000000000000000

Web

The prefix web: is reserved for website urls.

Key

Meaning

Type

Example

web:governance_profile_url

string

OpenID

Key

Meaning

Type

Example

openid:<claim>

(e.g. openid:name)

see OpenID spec

"Alice Smith"

Gravatar

Key

Meaning

Type

Example

gravatar:hash

string

"0bc83cb571cd1c50ba6f3e8a78ef1346"

Social media

Key

Meaning

Type

Example

twitter:handle

The associated Twitter handle of the domain.

string

"BillGates"

instagram:handle

The associated Instagram handle of the domain.

string

"nasa"

Developer accounts

Key

Meaning

Type

Example

github:username

User's GitHub account name.

string

"torvalds"

gitlab:username

User's GitLab account name.

string

"foobar"

keybase:username

User's Keybase account name.

string

"foobar"

Source control

Key

Meaning

Type

Example

project:repository_url

Project's Git repository.

string

"https://gitlab.com/tezos-domains/contracts.git"

The governance post url which is desribing your Tezos Domains Delegate profile. More details .

The prefix openid: is reserved for OpenID claims. The values have their respective meanings according to the . The value types specified in the OpenID spec must be adhered to.

Any

To provide an avatar representing their account, users can equip their Tezos Domain with the MD5 hash of their Gravatar e-mail.

The on Gravatar in hexadecimal format.

RFC 8259
OpenID spec
Gravatar
here
https://talk.tezos.domains/t/how-to-become-a-delegate/34/1
OpenID claim
MD5 hash of the user's e-mail