Look into using Helios library to have trustless .eth resolving system #56
Description
Problem
Currently plebbit-js believes whatever ETH RPCs tells it who owns a domain and its record values. There's no way to validate against RPC tampering with blockchain states in responses.
An RPC provider like Infura could potentially censor subs, although their effect will be limited because plebbit-js uses many different RPCs, and it's probably unlikely all of them will censor the same .eth.
This not only affects .eth, in the future if we implement .pleb on an EVM chain, we would have the same problem.
Priority
Low for now, would probably be a while before we have ETH RPCs censoring subs, but it's something to think about and document.
Solution:
Using Helios, plebbit-js clients would notice any censoring or manipulation immediately which would give users time to switch RPCs.
seems mature as of now.
It needs to run its own server to have trust-less requests, so I suppose we can either embed it within plebbit-js node files, or we could have it as part of plebbit-cli