🔮FNS Architecture

The FNS system is based on smart contracts and IPNS. The smart contract is responsible for registering and managing FNS domains, while IPNS is used to resolve the mapping between FNS domains and the corresponding content identifiers (CIDs) of the data stored on the Filecoin network.

The FNS architecture is based on Filecoin EVM smart contracts and the IPFS naming system (IPNS) to implement domain name registration, renewal, and transfer operations. The FNS architecture is illustrated in the following diagram:

• FNS Ddomains

FNS domains are easy-to-read domain names that can be used to access data stored on the Filecoin network. Users can register FNS domains through the FNS contract, and associate them with the CID of their stored data. FNS domains can be used to represent various types of data, including personal data, files, and applications.

• Content Identifier (CID)

The CID is a unique identifier for data stored on the Filecoin network, similar to the hash value used in IPFS. Each CID uniquely identifies a piece of data on the network and can be used to access that data. CIDs are used in FNS to map the FNS domains to the corresponding data stored on the Filecoin network.

• FNS Contract

The FNS contract is an ERC-721 compliant NFT contract that manages FNS domains. It provides functions for domain registration, renewal, transfer, and resolution.

• Resolver

The resolver is a smart contract that maps FNS domains to CIDs. It is responsible for resolving an FNS domain name to the corresponding CID and retrieving data from Filecoin.

• Integration with IPFS Decentralized Storage Space

The FNS system integrates with the IPFS decentralized storage space, allowing users to access data stored on IPFS through their domain names. The FNS system includes an IPFS node to ensure system stability and performance. The system uses IPFS's PIN service to ensure that data stored on IPFS is not lost due to node failure.