Upload
others
View
8
Download
0
Embed Size (px)
Citation preview
THE FILENET SUPERNODE PLAN
The Filenet supernode plan
Until this point, Filenet is in a period that can be called an equity flow era. In the era of
Filenet equity transfer, we have completed the blockchain transfer function, enabling
the transfer of equity to Filenet supporters. At the same time, Filenet has completed the
reward function, absorbed some devices to provide storage and retrieval services, and
provided block packaging services as super nodes by utilizing the node resources
provided by the technical community for free. Meanwhile, the development of SDK and
DApp is also progressing smoothly.
The most difficult problem in the Filenet equity transfer era is the unstable computing
power of the network. Some nodes temporarily join the network to provide services
and choose to terminate services at any time. This leads to poor product experience
and hinders the development of SDK and DApp. Data can be restored when multiple
copies of the same data are backed up at the same time. When the number of backups
is small, some node exits or corruption can result in data loss, which is not acceptable in
the Filenet storage service. It is difficult to balance the efficiency and security of data
storage. We have to store a piece of data at a very high cost. Even so, there have been a
few cases of data loss as miners have pulled out.
Therefore, in the new consensus mechanism, more emphasis will be placed on the
stability of nodes, and some supernodes will be encouraged to provide stable and
reliable storage services. Unstable and dishonest nodes will reduce credit, and even be
considered invalid nodes. There are penalties for data loss.
And as the old equity flow era completes its historic mission, we will see a supernode
era for Filenet. We've been working on a technical solution for a long time, and on June
1 of this year, Filenet will be hard forked, with a new consensus mechanism supporting
supernodes, and a hard forked solution supported by the majority of geeks in the
technology community.
Filenet's original supernodes are very vulnerable, both because of the lack of focus on
equity issuance and circulation in the equity transfer era (it is difficult to vote when the
equity issuance is insufficient), and because of the lack of incentives for supernodes,
which makes many miners reluctant to use their own nodes to provide supernode
services. Under the new consensus mechanism, supernodes will be rewarded to provide
reliable services.
At the same time, Filenet will focus on ensuring that the reward is fair. Supernodes that
provide high-quality and efficient services receive high rewards, while supernodes that
provide ordinary services receive low rewards. The size of the award is no longer
dependent on the size of the equity stake, but on the quality of the service. The more
the supernodes give, the more they give back.
In the Filenet supernode era, a miner can choose to put up a deposit for a period of
time, and can also choose to put up a deposit at any time. But obviously, the person on
the margin is more creditworthy, because he's making a promise that he's going to do a
good job for a certain amount of time, or he's going to lose money or he's going to get
a penalty.
Another problem in the Filenet equity flow era is that nodes have different performance,
resulting in very different services being provided. In this way, when forming super
nodes to dig together, it will lead to the problem of uneven distribution of income. This
difference cannot be expressed simply in terms of parameters, and we have made a lot
of effort and improvements in fairness to address this problem, but not enough; Filenet
still has a disproportionate relationship between effort and return.
Many miners who support supernodes want us to set a standard that can make
everyone's nodes the same and the benefits the same. However, this is a task that
cannot be completed. We prefer to choose nodes freely, and we will ensure fairness
through certain algorithms. For machines that join the same supernode, it is acceptable
to select the same or close nodes. In addition, in the age of supernodes, we are able to
support bulk transfers more easily. This makes it easier to deploy and implement nodes
that support more supernodes and other nodes with large transfer requirements.
Introduction to super node entries
The campaign Filenet supernode will go through three phases, a pre-election
phase, a test phase, and a contract service phase. The pre-selection stage will
determine whether the candidate is qualified to join the super node campaign.
After the qualification is confirmed, we will publish the list of nodes entering the
test stage. In principle, the test stage should last for 30 days. During the testing
phase and the service contract phase, the margin required for the Fn wallet
address shall not be less than the amount required when the test nodal list is
published (non-mandatory lockup); The tested node will become a qualified
super node and will officially enter the service contract period of super node (the
contract period is 6/12 months).
Total supernode recruitment
There is a huge demand for supernodes, and Filenet supernodes will be recruited
in three phases, each in three batches. Recruitment of no less than 76 large
supernodes and more than 140 small and medium nodes (Filenet supernodes will
all be generated from preselected nodes) is completed in steps to meet the
real-time distributed storage requirements of the whole network.
Supernode preselection rules
The primary election of super nodes in the first phase will be divided into three
batches. If the first batch of pre-selected nodes is not successfully elected, it will
be automatically adjusted to the nodes participating in the second batch and the
third batch of pre-selected nodes (subject to the announcement). In principle, the
amount of reward and credit enhancement will be reduced.
Supernode campaign process
Submit pre-selection application -- qualification approval and confirmation -- test
stage -- service contract stage and award monthly
The first batch of supernodes in the first phase
The first batch of super nodes in the first phase (0:00 on April 19 -- 24:00 on April
23) will provide the maximum reward and improve the highest credit of the
nodes.
In order to ensure the optimization of node quality, in addition to the basic
requirement that the candidate nodes should actively support Filenet ecology,
the selected nodes will be selected mainly based on the comprehensive factors
such as the order of registration of the candidate nodes, the strength of the node
and the amount of currency held. Starting with the first batch of phase 2, it is
possible to set standards for node hardware.
The first batch of the first issue
Preselected node type margin Node reward
Three large supernodes ≥200000Fn ≥500 200000Fn for 3m
Five small supernodes ≥ 50000Fn ≥150 500000Fn for 3m
The second batch of the first issue
Preselected node type margin Node reward
Four large supernodes ≥200000Fn ≥500 200000Fn for 6m
Seven small supernodes ≥ 50000Fn ≥150 500000Fn for 6m
First and second supernode lockup and contract rules
Non-mandatory lockup: the first batch of election nodes in the first period,
during the test period (April 24 -- May 23)shall ensure that the margin for the
election Fn wallet address shall not be lower than the amount of margin when the
test list is published.
Supernode service contract: during the effective period of the selected service
contract A or B, it is required to ensure that the amount of margin in the selected
Fn wallet address is no less than the amount when the test list is published.
First batch of supernodes exit mechanism
First, you can exit at any time before the end of the test period.
Secondly, before the issuance of reward tokens in the service contract period, the
deposit in the Fn wallet address of the node or the number of nodes is lower than
the relevant requirements in the published test list shall be deemed as an
automatic withdrawal: no reward tokens shall be issued.
Finally, after the issuance of reward tokens in the service contract period, the
deposit in the Fn wallet address of the node or the number of nodes lower than
the relevant requirements in the published test list shall be deemed as an
automatic exit: the credit value of the service address shall be cleared to zero.
First batch of supernodes (pre-selected) audit list:
The first batch of supernodes to be adjusted into the second batch of
supernodes in the first batch:
For queries, contact the official email address of the Filenet supernode: