search

AlacrisIO / meta

Internal management of Legicash/Legilogic/Alacris
0 stars 0 forks source link

Allow Alacrity to deal with large times #129

Open fare opened 5 years ago

fare commented 5 years ago

For Alacrity to be able to deal with large evaluation times, it needs to accept one or many of the following backends:

  1. TrueBit-style claims of result of the computation, with interactive dichotomy to challenge the claim.
  2. Claim of the result of the computation, while posting the trace to the MKB (or directly to a consensus), and accepting a direct challenge as to any misstep.
  3. Intermediate strategy with claim where the trace is only posted upon challenge (and possible reduction of the space via a few steps of dichotomy / decaexatomy)
  4. Same as the above, but with some or all interactive steps replaced by non-interactive proofs with zkSNARKs.
fare commented 5 years ago

Note that #129 takes priority over #128, because there is no space left to compress if time wasn't compressed first.

fare commented 5 years ago

(Although the time compression inherent in using State Channels for interaction-heavy computations might be sufficient to justify compressing space, without needing compression of interaction-less computations)