improvements

Author: aditya520

pages/entropy/protocol-design.mdx

@@ -27,6 +27,8 @@ Each random number in the sequence can then be verified against the previous one
 
 Pyth Entropy uses automatic callbacks to simplify the flow:
 
+- **Request**: To produce a random number, the following steps occur.
+
 1. The user U draws a random number $x_U$, and submits it to the contract. The contract generates the hash $h_U = \mathrm{hash}(x_U)$ and records both $x_U$ and $h_U$. The contract uses [`constructUserCommitment`](https://github.com/pyth-network/pyth-crosschain/blob/7bccde484f01c19844b7105d63df207a24018957/target_chains/ethereum/contracts/contracts/entropy/Entropy.sol#L628-L632) to generate the user's commitment.
 2. The contract [remembers $h_U$ and assigns it an incrementing **sequence number $i$**](https://github.com/pyth-network/pyth-crosschain/blob/7bccde484f01c19844b7105d63df207a24018957/target_chains/ethereum/contracts/contracts/entropy/Entropy.sol#L232-L246), representing which
    of the provider's random numbers the user will receive. $x_U$ is recorded in the [event logs](https://github.com/pyth-network/pyth-crosschain/blob/7bccde484f01c19844b7105d63df207a24018957/target_chains/ethereum/contracts/contracts/entropy/Entropy.sol#L300-L306).
@@ -35,11 +37,13 @@ Pyth Entropy uses automatic callbacks to simplify the flow:
 5. If both of the above conditions are satisfied,
    the random number $r = \mathrm{hash}(x_i, x_U)$ is generated and a callback is made to the requesting contract.
 
-This protocol has the same security properties as the 2-party randomness protocol above: as long as either
-the provider or user is honest, the number $r$ is random.
-
 In this flow, providers can refuse revealing $x_i$ if the final random number $r$ is not in their favor, or
 they may be able to access $x_U$ before on-chain submission (e.g. via mempool) and rotate their commitments to influence the random number $r$.
 Of course, both of these behaviors are detectable and protocols can blacklist providers that exhibit them.
 
-Pyth Network deployed a default entropy provider. The code of default provider can be found [here](https://github.com/pyth-network/pyth-crosschain/tree/7bccde484f01c19844b7105d63df207a24018957/apps/fortuna).
+This protocol has the same security properties as the 2-party randomness protocol above: as long as either
+the provider or user is honest, the number $r$ is random.
+
+Note that providers need to be careful to ensure their off-chain service isn't compromised to reveal the random numbers -- if this occurs, then users will be able to influence the random number $r$.
+
+There are two separate default deployed providers, one for mainnet chains and one for testnet chains. The code of default deployed provider can be found [here](https://github.com/pyth-network/pyth-crosschain/tree/7bccde484f01c19844b7105d63df207a24018957/apps/fortuna).