Flowns: A Web3 name service

    Tracking Flowns domains on Flow

    Intro

    Readable names and rich-data on-chain identities are indispensable infrastructure in the digital world. Domain names are indexes and profiles for owners. A name domain could store more information and assets on chain, then it becomes a personalized expression of their own.

    Flowns is a new generation of decentralized domain name service built on the Flow network. It is a resource-oriented domain name service based on Cadence smart contract language. The Resource model in Flow makes the Flowns service flexible and extensible, and based on the domain name NFT asset.

    Flowns is born in the community and gets a lot of support from the community. As infrastructure and the public good, Flonws will also belong to the community. We regard the domain buyer as a community member and supporter, most of the sale funds will be given back to the community by establishing a DAO.

    The Flow account model supports multi-public key binding. Therefore, when the Flowns service runs stably, the admin account becomes a multi-signed account by adding multiple public keys.

    In the future, the admin account will also be upgraded to a multi-signed account, and gradually transfer the management authority to the community. (Text source) (Image source)

    db_img
    Methodology

    For finding Flowns minting transactions I used 'A.233eb012d34b0070.Domains' in flow.core.fact_events table, and for finding the details of the Flowns I used EVENT_DATA:receiver for finding minters' address, EVENT_DATA:name to find the registered name, EVENT_DATA:parentName as the parent name of it (there are 2 types of parent names, ".fn" which can be minted by paying an $FLOW as for registration cost for a specified time and ".meow" which is gifting by Lilico wallet to it's users for free!) I also excluded two smart contracts from the minters, '0x233eb012d34b0070 which was related to the Flowns itself and '0xf6fcbef550d97aa5' which was labeld as "MyNFT" on Flow databases.

    Also, I used each wallet providers related payer address to find which wallet app the minters are using (for providing a better experience of interacting with blockchains and web3 space, wallet providers on Flow pay transaction fees for users)

    Lilico's payer: '0x319e67f2ef9d937f'
    Blocto' payer: '0x55ad22f01ef568a1'