Exploring Network Topologies: Flexnodes & Slashing — Transcript

Full transcript

1. 0:05All right. So, here we are. We have our
2. 0:10mom system and the mother of all systems
3. 0:13with our flex nodes. And our flex nodes
4. 0:15are happily getting rewards for
5. 0:18different validators, block builders,
6. 0:21wherever they may be, different nodes
7. 0:22that are getting better rewards. And
8. 0:25everybody's happy. everybody's rewarding
9. 0:27each other and getting better rewards.
10. 0:30Now, one of the concerns if you're in
11. 0:32web three right now running a node is
12. 0:35that you need to have really good
13. 0:37uptime. The reason you need to have
14. 0:39really good uptime is because otherwise
15. 0:41you will get slashed. You said you would
16. 0:43give some service, you didn't give it
17. 0:45and you keep doing that, eventually it
18. 0:48gets slashed and you lose whatever you
19. 0:51have stayed. The plan for us is not to
20. 0:54have slashing. And how is it that we can
21. 0:57get away with that? Well, remember here
22. 1:00that this node over here, this uh
23. 1:02receiver tree, say a validator was, you
24. 1:06know, sharing the rewards that they were
25. 1:08getting with these different flex nodes.
26. 1:09Flex one, flex node two, flex node
27. 1:11three. Now suppose uh that one of these
28. 1:14flex nodes, which might be say my
29. 1:16computer goes away, right? I close my
30. 1:19computer. I have to go somewhere. I have
31. 1:21to take my computer with me. It's not
32. 1:23going to be obviously while I'm not
33. 1:27helping anyone. I'm not going to get
34. 1:29rewarded. I'm not going to get paid for
35. 1:31work I don't do. However, am I going to
36. 1:35get beyond not getting paid? Am I going
37. 1:37to get in any way punished? You know,
38. 1:40which is kind of what slashing is.
39. 1:41Basically what will happen is you know
40. 1:43suppose that this node over here just
41. 1:48went away for whatever reason. This node
42. 1:51is still relying on other nodes. If
43. 1:52anything you know it may have to share
44. 1:55its rewards with just fewer nodes as
45. 1:58fewer nodes to to go around. That's
46. 2:00okay. Maybe the rewards will be a little
47. 2:02lower because it doesn't get as much
48. 2:04service, but it's still worth it for
49. 2:06this node uh to get to share the rewards
50. 2:10and get those extra rewards that come
51. 2:12from coding rather than having say a
52. 2:14single path like we looked at before.
53. 2:16Still better off that being on the red
54. 2:18or on the green. So basically what will
55. 2:21happen in this case is this node goes
56. 2:24away and automatically
57. 2:26the entire system is still entirely
58. 2:28robust. It's like that node wasn't
59. 2:30there. On the other hand, if a new node
60. 2:33comes on, say, you know, this node now
61. 2:36gets in and now decides to, you know,
62. 2:38also get get in the game and also be a
63. 2:41flex node, that's okay. That's great,
64. 2:43you know, and then this node can recode
65. 2:45and help out, etc. So basically nodes
66. 2:48can come and go and as long as a node
67. 2:50doesn't get entirely disconnected in
68. 2:53which case the only reason it would get
69. 2:54disconnected is actually not even the
70. 2:57pointto-point path. Therefore there was
71. 3:00no physical way in any way shape or form
72. 3:03of getting to it. As long as the node
73. 3:06doesn't get completely disconnected it's
74. 3:07okay. So this is why we're able to look
75. 3:10at flex nodes as part of the flexibility
76. 3:12in the flex nodes. A they're flexible
77. 3:14because they may send a few equations.
78. 3:17They may send a lot of equations, right?
79. 3:19Maybe this one's sending a lot, this
80. 3:20one's sending a few. But also, they can
81. 3:22come and go and nobody is having to
82. 3:25punish them in order to force them to
83. 3:27stay there. Uh so this is something
84. 3:29that's very uh exciting we believe about
85. 3:32flexits.