Sakaivault - Audit

In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority to arbitrarily transfer ownership.  In the contract `SAKAI` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and set important state variables and disrupt normal process and fee collection.  In the contract `SAKAI` the role `gasWallet` has authority over the functions. Any compromise to the `gasWallet` account may allow the hacker to take advantage of this authority to arbitrarily transfer `gasWallet` role and receive the WETH gas fees. - `setGasWallet()` changes gas wallet In the contract `SakaiStaking` the role `_owner` has authority over the functions. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. - `claimStuckTokens()` withdraws tokens or BNB or the contract - `setBNBFee()` changes bnb fee - `setStakingToken()` changes the `stakingToken` - `setBackendWallet()` changes the `backendWallet` - `startPool()` changes state `isStart`, begins to deposit - `setSpecialWallet()` changes wallet In the contract `SakaiStaking` the role `backendWallet` has authority over the functions. Any compromise to the `backendWallet` account may allow the hacker to take advantage of this authority. - `claimReward()` claims reward for user

All SAKAI tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute SAKAI tokens without the consensus of the community.