/Reach - Diff 1

The functions `setEthDistribution()` and `setReachDistribution()` accept two input arguments: the `_merkleRoot` containing all the users and the amount each user should get, and the `_amount` input representing the total amount to be distributed. The `_amount` value should be equal to the total amount to be distributed to all the leaves in the Merkle tree, and also less or equal to the current ETH or token balance of the contract. Otherwise, some users would be expecting rewards that are not even available.

Distributions are held in different rounds, where a user must submit their Merkle proof to claim their rewards for the current round. If the round has elapsed through calling `createDistribution()`, the Merkle roots are overwritten. Though the funds remain in the contract for a future distribution, there is no guarantee that the new Merkle roots will account for unclaimed prizes.

1. `ReachDistribution` - The owner can: - Pause and resume reward claiming. - Change the Merkle root of the current distribution at any time with `setEthDistribution()` and `setReachDistribution()`. See `Distributions Merkle Roots Can Be Overwritten`. - Create new distributions calling `createDistribution()`. - Change the address of `reachToken`. 2. `ReachFactory` - Owner can: - Change `prices`: the prices of the credits and the minimum ETH allocation. - Deploy new `ReachDistribution` contracts. - Sign data to allow users to call `topUp()` and `reserveEthAllocation()`. 3. `Reach` - Owner can: - Will receive all initial supply (`10e7` tokens). - Transfer out any ERC-20 tokens locked in the contract, including `REACH` fees captured from buy/sell tax. - Update router. - Exclude addresses from paying fees. - Mark addresses as AMM pairs (charge buy and sell tax). - Change buy and sell tax percentage (up to 20%). - Activate trading. - Set and change treasury and dev wallets. - Blacklist any address (bots). - Change the threshold to swap `REACH` fees to ETH.