Welcome to Nebulas Weekly Report #57, delivering the latest updates on the Nebulas project. This report is maintained by the Nebulas team. Please send feedback to contact@nebulas.io, or tweet us @nebulasio.

Notes: To facilitate community members, Nebulas team has adjusted the weekly report, breaking it into community dynamics and development updates. The two parts will be alternately released on a weekly basis.

Nebulas Technical Committee (NTC) Meeting Minutes (2018.11.21)

The Nebulas Technical Committee (NTC) has decided to disclose the meeting minutes pertaining to the development of Nebulas NOVA in order to improve the transparency and openness of Nebulas. We welcome the community to explore the the meeting minutes via the Nebulas Wiki and to communicate with us via our mailing list.

Summary：

1. The process to submit IR (LLVM Intermediate Representation) and who can submit IR (LLVM Intermediate Representation). 2. The time window for NR & DIP. 3. How much NAS for DIP & how to distribute NAS for DIP.

Detailed minutes：

The process to submit IR and who can submit IR

(1) Nebulas Nova will use an auth_table to decide whose IR can be executed and the lifetime of each IR.

(2) auth_table is a set of tuples, and each tuple includes IR name, submitter’s address, the valid start and end height for the submitter.

(3) Only the auth_admin’s auth_table can update in Nebulas Nova. The auth_admin account should be created by a cold wallet. Each IR should be managed by different accounts. The Nebulas Technical Committee will further discuss the community governance details with the community. Before we finalized the governance details, the Nebulas team will not recklessly open the IR submission access. The NBRE only executes several predefined IRs, like checking the auth_table, and the IRs defined in auth_table. Other IRs will not be executed

(4) However, each node may change the code. And that could be the auth_admin account, and the auth_table. Consequently, it may change the behaviors in NBRE, and the node shall fail to sync data with the main-net.

2. The time window for NR &DIP

(1) In the yellow paper introducing Nebulas Rank, we mentioned that to avoid the affect of loop attack, we will remove the forwarding loop before we calculate the In-and-Out degree for the transaction graph, thus the time-window is important for anti-manipulation.

(2)If the time-window is too short, there may be more cheating.

(3)For now, we suggest the time window in several days.

(4)We should monitor the cheating status, and adjust the time-window if necessary.

(5)Time window for DIP should be much more larger than the time window of NR, for now, we suggests 7 days

3. How much NAS for DIP & how to distribute NAS for DIP

(1)For each month, we suggest around 500 NAS in total, the winners shall be relatively stable, so a winner will get reward in several months.

(2)We will have a special account for distributing NAS for DIP. The account can only send special transactions for DIP.