Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

[Consensus] Random Seed sampling #24

Closed
2 of 4 tasks
sternhenri opened this issue Nov 24, 2018 · 1 comment
Closed
2 of 4 tasks

[Consensus] Random Seed sampling #24

sternhenri opened this issue Nov 24, 2018 · 1 comment
Assignees
Labels
EC help wanted External collaboration required or helpful key-todo launch-critical Required for launch P0 Highest priority

Comments

@sternhenri
Copy link
Contributor

Currently evaluated strategies:

  • (current) VRF+VDF(Post) against current min ticket from parent set
  • Sample from k blocks back (constant lookback)
  • Sample from k blocks back but variable lookback: use seed for n block epoch

Strategy

Short term

Mid/long-term

  • Involve outside researchers (could be Snow White authors (Rafael Pass, Phil Daian)) about this

Other notes:


Why do we need randomness?

  • Elect leaders
  • Seed for the proof of spacetime (this is where we get PoSt challenges from!)
    • Taking the seed from chain ensures that a VDF speedup won't compromise security since the network still has to wait for the "re-seeding" from chain
    • Can we avoid taking challenges from chain for PoSt? Technically yes (MPC? All absed on VDF?), practically, it's difficult.

Decision tree (so far):

  • Can we use the chain as a Randomness Beacon?
    • if yes:
      • Construction 1: just use the ticket chain (like algorand!)
    • if not:
      • Run MPC at every round:
        • Construction 2: Run a slow MPC -> VDF+RANDAO (similar to justice)
        • Construction 3: Run a fast MPC -> Deterministic Threshold Signatures (like DFinity) at every round (also useful for SSLE)
      • Current leader runs VDF:
        • Construction 4: leader submits a ticket, miners run VDF for T blocks to find their secret leader election seed

More in this presentation on randomness

@mhammersley mhammersley assigned sternhenri and unassigned ZenGround0 Jan 17, 2019
@sternhenri sternhenri transferred this issue from another repository Jan 19, 2019
@sternhenri sternhenri transferred this issue from filecoin-project/research Jan 22, 2019
@sternhenri sternhenri added launch-critical Required for launch P0 Highest priority EC labels Jan 22, 2019
@mhammersley mhammersley added help wanted External collaboration required or helpful key-todo labels Jan 25, 2019
@sternhenri
Copy link
Contributor Author

@whyrusleeping @nicola @ZenGround0 How are we feeling about this one? Is it still a major area of open questions, I must admit I feel like I've answered a lot of my own questions here.

I also think we can close filecoin-project/research#98.

Major Qs for me come from filecoin-project/research#34, which I take to be blocked on @nicola (for lack of context on my part)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
EC help wanted External collaboration required or helpful key-todo launch-critical Required for launch P0 Highest priority
Projects
None yet
Development

No branches or pull requests

3 participants