‘RouteRandomizer.sol’

[HrikB]

Description

With the completion of the ‘Lootbox.sol’ contract, it occurs to me that this idea of routing to a random contract with the same inputs does not need to be limited to Crafter contracts. You can put Transformer or Minter contracts behind it as well! Perhaps if you hold a special nft, it behaves as a lootbox 98% of the time, but 2% of the time it upgrades your sword. Or maybe a minting can be held where the contract from which you are minting has probabilities involved. I think that this is a really cool concept and would be great to have as one of the contracts whose support is gated behind holding the OWL NFT (or a certain amount of $OWL). And the ‘Lootbox.sol’ can be a great teaser and demonstration of the usecase. For free, game developers can route randomize Crafter contracts but to route randomize other plugins or even mix and match, they’ll have to be a holder.

Implementation

• Initializer will initialize array of contract addresses and array of signatures (must be same size)
• ‘randomizeRoute(bytes[] memory args)’ whose argument array contains the respective arguments from the array of signatures
• First argument in array of signatures will always be address that will be filled in to be ‘_msgSender()’ by ‘randomizeRoute()’
• All functions that are able to be called by the ‘RouteRandomizer.sol’ contract must be refactored. The function must be prepended with _ and made internal. Then, address argument is prepended to the internal function. Finally, two functions are created of the same name without the ‘_’. One takes the address as the parameter and is protected by ‘onlyRole(FORWARDER_ROLE)’. The other one doesn’t have an address parameter. Both function will call the internal function but the protected one passes the parameterized address while the other simply passes ‘_msgSender()’.

[aqzhen]

/cib

[github-actions[bot]]

Branch issue-266 created! Clone with: git fetch && git checkout --track origin/issue-266 Rebase develop branch changes with: git checkout issue-266 && git rebase develop

[HrikB]

@aqzhen Add boolean routed on Transformer.sol and Crafter contracts to indicate it is part of a RouteRandomizer scheme. It would be problematic if the Crafter or Transformer could be called directly.