Network
NeoFS network nodes run the same software and talk the same protocol but may have different roles. There are nodes that store data and process user API requests, they are regular storage nodes that form the Outer Ring. There are nodes that take care of network health, perform service tasks, such as data audit and payments settlements, and form the Inner Ring. There are not many of them and they use dBFT 2.0 consensus algorithm to coordinate their actions.
Inner Ring nodes are connected to Neo Blockchain. They are constantly monitoring events coming from the blockchain to synchronize their state and the state of NeoFS smart contract that manages users' money deposits and information about Inner Ring nodes themselves.
Since the Inner Ring is a critical infrastructure part, not every node may get this role. The node willing to join the Inner Ring should be registered in NeoFS smart contract in Neo Blockchain and pay some security deposit that is lost in case node starts to behave badly.
In addition, in the same way as Neo consensus nodes, NeoFS Inner Ring nodes try to achieve maximal possible geographical, political and network decentralization.
The main use case for NeoFS is dApps's data storage and content distribution. Nowadays most dApps do not store their assets in decentralized fashion that makes them not really distributed applications. In NeoFS, dApps can upload content and distribute it to clients via protocol gates using standard HTTPS protocol or, for example, using NeoFS API from mobile application.
dApps can access NeoFS directly from smart contract code. For instance, dApp's smart contract can query some data from NeoFS (with JSONPath filtering) and have some logic depending on this data. Storing data off-chain is significantly cheaper and easier to deliver to client.
Network Map
Inner Ring nodes monitor state of NeoFS storage nodes. Using this information, they maintain up-to-date Network Map. It is a multi-dimensional graph where nodes have attributes and are grouped by those attributes and their values. This allows using a special data placement function to find nodes that would store an object when putting or getting it in/from NeoFS network.
This approach allows not having any centralized meta-data storage keeping object's locations and not re-balancing data with every joining or leaving storage node, as it happens in DHT-based systems.
Work reliably in chaotic environment
As files are organized in directories in file system, objects are organized in containers in NeoFS.
Each container is served by a subset of storage nodes that satisfy storage policy defined for this particular container by the user. To calculate that nodes’ subset, storage policy filters are applied to Network Map. The resulting set of nodes is responsible for making sure that storage policy is satisfied and data is not corrupted. In case of success, they share users’ payment for data storage. One storage node may serve many containers, so if it behaves correctly small shares from each container summ-up in a significant reward. The same is true for the losses in case of container nodes’ misbehavior. This motivates nodes to keep an eye on other container members and properly perform all required replication, migration and data recovery processes.
Another non-obvious benefit of this approach is the bigger NeoFS network grows, the more stable it becomes, because the chance of network changes affecting a particular container is decreasing with the increasing number of nodes in the network. It means, unlike in DHT approach, the amount of required data migrations decreases with network growth.
NeoFS Blockchain Components
The main smart contracts that provide deposit and withdrawal of GAS tokens to/from NeoFS accounts and maintain the list of Inner Ring nodes, are on the Neo mainnet. NeoFS internal banking and data audit results are on FS chain (which technically is a sidechain to the main network). This allows to avoid pushing a large number of internal NeoFS transactions to the main Neo blockchain network. This approach also allows us to achieve complete anonymity of Inner Ring nodes and not to disclose them to other network nodes.
The main NeoFS network contract is deployed in the Neo main network. The role of this contract is to accept Neo GAS assets from users, and withdraw Neo GAS to users. The list of Inner Ring nodes is maintained in a standard native Role Management contract with a designated NeoFS Alphabet role,
Service contracts of the NeoFS network such as Network Map contract, Container contract, Balance contract, Data Audit contract, and Reputation contract are on the FS chain.
The Network Map contract is the main NeoFS network contract in FS chain. The roles of this contract are to manage the list of storage nodes, maintain the network map, keep snapshots of network map when an epoch switch happens, store the epoch counter (providing an interface for changing the epoch to Inner Ring nodes) and keep a set of network-wide configuration options. Epoch is a real-time period during which a permanent Network Map exists.
The Container contact is deployed in FS chain. The roles of this contract are to maintain a list of containers and provide such operations as to get a specific container by its identifier, to get a list of all user containers, and to get a list of all containers.
The Balance contact, being in FS chain, provides the internal NeoFS banking performing a large number of fast microtransactions based on the results of the NeoFS network.
The Reputation contract’s role is maintaining reputation ratings of Storage nodes. This contract is also deployed to FS chain to process a lot of invocations to process the view of Storage nodes' trust.
Neo main chain and FS chain do not interact directly. The bridge between the two chains is Inner Ring which subscribes to events from both chains. The Inner Ring nodes are responsible for servicing the NeoFS network, monitoring Storage nodes, and data integrity of the storage network.
The Inner Ring nodes are connected to Neo Blockchain. They are constantly monitoring events coming from the blockchain to synchronize their state, the state of the NeoFS smart contract that manages users' GAS deposits and information about the Inner Ring nodes themselves, and FS chain smart contracts.
Protocol Gates
To interact with existing systems using standard protocols, NeoFS has protocol gates. Gates are mainly maintained by users and not a part of NeoFS network. From the start, REST protocol gateway is provided, that allows accessing data from NeoFS using regular browser. AWS S3 gateway is also provided to allow users to make more sophisticated integrations. Technically one may easily develop own gate by using NeoFS protocol libraries.
