That’s included in the Alpha network code, though I can’t be sure it’ll do what I’m thinking it will (constrain the demand each node puts on the network to keep load on the network low).
From some kind of initial distribution, plus ongoing proof of stake based distribution, similar to any proof-of-stake crypto. (the proof of stake mechanism would need to be developed).
Nobody would have any ability to upload anything to the network other than account details. Wallet providers would have pre-assigned space and the keys to it so they can update. There will be no general data uploading on this network, and anything that uses resources (transactions, updates) will require a fee, so won’t be spammed.
Was the open test network spammed only by accounts, or by data that those accounts uploaded? If it’s just accounts, then yes, mechanisms would be needed to prevent abuse that affects the network stability. Rate limiting may be one of these.
May be right, hence I’m looking for opinions on what would be required and how difficult it would be, so thanks for your contributions to this discussion.
This would be a decentralised network, so not comparable to a centralised server.
Why would you the network need to whitelist vaults and clients if they can’t spam the network due to inability to create a large load on the network, plus fees for anything that uses network resources?
You don’t need to discriminate anything - just charge for everything and it won’t be spammed unless someone wants to somehow acquire an awful lot of a scarce asset (needed to pay for all transactions) to create the spam… but then it’s just paying nodes for their service.
There certainly would be a lot to think through. Whether significantly easier solutions for each problem are possible with a smaller, more restricted, and slower network is the key question here.
)