New RFC: 42/LOGOS-REPUTATION-INKINGUT

[easye]

Problem

Within the Logos Consensus model (c.f. #509), a "pluggable" behavior for node reputation may be specified. Such a "Reputation RFC" needs to be abstracted, reviewed, and written.

Acceptance criteria

This RFC will be reviewed by the appropriate peers as a series of pull requests.

Details

Although presumably the "Logos Consensus Model" (#509) will provide some framing context, this RFC would set up the necessary motivation for the initial version of the Inkingut node reputation algorithim, describe that algorithim, present a security model of potential adversaries, fill-in known attacks, and perhaps provide a reference implementation.

Inkingut is expected to evolve, so specifying a minimal protocol/implementation API, and a mechanism for its subsequent revision would perhaps be a good scope.

Possible Solutions

Write an RFC; get feedback on pull requests.

Notes

Currently getting #509 into a RAW state has priority, but developing a table of contents, and initial sections should be possible for reputation in the near term: it always helps to be working on a couple things.

As with #509, there is a sizable amount of markup in the notion.so system that can be used as a starting point.

[jimstir]

Closing as this seems to be complete. Pull request here