After the Merge, the header of every block contains a field called prevrandao, a random number generated by the beacon chain that is used by the proof-of-stake to randomly elect block proposers in the beginning of every epoch.
Applications can use this number as a source of randomness if they don't intend to handle large sums of assets. For large TVLs, we do not recommend using block.prevrandao. See EIP-4399 for technical details, and security tips for application developers.
✔️ Solution
We can add prevrandao to every input as metadata.
This would be reflected in the current architecture as an extra parameter in the EvmInspect function.
In Solidity, we'll call it prevRandao so that application developers can quickly find resources based on the real name.
📚 Context
After the Merge, the header of every block contains a field called
prevrandao
, a random number generated by the beacon chain that is used by the proof-of-stake to randomly elect block proposers in the beginning of every epoch.Applications can use this number as a source of randomness if they don't intend to handle large sums of assets. For large TVLs, we do not recommend using
block.prevrandao
. See EIP-4399 for technical details, and security tips for application developers.✔️ Solution
We can add
prevrandao
to every input as metadata. This would be reflected in the current architecture as an extra parameter in theEvmInspect
function. In Solidity, we'll call itprevRandao
so that application developers can quickly find resources based on the real name.