Incentivised Data Node Spec

davidsiska-vega commented 3 years ago

In the WIP pull request: https://github.com/vegaprotocol/specs-internal/pull/684

@Vegaklaus statistical oddities of hash functions: fill in parameter inputs, decide what are network parameters, give calculation for the expected distance from start block
@Vegaklaus please check what are the other network parameters arising
@vegaprotocol/core Please read and flag any questions you have.

gordsport commented 2 years ago

@davidsiska-vega @Vegaklaus - during the x-functional meeting we discussed the need for data-nodes to have an SSL cert for GraphQL use.

The ticket: https://github.com/vegaprotocol/data-node/issues/295 will not be implemented in the core software, however, could this be taken into consideration as a possible incentive to encourage people running data-nodes to use SSL certs

davidsiska-vega commented 2 years ago

So far the spec covers only:

how to prove that data node has all the data "with high probability".

What we still need:

catch up without replaying chain (postulate we need this, claim it's engineering problem, Bittorent data from other nodes / postgres replication )
how to handle data nodes that observe advertised retention rules; prove that the data is available within the advertised retention rules. This might need a specific subset of "valid retention rules for incentivised data node".
how to "price" queries so that there can be a "free" version or free queries and then "paid-for" version where you pay gas for access.

vegaprotocol / specs

Incentivised Data Node Spec #685