Skip to main content


Our immediate plan is to release the first working version and put it into production on the mainnet, because from there it is easy to create new features and, consequently, we speed up development.

First version

Panel so that holders can configure their resolvers, defining different information on-chain such as:

  • Address shortener of your preferred wallet on Cardano and other networks
  • Your Twitter, Discord, Telegram, Line, Viber, Skype, Email, Facebook, Whatsapp if you wish

In parallel with development and release, we will also develop:

  • you will be able to set a default profile picture (PFP)
  • you can set a default IPFS URL
  • you will be able to create a list of your coolest NFTs
  • you will be able to create a list of your personal or professional links (similar to
  • you will be able to define several other information that we will disclose when starting the development of this version
Browser Extension

We are already developing and it will detect when a resolver is accessed in a browser like Chrome, Brave, Edge and so it will direct to the IPFS address or a configured default profile, in addition to several other features unique to the extension such as getting information from others resolvers, possibility to save a resolver in your favorites list, various information about the Cardano network, address resolution compatible with different services such as Gmail, Telegram, etc.

DNS and traditional domains

It will be possible to attach a resolver to an existing traditional domain name (like so that it works as an extra domain for a resolver. So, if this traditional domain name is used in any of our tools, it will also be recognized as the resolver attached to it. Everything will be based on DNS settings for domains.

Identity (second version)

This is where we will give identity functions to a resolver, we will develop a multiplatform application (smartphone and computer) where it will be possible to search a resolver, get its data, save to favorites and even interact with native applications based on information from a resolver.

These are just some basic identity utilities, we will have others that we will only disclose when we start development.

We will also have and (or), a decentralized profile based on a resolver that you can share on social networks, email, messengers, etc.

Access (third version)

We will create the access function using a resolver where we will have a tool that will allow holders to have access in the virtual world but mainly in the physical world such as shows, events, stores, restaurants, malls, etc.

This will only be an access utility, we will have other uses that we will bring more information later.

In this release, we will develop an open source hardware/IoT that will communicate with a resolver (blockchain) to perform power on, off, open, close and release actions in the physical world.


To use the tools, you will need to have a resolver, both for end users and for owners of establishments, events, NFT, Token or Stake Pool projects.


Will a resolver be entirely dependent on third-party integration to function?

No, definitely not! We are creating a product that will be multiplatform and will have its own utilities, such as the application and the profiles mentioned in identity, the platform mentioned in access, the extension mentioned in social and several others that will come to exist.

Integration with dApps (web3) or Apps (web2) is just another layer of utility of an Resolver.

Will we have other uses besides those mentioned here for a resolver?

Yes, we already have at least four utilities that we don't mention here because we want to leave them for when they start to be developed.

What is a "traditional domain name"?

These are domains as we know them on the traditional internet, those that end with .gov, .com, .io, .club and many others. See a list of all existing domain names on the internet, or as we call it here, on web2.