From 09d0462d2b964e3cc2c8b1ba8a4545f054343f19 Mon Sep 17 00:00:00 2001 From: Peter Robinson Date: Wed, 26 Jun 2024 18:10:08 +1000 Subject: [PATCH] Update text --- contracts/random/README.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/contracts/random/README.md b/contracts/random/README.md index 974c9363..b3e7a72f 100644 --- a/contracts/random/README.md +++ b/contracts/random/README.md @@ -1,11 +1,6 @@ # Random Number Generation Immutable has thoroughly investigated on-chain random number generation and use of off-chain random -providers such as Supra and Chainlink. To create a secure on-chain source requires an off-chain -service to inteact with the chain regularly. At present, there is not sufficient demand for -on-chain random for Immutable to invest in creating such a service. The source code, tests, and -threat model are contained in the [random2 branch](https://github.com/immutable/contracts/tree/random2). -In particular, teams considering using on-chain random number generation should read the -[threat model document](https://github.com/immutable/contracts/blob/random2/audits/random/202403-threat-model-random.md) as this describes in detail how on-chain randon number generation can -be used securely. +providers such as Supra and Chainlink. To create a secure on-chain random source requires an off-chain service to inteact with the chain regularly. At present, there is not sufficient demand for on-chain random for Immutable to invest in creating such a service. The source code, tests, and threat model from the investigation are contained in the [random2 branch](https://github.com/immutable/contracts/tree/random2). +In particular, teams considering using on-chain random number generation should read the [threat model document](https://github.com/immutable/contracts/blob/random2/audits/random/202403-threat-model-random.md) as this describes in detail how on-chain randon number generation can be used securely.