HIPxx: Validator Node Security Implementation(s)#211
HIPxx: Validator Node Security Implementation(s)#211jamiew merged 15 commits intohelium:masterfrom Bx64:master
Conversation
|
I see another HIP with number 32 was just filed, in case you need the number of this PR updated to HIP33, please let me know. |
|
@Bx64 thank you for the thoughtful and well-formatted submission. I just marked it as "HIPxx" until I can give it a full review and merge later today |
Excellent, and no problem. Let me know if you need any further information from me. |
|
@Bx64 any interest in presenting this and fielding any questions for 5-15 mins on the community call tomorrow? More info: https://dewi.org/community-call or feel free to hit me up on Discord |
@jamiew is it possible to put us in at 4.15 UTC? We have conflicting schedules so can't really do anything else. We can join in for a few minutes then. |
|
Sure, would be happy to -- that's 4:15 UTC right?
…On Tue, Jun 29, 2021 at 3:12 PM Bx64 ***@***.***> wrote:
@Bx64 <https://github.com/Bx64> any interest in presenting this and
fielding any questions for 5-15 mins on the community call tomorrow? More
info: https://dewi.org/community-call or feel free to hit me up on
Discord jamiedubs#1105
@jamiew <https://github.com/jamiew> is it possible to put us in at 4.15?
We have conflicting schedules so can't really do anything else. We can join
in for a few minutes then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#211 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAO34NCDCA2ZYDBHNJMVLTVILKPANCNFSM4647P7PQ>
.
|
|
Yeah, sorry - 4.15 UTC or 15 minutes after the call starts :) |
As validators will take over all activities regarding consensus on the Helium network, the pool of actors in charge of validating transactions and creating blocks is significantly reduced from the current situation (46K+ hotspots and growing fast) to a small pool of (expected) several hundreds of nodes, which significantly decreases the targets that need to be interfered with in order to impact consensus in one's own favor. Having these nodes IPs (and with that, location and hosting provider information) be publicly visible, traceable and targetable on the Helium network therefore poses a significantly increased security risk compared to the current situation. If the validator nodes are compromised, so is the progress of the chain meaning the chain could completely (and perhaps unrecoverably) stall.
Ed: rendered view = https://github.com/Bx64/HIP/blob/master/0032-validator-node-security-implementation.md