Frequent Questions Privacy policy Terms and Conditions
1. Frequent Questions:
Q: What are the basic processes FileStorm participates in? A: Download the mining node program, install and run it, and register at Read details。 Q: What is FileStorm's requirement for mining hardware? A: For the time being, only Linux is supported during the public beta. At least 2 cores CPU, 4 GB memory, hard disk support 1 TB and 8 TB. (More hard disk sizes will be available in the future). It is recommended that you choose the following two operating systems: CentOs 7.4 64 bit (make, GCC and glibc are needed for the installation package, so it is recommended to install the full version) and Ubuntu 18.04 LTS. Q: Please explain Vnode, SCS, Verification Node, Super Nodes, Mining Node, Storage Node. A: The FileStorm block chain is a sub-chain of the ink block chain. Mockers adopt an extensible mother-child chain architecture. Vnode is a node on the mother chain. SCS is a node in FileStorm's exclusive ink sub-chain. Each SCS is connected to a Vnode. Verification nodes are out-of-block nodes on FileStorm and enjoy out-of-block rewards. FileStorm adopts the dPOS consensus, so it needs to pledge a certain number of FSTs (2 million) to participate in the block after the verification node is recruited and elected. Each mining node is bound to a verification node and gives it 10% of the revenue. So we also call verification nodes supernodes. Mining node is the node used for storage in FileStorm sub-chain, which can gain benefits. So the mining node is the same as the storage node. Because most of the nodes on the FileStorm platform are used for storage and mining. Q: Why is super node testing invitation? A: There are only 121 supernodes at most. Twenty-one participants were invited early. The quantity is small. But two million FSTs need to be pledged to participate. So we will only invite individuals and teams who are really willing to participate in the Super Nodes to join us in promoting FileStorm to participate in public beta in the future. Q: Please explain the differences between FST, COIN and MOAC. A: FST is called FileStorm Token. It is an ERC20 pass issued by FileStorm platform on the chain of Mokka blocks. In the future, we can exchange other digital assets on the exchange. COIN is a usage pass for internal circulation of FileStorm. Users use COIN to purchase storage space, and miners provide storage to earn COIN. COIN can exchange 1:1 equivalent with FST free of charge at any time. Payment of COIN between users is free. Payment of FST requires a small amount of MOAC as fuel. MOAC is the original passport of the Mokka block chain. It will not be displayed on the FileStorm platform. Q: Why is the FST ERC20? A: The ERC20 of FST is different from the ERC20 issued in ETF. This is ERC20 issued on the chain of Mokka blocks, which corresponds to the original Coin on the exclusive sub-chain of FileStorm. Coin can be used after being dug out by miners. There is no efficiency bottleneck. FST can be used for trading and liquidity on exchanges. Q:How do you know that the stored node program has run successfully? A:Use the following instruction:
Looking at the log file, tail - 100F storm. out, the following information appears to indicate that it is in normal operation
StormCatcher has started. Your storage miner is ready to work.
Q:How do you know that node registration has been successful? A:Use the following instruction:
Seeing the following log indicates that the A device has been registered successfully and has not been partitioned yet.
/dev/sda1 (A device directory) verify IPFS file
not generated shard ID!
See the following log to indicate that A equipment has been registered successfully, has been added to the fragmentation, mining
/dev/sda1 (A device directory) verify IPFS file
wait file verify handle!
Q:How long will it take to register for mining? A:Mining nodes do not dig as soon as they are registered. First, it is added to a reserve pool to wait. When there are enough machines of the same size in the reserve pool, the system automatically synthesizes these machines into a storage unit called Shard. Now the size of Shard is set at 10. That is to say, only if there are 10 alternative slices in the pond, the storage slices will be generated. Only when the miner enters the fragmentation can it work, and can it regularly obtain benefits. The waiting time depends entirely on how many new miners are added to the mine. Q:What are the benefits of mining now? A:Up to now, the one-day profit of pledging 1000FST/1TB mining is about 6FST, and 1FST is about 1.5RMB. Specific earnings will vary slightly every day. Please refer to the latest official announcement. Q: Where can I see the revenue? A:On click the address in the upper right corner, and then click to view the assets, you can see the mining revenue. The proceeds are distributed in the form of Coin. It is distributed once a day. The Coin can be proposed by the FST and converted into other assets on exchanges in the future.
2. FileStorm User Guide
FileStorm is an IPFS-based de-centralized storage platform implemented in the Mohist sub-chain. Detailed description can be found in this FileStorm - IPFS storage platform implemented on the Mozier sub-chainThere are three types of users of this platform.
       1.Storage Provider: Storage Provider will provide hardware devices for storage, such as computers with large capacity hard disks, or customized hardware boxes. Devices need to install FileStorm programs to link ink fileStorm subchains to IPFS networks. Providing storage for FileStorm yields benefits, commonly known as storage mining.
       2.Application Deployer: Application Deployer is the creator of FileStorm subchain. They can build a special sub-chain to store their applications. The application deployer has to bear the cost of running the FileStorm sub-chain. (Ink will also deploy a FileStorm sub-chain as the application deployer for users.)
       3.Storage users: Storage users use applications deployed by application Deployers to store and read files. Storage users do not have to pay for using FileStorm. But it may have to bear the cost of using the application.
3. FileStorm Consensus
       FileStorm consensus is a dPOS consensus based on ProcWind consensus. DPOS, Delegated proof of stake, the consensus of delegated rights and interests needs to select a group of miners'nodes for block production and scheduling. The owners of these rights need a mortgage pass. Mortgage passport will be deducted if any node fails to block out normally or verify the block out of other nodes.
       These nodes are called validation nodes, or out-of-block nodes. Verification nodes rotate out blocks in sequence, one block per n seconds, n can be set, now set to 10. The difference between FileStorm is that there are two more random numbers on the block head of each FileStorm subchain. These two random numbers are used for file validation. Prove that every node has saved the file. On the FileStorm subchain, nodes are divided into two kinds: outgoing block nodes and storage nodes. The outgoing node is responsible for packaging transactions, outgoing blocks, and generating file validation random numbers. Storage nodes store files and validate them.
       Outgoing node is divided into different groups, each group is a basic unit of storage, equivalent to a Shard in the database. The storage space of nodes in each fragment is as large as that of files stored. Multiple nodes in such a fragment can verify each other. All file information and read-write transactions are written on the block chain, while the file content exists in the IPFS of the storage node.
       Each storage node periodically verifies the local files. Initially set to 40 blocks. The block in turn for validation generates a set of files based on two random numbers, and then uses the first random number to find a starting position in each file. A random set of strings is obtained by counting 256 bytes from this starting position. The string is then hashed until a root hash value is obtained. At the same time, the same operation should be done with other nodes in the slice. Get the hash value. The verified node first sends its hash value to the chain in the form of transaction. After receiving the transaction with other fragmented nodes, the comparison is made with the root hash generated by themselves, and the comparison results are sent out in the form of transaction. Finally, statistics are made, if more than half of the nodes give the same hash value as the verified nodes. We think that if the verified node has all the files in it, we will reward it.
       Each storage node is validated in turn, and the validation is rewarded. File validation is performed in each fragment.
4. Download and installation of mining procedures