🔒Security

Non-Technical Explanation

For non-technical users looking to use Ruggle and want to confirm that it's safe to use. The following key points are important to note:

• All Games are self contained in their own contract. Meaning Game 1 and Game 2 funds are stored in their own contracts. This is true of all current game modes as well. Mathematical errors such as overpaying Game 1 winner(s), and leaving Game 2 with a bad payout are not possible.

• The Ruggle contracts that users send funds into do not contain any backdoor withdraw functions. The only way to remove funds from the contract, is after the game fills or time expires. There is a function called RugPool() and anyone can call (not just the team), after a game is closed. It will pay the fees to the creator and protocol before paying out the remainder of the pool to the winner(s).

• The only withdraw function exits in the Factory contracts, that only pool creators interact with. This function is designed for the team to withdraw the creation fees. The Game contracts, do not contain a withdraw function. The only functionality is tied to declare a games results.

Security Scans

The Ruggle contracts have been analyzed using automated scanning tools, including Slither, Solhint, and Solscan. Identified critical issues have been reviewed and addressed at our discretion, including instances we assessed as false positives. Please note that these scans do not constitute a formal audit, and we do not guarantee the absence of vulnerabilities. Users should conduct their own due diligence before interacting with the contracts.