Let's start with what I mean by cryptographic random beacon (RB).
A RB is a protocol among some parties who generate a random value all together such that:
- these parties do not trust each other
- the result is publicly verifiable (anyone can verify the result is correctly generated by the protocol)
- The output is unbiasable: No party can make a bias in the result.
- the result is unpredictable: no body can predict the next output from the current output.
The first intuitive solution is commit-and-reveal, which does not work!
everyone chooses a secret random value $s_i$ and commit to it, then in the second round they reveal their secrets.
The output is random, unpredictable and publicly verifiable, but not unbiasable.
The malicious party can simply wait until every body reveals its secret, then she decides if this is good for her to reveal or not and she may withdraw from revealing its secret.
Then there are several solutions based on random delay function or threshold cryptography (for me the most understandable one is the one based on the threshold BSL signature, from Dfinity company).
Now where in cryptography this can be used? why Random Oracle (+ Fiat-Shamir) is not enough?
I understand that this can be useful in the applications where the challenge should be unknown in special time-stamps.
For example if a data storage want to prove that at the time-stamp $t$ it still has the data, it should use a challenge generated by RB at time-stamp $t$ and give a proof based on this challenge. Otherwise, it can generate the challenge by herself (by RO e.g.), remove the data and at time-stamp $t$ claims that it has the data because it can generate the proof based on the data and the challenge.
But If there is no time-stamp, I really do not see any point to use RB instead of RO. I think for non time-stamp applications RO is more practical.
So, is my understanding correct? I still see some papers which are using the output of RB as the challenge (or just for random generation) rather than using RO (while there is no concept of time), and I don't know why!