What’s a good way to access randomness on @base if I don’t want to use chainlink? Is it bad do use RANDAO considering there are any block builders other than Base themselves?

Posting here just in case anyone knows of good in chain randomness solutions?

Interesting. I guess it means that you are letting Coinbase provide the PRNG seed? In Bitframes I mix RANDAO with my own key that commit to earlier but only reveal after random execution. Maybe a system like that is possible?

Engineer @ Syndicate, prev: Rainbow, Foundation & Cloudflare /poetic-web, builds caststorage.com

Interesting. I guess it means that you are letting Coinbase provide the PRNG seed? In Bitframes I mix RANDAO with my own key that commit to earlier but only reveal after random execution. Maybe a system like that is possible?  

https://github.com/mattdesl/bitframes-randao

I wonder if you could use L1 RANDAO somehow, like with an oracle of sorts. It should be possible to automate—you could regularly post messages with the next raffle’s SHA commitment, and previous raffle’s revealed key.

It turns out that L2’s (or maybe just Base) doesn’t have a RANDAO value (I think it’s a constant). So would have to go with a VRF value I think. I ideally need it within a function call. But maybe I could use your method in an offchain way and send it to the function in my contract.

Do you know if your randao would be able to have the system setup procedurally or is there a certain amount of planning for each raffle