Domain Buying Architecture

Let’s start with the application’s user flow

After user registration has been done, users can start searching on the portal for their desired domains. Since we also have a copy of the domain searched, if not already purchased then the controller will move to the next step.

In the next step, we have a set of Domains defined as Premium Domains. If the domain exists on Premium Domain List, the pricing of that domain will be considered the same as a premium domain and returned with all info to the user.

Users will be allowed to bid on the domain or can buy with full upfront payment. Bidding is allowed with a minimum window of 50% of the price. And the domain will be put on a list to showcase to the public and bid. After 7 days, the highest bidder can get the domain.

From there, the user can own and configure the domain, the token will get minted thereafter, and registered on the user requested chains.

The client part of the DApp consists of plugins for Browsers and public API/ ABI for other platforms to consume to resolve data of the domain. Using that, anyone or any platform can provide the domain name to our smart contract, and the smart contract will reply with the address of wallet / smart-contract/ token / Block / IPFS / ipv4 or ipv6 IP address/websites / Social Media Link and so on, whatever owner has saved there.

Also, owners of NexBloc can resell, share or gift their NFT to the next person.

Data Flow

Each of NexBloc blockchains’ functions is built upon more traditional cryptocurrency technology and each blockchain supports traditional cryptocurrency operations. As a result, concepts such as an “address” (a hashed and encoded public key for conducting transactions) and a wallet (a representation of a collection of addresses owned by a single entity) apply to these blockchains and can be used to track and correlate transactions.

Last updated