AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-10 07:47:59 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #265 from libp2p/update/gossipsub-v1.1-extended-validators

Browse Source 
extended validators for gossipsub v1.1
This commit is contained in:
vyzo
2020-05-04 10:53:00 +03:00
committed by GitHub
parent bc295e2a14 8e2693c2fb
commit e64f1e31d2
1 changed files with 16 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
pubsub/gossipsub/gossipsub-v1.1.md
View File

@@ -2,7 +2,7 @@
| Lifecycle Stage | Maturity | Status | Latest Revision |
|-----------------|----------------|--------|-----------------|
| 1A | Draft | Active | r2, 2020-04-11 |
| 1A | Draft | Active | r3, 2020-04-28 |
Authors: [@vyzo]
@@ -45,6 +45,7 @@ See the [lifecycle document][lifecycle-spec] for context about maturity level an
- [P₄: Invalid Messages](#p%E2%82%84-invalid-messages)
- [Parameter Decay](#parameter-decay)
- [Guidelines for Tuning the Scoring Function](#guidelines-for-tuning-the-scoring-function)
- [Extended Validators](#extended-validators)
- [Overview of New Parameters](#overview-of-new-parameters)
- [Spam Protection Measures](#spam-protection-measures)
@@ -470,6 +471,20 @@ if invalidMessageDeliveries < DecayToZero {
`TBD`: We are currently developing multiple types of simulations that will inform us on how to best recommend tunning the Scoring function. We will update this section once that work is complete
#### Extended Validators
The pubsub subsystem incorporates application-specific message validators so that the application can
signal invalid message delivery, and trigger the P₄ penalty.
However, it is possible to have circumstances where a message should not be delivered to the application
or forwarded to the network, but without triggering the P₄ penalty.
A known use-case where this need exists is in the case of duplicate beacon messages or while an application is syncing its blockchain, in which case it would be unable to ascertain the validity of new messages.
In order to address this situation, all gossipsub v1.1 implementations _must_ support extended validators with an enumerated decision interface.
The outcome of extended validation can be at a minimum one of three things:
- Accept message; in this case the message is considered valid, and it should be delivered and forwarded to the network.
- Reject message; in this case the message is considered invalid, and it should be rejected and trigger the P₄ penalty.
- Ignore message; in this case the message is neither delivered nor forwarded to the network, but the router does not trigger the P₄ penalty.
### Overview of New Parameters
The extensions that make up gossipsub v1.1 introduce several new application configurable