Closed thomaseizinger closed 3 years ago
According to https://github.com/libp2p/specs/pull/334#issuecomment-865171882, we don't actually want PoW in the protocol.
I'll leave this ticket open to track that the spec needs to be changed to clarify that, in particular I think we should:
Any deterministic/verifiable randomness sounds application specific, but that's fine given the applications being build on libp2p. I only gave examples with a radomness beacon, but anyone without one could consider H("app" ++ date ++ dest_pk) if dest_pk stays hidden from the network, or somehow VRF.Sign(sk, "app" ++ date) and VRF.Verify(pk, "app" ++ date) if pk is public.
Originally raised by @burdges in https://github.com/libp2p/rust-libp2p/pull/2107#issuecomment-864468604.