DRAFT PROPOSAL
Below is an example of a proposal we (the DFINITY R&D team) intend to submit to the NNS in a few days/weeks, depending on community feedback as well as questions and answers. We want to hear what you all think, including any wording changes we need to make
Summary
TLDR: As part of the work to further decentralize the infrastructure layer, we want to submit a new motion proposal to introduce a new type of hardware spec (and its corresponding remuneration) for nodes on the IC. We would like to get community feedback on this before proposing.
1. State of the world
Nodes are remunerated based on their location and node type. The Node Rewards table shows the rates per location and node type.
The current types are are listed here:
https://wiki.internetcomputer.org/wiki/Node_provider_hardware
2. What we are proposing
If you vote ACCEPT, you are agreeing on two things:
- IC should Introduce a new node type. The new type has requirements independent of vendors (except for the CPU).
You can see the details for the new proposed type here:
- Dual Socket AMD EPYC 7313 Milan 16C/32T 3 Ghz, 32K/512K/128M
- optionally 7343, 7373, 73F3
- 16x 32GB RDIMM, 3200MT/s, Dual Rank
- 5 x 6.4TB NVMe Mixed Mode
- Dual Port 10G SFP or BASE-T
- TPM 2.0
- DFINITY foundation will determine the expected cost of the new node type based on data from several independent vendors and propose reward rates based on an expected node lifetime of 4 years. DFINITY R&D will research various ways to construct the vendor-generic node type and propose rates for this node type.
This is a governance proposal, so if this vote passes, there will be subsequent NNS proposals to introduce the new node type and reward rates to the NNS.
3. Why we are doing proposing this
This new node type is being introduced for two reasons:
a. The current node specifications are vendor-specific which is an unnecessary centralisation a year after launch. Vendor-specific specs also makes adding future nodes more difficult as it is harder to buy machines with older hardware specs.
b. The current node types do not support VM memory encryption and attestation which will be needed in future features.
4. What we are asking the community
- Read proposal
- Ask questions
- Give feedback