From ce934a547ea6b9b088984dcda03dd03a67ddb32a Mon Sep 17 00:00:00 2001 From: Stephen Akridge Date: Mon, 22 Oct 2018 15:56:00 -0700 Subject: [PATCH] Storage RFC validator incentive clarification --- rfcs/rfc-003-storage.md | 1 + 1 file changed, 1 insertion(+) diff --git a/rfcs/rfc-003-storage.md b/rfcs/rfc-003-storage.md index 4c94548849..0376997ffc 100644 --- a/rfcs/rfc-003-storage.md +++ b/rfcs/rfc-003-storage.md @@ -52,3 +52,4 @@ Our solution to this is to force the clients to continue using the same identity * Replicator clients fish for lazy validators by submitting fake proofs that they can prove are fake. * Replication identities are just symmetric encryption keys, the number of them on the network is our storage replication target. Many more client identities can exist than replicator identities, so unlimited number of clients can provide proofs of the same replicator identity. * To defend against Sybil client identities that try to store the same block we force the clients to store for multiple rounds before receiving a reward. +* Validators should also get rewarded for validating submitted storage proofs as incentive for storing the ledger. They can only validate proofs if they are storing that slice of the ledger.