From c133021bee5e9bd6e4ca831f037eeea083dc2e96 Mon Sep 17 00:00:00 2001 From: Chase Fleming Date: Wed, 8 Nov 2023 09:24:57 -0800 Subject: [PATCH] Update docs/build/advanced-concepts/randomness.md Co-authored-by: Alexander Hentschel --- docs/build/advanced-concepts/randomness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/build/advanced-concepts/randomness.md b/docs/build/advanced-concepts/randomness.md index 1bfa51493f..73c3e1c5dc 100644 --- a/docs/build/advanced-concepts/randomness.md +++ b/docs/build/advanced-concepts/randomness.md @@ -87,7 +87,7 @@ Adding a safe pattern to reveal randomness without the possibility of conditiona On Flow, we have absorbed all security complexity into the platform. -[FLIP 123: On-chain Random beacon history for commit-reveal schemes](https://github.com/onflow/flips/blob/main/protocol/20230728-commit-reveal.md#flip-123-on-chain-random-beacon-history-for-commit-reveal-schemes) was introduced to provide a safe pattern to use randomness in transactions so that it's not possible to revert non-favorable randomized transaction results. +[FLIP 123: On-chain Random beacon history for commit-reveal schemes](https://github.com/onflow/flips/blob/main/protocol/20230728-commit-reveal.md#flip-123-on-chain-random-beacon-history-for-commit-reveal-schemes) was introduced to provide a safe pattern to use randomness in transactions so that it's not possible to revert unfavorable randomized transaction results. We recommend this approach as a best-practice example for implementing a commit-reveal-recover scheme in Cadence. The `RandomBeaconHistory` contract provides a convenient archive, where for each past block height (starting Nov 2023) the respective “source of randomness” can be retrieved. The `RandomBeaconHistory` contract is automatically executed by the system at each block to store the next source of randomness value.