Outstanding questions related to PoET, PoST, POPS-VRF

[lane]

1. DoS mitigation/How exactly should POPS-VRF be implemented?

   • see POPS-VRF · Issue #168 · spacemeshos/pm · GitHub

   • see https://community.spacemesh.io/t/tortoise-beacon-based-on-bad-vrf/100

   • see https://community.spacemesh.io/t/possible-dos-against-pops-vrf-beacon-and-mitigation/210

   • what’s the difference between POPS-VRF (finding a nonce on poet output) and finding a nonce on post data?

   • historically, there were two requirements from research

     1. find a nonce on poet output
     2. find a nonce on the post data

   • aviv created SMIP, GPU-POST lib got updated, then Tal said we don’t need it

   • see SMIP-0011: GPU-POST LIB - PHASE II · Issue #45 · spacemeshos/SMIPS · GitHub

   • Tal reply on slack here: SMIP-0011: GPU-POST LIB - PHASE II · Issue #45 · spacemeshos/SMIPS · GitHub

   • if we implemented it and not needed we need to clarify why

   • Does current implementation in GPU PoST lib satisfy requirements? If not, why not? What still needs to be done here?

2. How exactly does PoST data commit to genesis ID?

   • see POPS-VRF · Issue #168 · spacemeshos/pm · GitHub
   • see activation: bind post data to genesis id · Issue #3507 · spacemeshos/go-spacemesh · GitHub

3. Do we want to add additional verification in PoET to ensure that each miner only submits once per round per PoET server?

   • see poet: allow one submission of PoST per miner per round per poet service · Issue #3458 · spacemeshos/go-spacemesh · GitHub