-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #43 from Into-the-Fathom/mainnet-deployment-reaudit
Mainnet deployment reaudit
- Loading branch information
Showing
130 changed files
with
3,622 additions
and
1,564 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
// SPDX-License-Identifier: MIT | ||
// OpenZeppelin Contracts (last updated v4.7.0) (token/ERC20/utils/SafeERC20.sol) | ||
|
||
pragma solidity 0.8.16; | ||
|
||
import "../dao/tokens/ERC20/IERC20.sol"; | ||
import "../dao/tokens/ERC20/extensions/IERC20Permit.sol"; | ||
import "./Address.sol"; | ||
|
||
/** | ||
* @title SafeERC20 | ||
* @dev Wrappers around ERC20 operations that throw on failure (when the token | ||
* contract returns false). Tokens that return no value (and instead revert or | ||
* throw on failure) are also supported, non-reverting calls are assumed to be | ||
* successful. | ||
* To use this library you can add a `using SafeERC20 for IERC20;` statement to your contract, | ||
* which allows you to call the safe operations as `token.safeTransfer(...)`, etc. | ||
*/ | ||
library SafeERC20Staking { | ||
using Address for address; | ||
|
||
function safeTransferFrom( | ||
IERC20 token, | ||
address from, | ||
address to, | ||
uint256 value | ||
) internal { | ||
_callOptionalReturn(token, abi.encodeWithSelector(token.transferFrom.selector, from, to, value)); | ||
} | ||
|
||
/** | ||
* @dev Deprecated. This function has issues similar to the ones found in | ||
* {IERC20-approve}, and its usage is discouraged. | ||
* | ||
* Whenever possible, use {safeIncreaseAllowance} and | ||
* {safeDecreaseAllowance} instead. | ||
*/ | ||
function safeApprove( | ||
IERC20 token, | ||
address spender, | ||
uint256 value | ||
) internal { | ||
// safeApprove should only be called when setting an initial allowance, | ||
// or when resetting it to zero. To increase and decrease it, use | ||
// 'safeIncreaseAllowance' and 'safeDecreaseAllowance' | ||
require((value == 0) || (token.allowance(address(this), spender) == 0), "SafeERC20: approve from non-zero to non-zero allowance"); | ||
_callOptionalReturn(token, abi.encodeWithSelector(token.approve.selector, spender, value)); | ||
} | ||
|
||
/** | ||
* @dev Imitates a Solidity high-level call (i.e. a regular function call to a contract), relaxing the requirement | ||
* on the return value: the return value is optional (but if data is returned, it must not be false). | ||
* @param token The token targeted by the call. | ||
* @param data The call data (encoded using abi.encode or one of its variants). | ||
*/ | ||
function _callOptionalReturn(IERC20 token, bytes memory data) private { | ||
// We need to perform a low level call here, to bypass Solidity's return data size checking mechanism, since | ||
// we're implementing it ourselves. We use {Address-functionCall} to perform this call, which verifies that | ||
// the target address contains contract code and also asserts for success in the low-level call. | ||
|
||
bytes memory returndata = address(token).functionCall(data, "SafeERC20: low-level call failed"); | ||
if (returndata.length > 0) { | ||
// Return data is optional | ||
require(abi.decode(returndata, (bool)), "SafeERC20: ERC20 operation did not succeed"); | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.