Conference No. NIP-EN-20200527
Meeting time: May 28, 2020 2:00pm - 3:40pm Beijing time
Participants:
9 members, including Dustin (Natoshi Node), Shestovsk (StackOfStack), Leec (NAX.one), Mark (NASAU);Members of the Nebula Foundation: Becky, Iris, Larry and others participated in the speech, and attended: Ben, Lin Weimin ( CVDIP237)
Background:
The second PoD governance cycle on the main website began around 8:13 p.m. on May 29 (Beijing time).It is expected that 43 nodes will vote on more than 20 proposals.To view the proposals, please visit https://node.nebulas.io/govern. Before the voting begins, we invited the English community members with node related proposal, node operators, team members and so on to communicate and discuss.
Discussion Brief:
1. Notification on the Adjustment Progress of PoD Punishment Mechanism
The project NP289 was approved by the last PoD governance vote. Larry stated that it has completed development and is currently testing and it will be launched next month. After going online, the node penalty will have a period for a node to resume successful participation of being a consensus node, funds will not be frozen. If the node still cannot generate blocks after approximately 5 days (200 polling cycles), NAS will be frozen..
2. Node-related proposal discussion
A. About 51 candidate node selection:
NIP302 - Modification to the Stability Index for Nebulas Nodes v2 by Dustin
The maximum Si of the original new node is currently 0.8. Only once a block has been successfully generated, the Si of the node increases. Dustin believes that the new node’s Si should be slowly increased from 0.8 to 1 by directly monitoring the status of the node server and there is no need to wait for the node to generate a block to have a Si increase. The revised proposal recommends that the initial Si of all new nodes be set to “1” and if the node fails to perform, be subject to existing Si rules. As a result this will reduce the voting pressure of NAX. In addition the amount of modification to the smart contract is relatively small, and just requires a parameter adjustment.
B. About consensus node selection:
The following two scenarios are about how to select 21 consensus nodes out of 51 candidate nodes.The goal is to allow more nodes to participate in the block.
NIP305 - Modification to the NAX average calculation for Node selection V2 by Dustin
NIP305 is a relatively long-acting mechanism that reduces the gap between the nodes with a high amount of NAX staked vs nodes with less NAS staked via adjusting the selection algorithm (via removing of outliers from the calculation).The disadvantage is that it requires more development and sufficient testing time. It is not clear whether reducing the difference will reduce the NAX voting enthusiasm.
NIP355 - Add Lucky Node by Leec
The NIP355 has a small amount of change, which can be implemented via a parameter adjustment. After selecting 20 consensus nodes, the 21st consensus node will be selected completely by random. Since The probability of the top nodes being selected is relatively high, the 21st node will have a large probability to come from the lower ranked node list - even the nodes ranked 40-51. This will help lower ranked nodes participate in consensus.
C. About PoD voting:
NIP293-Node Governance: Remove “abstain” from calculations by CrisBRM
Removes the abstain from the calculation ratio. With this revised calculation system, more proposals are likely to be approved by meeting the minimum approval rating. The proposal was discussed and supported by multiple members of the community however, there are differences of opinions with this proposal. Because the total number of governance nodes is limited, up to 51, and about 43 in the second phase, which can be passed with the support of 29 nodes. In the case of fewer participants, the requirement of having ⅔ of all governance nodes supporting a proposal may be a more secure choice.
In addition, it is recommended to increase pre-communication, so that the initiator of the proposal should try to describe the proposal clearly and break down the value accurately. Many of the nodes that abstained in the first round were not necessarily due to the idea of the proposal but rather expressed doubts about the implementation and it could not be judged, or believed that the urgency was not high and did not necessarily need to be implemented immediately.
3. Free discussion of current issues
There are several common problems:
A. Low node participation rate
Everyone wants to increase the number of nodes. However, there are only 21 nodes stuck in the total block, and the total revenue amount is static. As a result, it’s harder to have hundreds of nodes. Increasing the number of independent nodes is a common desire, but from the first month of operation, the nodes built by independent teams/community organizations are ranked higher. Nodes that may be introduced into the community will have a better chance of success. At the same time, some nodes let the community users who participate in the voting to make decisions on the governance of the proposal, and the node operators to make the decision.This is also being explored.
B. Lack of NAX Application Scenarios and Future Development
Mark proposed that NAX’s current killer application scenario is lacking, and the current scenario is relatively simple. Iris says the Nebulas is currently organizing the NAX/dStaking - PoD - Go.nebulas entire governance cycle system, hoping to develop a better DAO as a service/tool to the Nebulas community and even other communities. While promoting DAO, community members are also welcome to make new proposals, share ideas. Nebulas is still pursuing gaming - for example NP293 - “Gaming on Nebulas” - Godot Engine Integration has been recently established as a project and we welcome community members to claim the development.
