25+ yrs in software, from architect to director. Expert in algorithms, networking, distributed systems. Driving innovation, delivering scalable solutions.
@0xPrimata Great question. The intent was to implement it as part of the proposer VM, wrapping the underlying VM. From the inner VM perspective, it would be seen as it would get a random seed per block height ( similar to the block height, which is already being passed in ).
Currently, Implementing verifiable randomness on Avalanche would require the usage of external oracles, which adds complexity and cost. ACP-113 offers an alternative by leveraging a chain of BLS signatures to generate verifiable random seeds within the Avalanche platform itself.
While theoretically possible, this attack is considered to have a negligible practical impact.
despite this known vector of attack, would you use the VM randomness generated via ACP-113 in an on-chain implementation?
Adding verifiable random value generation as a native function of AvalancheGo will unlock so many new dApp features, game functionality, and much more on Avalanche. @TsachiHerman leads us Thursday for an in-depth discussion:
Excited to announce that I've joined Ava Labs, the creator of the Avalanche network. Working with the Ava Labs amazing team, I have been focusing on adding support for long-desired features like virtual machine randomness support and (even better) proposer VM.