SIMD-0326: Proposal for the New Alpenglow Consensus Protocol

Sure, I understand all this. I don’t know how to enforce this magical “best behavior” though. At the very least I don’t know how to enforce it without serious side effects.

I would like to give you an idea what we are already planning: With Alpenglow we ship a new way to collect metrics. As part of this, all validators will tell us how quickly all validators vote (everybody reports on everybody once per epoch). This data could serve as a basis for a “much more accurate TVC”. We could simply take the median (to make it simple) report and directly pay according to that. This is not only what you want (silly TVC), but so much better than what you want. It’s like TVC on steroids.

However, this “better TVC” solution has obvious issues:

  1. You can earn more by not telling the truth.
  2. You can improve by moving to a geographically more central location.

Problem 2 we cannot really solve with this approach, it’s inherent with anything TVC. It’s even a tradeoff: The better you make TVC, the more of a centralization problem you have.

Problem 1 we can also not solve, at least not without what we would call “crypto delirium” (i.e., 100x overhead just to do the accounting in a more secure way, and it’s still 99% insecure). Both 1 and 2 are serious problems. No TVC is better than “good TVC” that has serious side effects.

Look, I understand the sentiment: Why do these “stubborn researchers” not just do TVC?!? The truth is, we thought long and hard about these things, and at the beginning of this long thinking process TVC sounds like a reasonable (even obvious!) idea. But if you think it to the end, “no TVC” actually trumps “TVC” (mainly because of the two reasons above). I know that this is difficult to understand, and I could tell you much much more about this stuff.

I hope this helps you understand why we are not just stubborn. We actually thought about this a lot…

1 Like

Here you talk about the “how” :slight_smile:

I don’t want TVC. I wish we could assess the work of a validator much better than TVC. For instance TVC rewards voting like the mob. Today when there is a choice between 2 forks, often the rooted fork is the failing one (empty block, too long block…). A validator voting for the alternate fork is penalized while it should be rewarded.

I don’t really understand your issue 1, but I can perfectly understand than there is no feasible way to do this assessment fairly, without side effects like centralization, or without opening the door to many abuses. If there is no feasible way, let’s stick with the minimal service.

1 Like

True :smiley:

Voting on this proposal is now live, follow the instructions here to claim and cast vote tokens: solgov-distributor/votes/simd0326 at master · laine-sa/solgov-distributor · GitHub

3 Likes

Are VATs purchased automatically by the validator?

If not, can VATs be purchased in bulk (e.g. annually) or will operators have to build automation to purchase one VAT every epoch?

1 Like

Hi Colton, maybe have a quick look at the VAT SIMD?

That should answer your question.

Best,

Roger