592 lines
66 KiB
XML
592 lines
66 KiB
XML
<?xml version="1.0"?>
|
|
<doc>
|
|
<assembly>
|
|
<name>Meadow.DebugSol.Generated</name>
|
|
</assembly>
|
|
<members>
|
|
<member name="T:Meadow.DebugSol.Generated.AccessControl">
|
|
<summary>From file @openzeppelin/contracts/access/AccessControl.sol<para/> <para/>Contract module that allows children to implement role-based access control mechanisms. This is a lightweight version that doesn't allow enumerating role members except through off-chain means by accessing the contract event logs. Some applications may benefit from on-chain enumerability, for those cases see {AccessControlEnumerable}. Roles are referred to by their `bytes32` identifier. These should be exposed in the external API and be unique. The best way to achieve this is by using `public constant` hash digests: ```solidity bytes32 public constant MY_ROLE = keccak256("MY_ROLE"); ``` Roles can be used to represent a set of permissions. To restrict access to a function call, use {hasRole}: ```solidity function foo() public { require(hasRole(MY_ROLE, msg.sender)); ... } ``` Roles can be granted and revoked dynamically via the {grantRole} and {revokeRole} functions. Each role has an associated admin role, and only accounts that have a role's admin role can call {grantRole} and {revokeRole}. By default, the admin role for all roles is `DEFAULT_ADMIN_ROLE`, which means that only accounts with this role will be able to grant or revoke other roles. More complex role relationships can be created by using {_setRoleAdmin}. WARNING: The `DEFAULT_ADMIN_ROLE` is also its own admin: it has permission to grant and revoke this role. Extra precautions should be taken to secure accounts that have been granted it. We recommend using {AccessControlDefaultAdminRules} to enforce additional security measures for this role.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Contract module that allows children to implement role-based access control mechanisms. This is a lightweight version that doesn't allow enumerating role members except through off-chain means by accessing the contract event logs. Some applications may benefit from on-chain enumerability, for those cases see {AccessControlEnumerable}. Roles are referred to by their `bytes32` identifier. These should be exposed in the external API and be unique. The best way to achieve this is by using `public constant` hash digests: ```solidity bytes32 public constant MY_ROLE = keccak256("MY_ROLE"); ``` Roles can be used to represent a set of permissions. To restrict access to a function call, use {hasRole}: ```solidity function foo() public { require(hasRole(MY_ROLE, msg.sender)); ... } ``` Roles can be granted and revoked dynamically via the {grantRole} and {revokeRole} functions. Each role has an associated admin role, and only accounts that have a role's admin role can call {grantRole} and {revokeRole}. By default, the admin role for all roles is `DEFAULT_ADMIN_ROLE`, which means that only accounts with this role will be able to grant or revoke other roles. More complex role relationships can be created by using {_setRoleAdmin}. WARNING: The `DEFAULT_ADMIN_ROLE` is also its own admin: it has permission to grant and revoke this role. Extra precautions should be taken to secure accounts that have been granted it. We recommend using {AccessControlDefaultAdminRules} to enforce additional security measures for this role. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Contract module that allows children to implement role-based access control mechanisms. This is a lightweight version that doesn't allow enumerating role members except through off-chain means by accessing the contract event logs. Some applications may benefit from on-chain enumerability, for those cases see {AccessControlEnumerable}. Roles are referred to by their `bytes32` identifier. These should be exposed in the external API and be unique. The best way to achieve this is by using `public constant` hash digests: ```solidity bytes32 public constant MY_ROLE = keccak256("MY_ROLE"); ``` Roles can be used to represent a set of permissions. To restrict access to a function call, use {hasRole}: ```solidity function foo() public { require(hasRole(MY_ROLE, msg.sender)); ... } ``` Roles can be granted and revoked dynamically via the {grantRole} and {revokeRole} functions. Each role has an associated admin role, and only accounts that have a role's admin role can call {grantRole} and {revokeRole}. By default, the admin role for all roles is `DEFAULT_ADMIN_ROLE`, which means that only accounts with this role will be able to grant or revoke other roles. More complex role relationships can be created by using {_setRoleAdmin}. WARNING: The `DEFAULT_ADMIN_ROLE` is also its own admin: it has permission to grant and revoke this role. Extra precautions should be taken to secure accounts that have been granted it. We recommend using {AccessControlDefaultAdminRules} to enforce additional security measures for this role. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.DEFAULT_ADMIN_ROLE">
|
|
<summary> <para/>Returns <c>bytes32</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.getRoleAdmin(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>Returns the admin role that controls `role`. See {grantRole} and {revokeRole}. To change a role's admin, use {_setRoleAdmin}. <para/>Returns <c>bytes32</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.grantRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Grants `role` to `account`. If `account` had not been already granted `role`, emits a {RoleGranted} event. Requirements: - the caller must have ``role``'s admin role. May emit a {RoleGranted} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.hasRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns `true` if `account` has been granted `role`. <para/>Returns <c>bool</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.renounceRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from the calling account. Roles are often managed via {grantRole} and {revokeRole}: this function's purpose is to provide a mechanism for accounts to lose their privileges if they are compromised (such as when a trusted device is misplaced). If the calling account had been revoked `role`, emits a {RoleRevoked} event. Requirements: - the caller must be `account`. May emit a {RoleRevoked} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.revokeRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from `account`. If `account` had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must have ``role``'s admin role. May emit a {RoleRevoked} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.AccessControl.supportsInterface(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>See {IERC165-supportsInterface}. <para/>Returns <c>bool</c></summary>
|
|
<param name="interfaceId"><c>bytes4</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.AccessControl.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.IAccessControl">
|
|
<summary>From file @openzeppelin/contracts/access/IAccessControl.sol<para/> <para/>External interface of AccessControl declared to support ERC165 detection.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>External interface of AccessControl declared to support ERC165 detection. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>External interface of AccessControl declared to support ERC165 detection. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.getRoleAdmin(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>Returns the admin role that controls `role`. See {grantRole} and {revokeRole}. To change a role's admin, use {AccessControl-_setRoleAdmin}. <para/>Returns <c>bytes32</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.grantRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Grants `role` to `account`. If `account` had not been already granted `role`, emits a {RoleGranted} event. Requirements: - the caller must have ``role``'s admin role.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.hasRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns `true` if `account` has been granted `role`. <para/>Returns <c>bool</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.renounceRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from the calling account. Roles are often managed via {grantRole} and {revokeRole}: this function's purpose is to provide a mechanism for accounts to lose their privileges if they are compromised (such as when a trusted device is misplaced). If the calling account had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must be `account`.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IAccessControl.revokeRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from `account`. If `account` had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must have ``role``'s admin role.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.IAccessControl.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.ReentrancyGuard">
|
|
<summary>From file @openzeppelin/contracts/security/ReentrancyGuard.sol<para/> <para/>Contract module that helps prevent reentrant calls to a function. Inheriting from `ReentrancyGuard` will make the {nonReentrant} modifier available, which can be applied to functions to make sure there are no nested (reentrant) calls to them. Note that because there is a single `nonReentrant` guard, functions marked as `nonReentrant` may not call one another. This can be worked around by making those functions `private`, and then adding `external` `nonReentrant` entry points to them. TIP: If you would like to learn more about reentrancy and alternative ways to protect against it, check out our blog post https://blog.openzeppelin.com/reentrancy-after-istanbul/[Reentrancy After Istanbul].</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.ReentrancyGuard.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Contract module that helps prevent reentrant calls to a function. Inheriting from `ReentrancyGuard` will make the {nonReentrant} modifier available, which can be applied to functions to make sure there are no nested (reentrant) calls to them. Note that because there is a single `nonReentrant` guard, functions marked as `nonReentrant` may not call one another. This can be worked around by making those functions `private`, and then adding `external` `nonReentrant` entry points to them. TIP: If you would like to learn more about reentrancy and alternative ways to protect against it, check out our blog post https://blog.openzeppelin.com/reentrancy-after-istanbul/[Reentrancy After Istanbul]. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.ReentrancyGuard.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Contract module that helps prevent reentrant calls to a function. Inheriting from `ReentrancyGuard` will make the {nonReentrant} modifier available, which can be applied to functions to make sure there are no nested (reentrant) calls to them. Note that because there is a single `nonReentrant` guard, functions marked as `nonReentrant` may not call one another. This can be worked around by making those functions `private`, and then adding `external` `nonReentrant` entry points to them. TIP: If you would like to learn more about reentrancy and alternative ways to protect against it, check out our blog post https://blog.openzeppelin.com/reentrancy-after-istanbul/[Reentrancy After Istanbul]. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.ReentrancyGuard.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.IERC20Permit">
|
|
<summary>From file @openzeppelin/contracts/token/ERC20/extensions/IERC20Permit.sol<para/> <para/>Interface of the ERC20 Permit extension allowing approvals to be made via signatures, as defined in https://eips.ethereum.org/EIPS/eip-2612[EIP-2612]. Adds the {permit} method, which can be used to change an account's ERC20 allowance (see {IERC20-allowance}) by presenting a message signed by the account. By not relying on {IERC20-approve}, the token holder account doesn't need to send a transaction, and thus is not required to hold Ether at all. ==== Security Considerations There are two important considerations concerning the use of `permit`. The first is that a valid permit signature expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be considered as an intention to spend the allowance in any specific way. The second is that because permits have built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be generally recommended is: ```solidity function doThingWithPermit(..., uint256 value, uint256 deadline, uint8 v, bytes32 r, bytes32 s) public { try token.permit(msg.sender, address(this), value, deadline, v, r, s) {} catch {} doThing(..., value); } function doThing(..., uint256 value) public { token.safeTransferFrom(msg.sender, address(this), value); ... } ``` Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also {SafeERC20-safeTransferFrom}). Additionally, note that smart contract wallets (such as Argent or Safe) are not able to produce permit signatures, so contracts should have entry points that don't rely on permit.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20Permit.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC20 Permit extension allowing approvals to be made via signatures, as defined in https://eips.ethereum.org/EIPS/eip-2612[EIP-2612]. Adds the {permit} method, which can be used to change an account's ERC20 allowance (see {IERC20-allowance}) by presenting a message signed by the account. By not relying on {IERC20-approve}, the token holder account doesn't need to send a transaction, and thus is not required to hold Ether at all. ==== Security Considerations There are two important considerations concerning the use of `permit`. The first is that a valid permit signature expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be considered as an intention to spend the allowance in any specific way. The second is that because permits have built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be generally recommended is: ```solidity function doThingWithPermit(..., uint256 value, uint256 deadline, uint8 v, bytes32 r, bytes32 s) public { try token.permit(msg.sender, address(this), value, deadline, v, r, s) {} catch {} doThing(..., value); } function doThing(..., uint256 value) public { token.safeTransferFrom(msg.sender, address(this), value); ... } ``` Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also {SafeERC20-safeTransferFrom}). Additionally, note that smart contract wallets (such as Argent or Safe) are not able to produce permit signatures, so contracts should have entry points that don't rely on permit. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20Permit.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC20 Permit extension allowing approvals to be made via signatures, as defined in https://eips.ethereum.org/EIPS/eip-2612[EIP-2612]. Adds the {permit} method, which can be used to change an account's ERC20 allowance (see {IERC20-allowance}) by presenting a message signed by the account. By not relying on {IERC20-approve}, the token holder account doesn't need to send a transaction, and thus is not required to hold Ether at all. ==== Security Considerations There are two important considerations concerning the use of `permit`. The first is that a valid permit signature expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be considered as an intention to spend the allowance in any specific way. The second is that because permits have built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be generally recommended is: ```solidity function doThingWithPermit(..., uint256 value, uint256 deadline, uint8 v, bytes32 r, bytes32 s) public { try token.permit(msg.sender, address(this), value, deadline, v, r, s) {} catch {} doThing(..., value); } function doThing(..., uint256 value) public { token.safeTransferFrom(msg.sender, address(this), value); ... } ``` Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also {SafeERC20-safeTransferFrom}). Additionally, note that smart contract wallets (such as Argent or Safe) are not able to produce permit signatures, so contracts should have entry points that don't rely on permit. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20Permit.DOMAIN_SEPARATOR">
|
|
<summary>Returns the domain separator used in the encoding of the signature for {permit}, as defined by {EIP712}. <para/>Returns <c>bytes32</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20Permit.nonces(Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns the current nonce for `owner`. This value must be included whenever a signature is generated for {permit}. Every successful call to {permit} increases ``owner``'s nonce by one. This prevents a signature from being used multiple times. <para/>Returns <c>uint256</c></summary>
|
|
<param name="owner"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20Permit.permit(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256,Meadow.Core.EthTypes.UInt256,System.Byte,System.Collections.Generic.IEnumerable{System.Byte},System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>Sets `value` as the allowance of `spender` over ``owner``'s tokens, given ``owner``'s signed approval. IMPORTANT: The same issues {IERC20-approve} has related to transaction ordering also apply here. Emits an {Approval} event. Requirements: - `spender` cannot be the zero address. - `deadline` must be a timestamp in the future. - `v`, `r` and `s` must be a valid `secp256k1` signature from `owner` over the EIP712-formatted function arguments. - the signature must use ``owner``'s current nonce (see {nonces}). For more information on the signature format, see the https://eips.ethereum.org/EIPS/eip-2612#specification[relevant EIP section]. CAUTION: See Security Considerations above.</summary>
|
|
<param name="owner"><c>address</c></param>
|
|
<param name="spender"><c>address</c></param>
|
|
<param name="value"><c>uint256</c></param>
|
|
<param name="deadline"><c>uint256</c></param>
|
|
<param name="v"><c>uint8</c></param>
|
|
<param name="r"><c>bytes32</c></param>
|
|
<param name="s"><c>bytes32</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.IERC20Permit.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.IERC20">
|
|
<summary>From file @openzeppelin/contracts/token/ERC20/IERC20.sol<para/> <para/>Interface of the ERC20 standard as defined in the EIP.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC20 standard as defined in the EIP. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC20 standard as defined in the EIP. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.allowance(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns the remaining number of tokens that `spender` will be allowed to spend on behalf of `owner` through {transferFrom}. This is zero by default. This value changes when {approve} or {transferFrom} are called. <para/>Returns <c>uint256</c></summary>
|
|
<param name="owner"><c>address</c></param>
|
|
<param name="spender"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.approve(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256)">
|
|
<summary>Sets `amount` as the allowance of `spender` over the caller's tokens. Returns a boolean value indicating whether the operation succeeded. IMPORTANT: Beware that changing an allowance with this method brings the risk that someone may use both the old and the new allowance by unfortunate transaction ordering. One possible solution to mitigate this race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards: https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729 Emits an {Approval} event. <para/>Returns <c>bool</c></summary>
|
|
<param name="spender"><c>address</c></param>
|
|
<param name="amount"><c>uint256</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.balanceOf(Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns the amount of tokens owned by `account`. <para/>Returns <c>uint256</c></summary>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.totalSupply">
|
|
<summary>Returns the amount of tokens in existence. <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.transfer(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256)">
|
|
<summary>Moves `amount` tokens from the caller's account to `to`. Returns a boolean value indicating whether the operation succeeded. Emits a {Transfer} event. <para/>Returns <c>bool</c></summary>
|
|
<param name="to"><c>address</c></param>
|
|
<param name="amount"><c>uint256</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC20.transferFrom(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256)">
|
|
<summary>Moves `amount` tokens from `from` to `to` using the allowance mechanism. `amount` is then deducted from the caller's allowance. Returns a boolean value indicating whether the operation succeeded. Emits a {Transfer} event. <para/>Returns <c>bool</c></summary>
|
|
<param name="from"><c>address</c></param>
|
|
<param name="to"><c>address</c></param>
|
|
<param name="amount"><c>uint256</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.IERC20.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.SafeERC20">
|
|
<summary>From file @openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol<para/> <para/>SafeERC20 <para/>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.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.SafeERC20.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>SafeERC20 <para/>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. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.SafeERC20.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>SafeERC20 <para/>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. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.SafeERC20.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.Address">
|
|
<summary>From file @openzeppelin/contracts/utils/Address.sol<para/> <para/>Collection of functions related to the address type</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Address.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Collection of functions related to the address type <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Address.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Collection of functions related to the address type <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.Address.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.Context">
|
|
<summary>From file @openzeppelin/contracts/utils/Context.sol<para/> <para/>Provides information about the current execution context, including the sender of the transaction and its data. While these are generally available via msg.sender and msg.data, they should not be accessed in such a direct manner, since when dealing with meta-transactions the account sending and paying for execution may not be the actual sender (as far as an application is concerned). This contract is only required for intermediate, library-like contracts.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Context.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Provides information about the current execution context, including the sender of the transaction and its data. While these are generally available via msg.sender and msg.data, they should not be accessed in such a direct manner, since when dealing with meta-transactions the account sending and paying for execution may not be the actual sender (as far as an application is concerned). This contract is only required for intermediate, library-like contracts. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Context.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Provides information about the current execution context, including the sender of the transaction and its data. While these are generally available via msg.sender and msg.data, they should not be accessed in such a direct manner, since when dealing with meta-transactions the account sending and paying for execution may not be the actual sender (as far as an application is concerned). This contract is only required for intermediate, library-like contracts. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.Context.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.ERC165">
|
|
<summary>From file @openzeppelin/contracts/utils/introspection/ERC165.sol<para/> <para/>Implementation of the {IERC165} interface. Contracts that want to implement ERC165 should inherit from this contract and override {supportsInterface} to check for the additional interface id that will be supported. For example: ```solidity function supportsInterface(bytes4 interfaceId) public view virtual override returns (bool) { return interfaceId == type(MyInterface).interfaceId || super.supportsInterface(interfaceId); } ``` Alternatively, {ERC165Storage} provides an easier to use but more expensive implementation.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.ERC165.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Implementation of the {IERC165} interface. Contracts that want to implement ERC165 should inherit from this contract and override {supportsInterface} to check for the additional interface id that will be supported. For example: ```solidity function supportsInterface(bytes4 interfaceId) public view virtual override returns (bool) { return interfaceId == type(MyInterface).interfaceId || super.supportsInterface(interfaceId); } ``` Alternatively, {ERC165Storage} provides an easier to use but more expensive implementation. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.ERC165.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Implementation of the {IERC165} interface. Contracts that want to implement ERC165 should inherit from this contract and override {supportsInterface} to check for the additional interface id that will be supported. For example: ```solidity function supportsInterface(bytes4 interfaceId) public view virtual override returns (bool) { return interfaceId == type(MyInterface).interfaceId || super.supportsInterface(interfaceId); } ``` Alternatively, {ERC165Storage} provides an easier to use but more expensive implementation. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.ERC165.supportsInterface(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>See {IERC165-supportsInterface}. <para/>Returns <c>bool</c></summary>
|
|
<param name="interfaceId"><c>bytes4</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.ERC165.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.IERC165">
|
|
<summary>From file @openzeppelin/contracts/utils/introspection/IERC165.sol<para/> <para/>Interface of the ERC165 standard, as defined in the https://eips.ethereum.org/EIPS/eip-165[EIP]. Implementers can declare support of contract interfaces, which can then be queried by others ({ERC165Checker}). For an implementation, see {ERC165}.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC165.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC165 standard, as defined in the https://eips.ethereum.org/EIPS/eip-165[EIP]. Implementers can declare support of contract interfaces, which can then be queried by others ({ERC165Checker}). For an implementation, see {ERC165}. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC165.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Interface of the ERC165 standard, as defined in the https://eips.ethereum.org/EIPS/eip-165[EIP]. Implementers can declare support of contract interfaces, which can then be queried by others ({ERC165Checker}). For an implementation, see {ERC165}. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IERC165.supportsInterface(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>Returns true if this contract implements the interface defined by `interfaceId`. See the corresponding https://eips.ethereum.org/EIPS/eip-165#how-interfaces-are-identified[EIP section] to learn more about how these ids are created. This function call must use less than 30 000 gas. <para/>Returns <c>bool</c></summary>
|
|
<param name="interfaceId"><c>bytes4</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.IERC165.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.Math">
|
|
<summary>From file @openzeppelin/contracts/utils/math/Math.sol<para/> <para/>Standard math utilities missing in the Solidity language.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Math.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Standard math utilities missing in the Solidity language. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Math.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Standard math utilities missing in the Solidity language. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.Math.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.SignedMath">
|
|
<summary>From file @openzeppelin/contracts/utils/math/SignedMath.sol<para/> <para/>Standard signed math utilities missing in the Solidity language.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.SignedMath.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Standard signed math utilities missing in the Solidity language. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.SignedMath.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Standard signed math utilities missing in the Solidity language. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.SignedMath.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.Strings">
|
|
<summary>From file @openzeppelin/contracts/utils/Strings.sol<para/> <para/>String operations.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Strings.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>String operations. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.Strings.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>String operations. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.Strings.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.EnumerableSet">
|
|
<summary>From file @openzeppelin/contracts/utils/structs/EnumerableSet.sol<para/> <para/>Library for managing https://en.wikipedia.org/wiki/Set_(abstract_data_type)[sets] of primitive types. Sets have the following properties: - Elements are added, removed, and checked for existence in constant time (O(1)). - Elements are enumerated in O(n). No guarantees are made on the ordering. ```solidity contract Example { // Add the library methods using EnumerableSet for EnumerableSet.AddressSet; // Declare a set state variable EnumerableSet.AddressSet private mySet; } ``` As of v3.3.0, sets of type `bytes32` (`Bytes32Set`), `address` (`AddressSet`) and `uint256` (`UintSet`) are supported. [WARNING] ==== Trying to delete such a structure from storage will likely result in data corruption, rendering the structure unusable. See https://github.com/ethereum/solidity/pull/11843[ethereum/solidity#11843] for more info. In order to clean an EnumerableSet, you can either remove all elements one by one or create a fresh instance using an array of EnumerableSet. ====</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.EnumerableSet.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Library for managing https://en.wikipedia.org/wiki/Set_(abstract_data_type)[sets] of primitive types. Sets have the following properties: - Elements are added, removed, and checked for existence in constant time (O(1)). - Elements are enumerated in O(n). No guarantees are made on the ordering. ```solidity contract Example { // Add the library methods using EnumerableSet for EnumerableSet.AddressSet; // Declare a set state variable EnumerableSet.AddressSet private mySet; } ``` As of v3.3.0, sets of type `bytes32` (`Bytes32Set`), `address` (`AddressSet`) and `uint256` (`UintSet`) are supported. [WARNING] ==== Trying to delete such a structure from storage will likely result in data corruption, rendering the structure unusable. See https://github.com/ethereum/solidity/pull/11843[ethereum/solidity#11843] for more info. In order to clean an EnumerableSet, you can either remove all elements one by one or create a fresh instance using an array of EnumerableSet. ==== <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.EnumerableSet.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Library for managing https://en.wikipedia.org/wiki/Set_(abstract_data_type)[sets] of primitive types. Sets have the following properties: - Elements are added, removed, and checked for existence in constant time (O(1)). - Elements are enumerated in O(n). No guarantees are made on the ordering. ```solidity contract Example { // Add the library methods using EnumerableSet for EnumerableSet.AddressSet; // Declare a set state variable EnumerableSet.AddressSet private mySet; } ``` As of v3.3.0, sets of type `bytes32` (`Bytes32Set`), `address` (`AddressSet`) and `uint256` (`UintSet`) are supported. [WARNING] ==== Trying to delete such a structure from storage will likely result in data corruption, rendering the structure unusable. See https://github.com/ethereum/solidity/pull/11843[ethereum/solidity#11843] for more info. In order to clean an EnumerableSet, you can either remove all elements one by one or create a fresh instance using an array of EnumerableSet. ==== <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.EnumerableSet.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.IClaimAbleNFT">
|
|
<summary>From file contracts/activity/NFTClaimStage2WL.sol<para/> <para/>Notice: Contract for the activity of NFT claim stage 2.</summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IClaimAbleNFT.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Notice: Contract for the activity of NFT claim stage 2. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IClaimAbleNFT.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>Notice: Contract for the activity of NFT claim stage 2. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.IClaimAbleNFT.safeMint(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256)">
|
|
<summary></summary>
|
|
<param name="to"><c>address</c></param>
|
|
<param name="tokenID"><c>uint256</c></param>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.IClaimAbleNFT.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.NFTClaimStage2WL">
|
|
<summary>From file contracts/activity/NFTClaimStage2WL.sol<para/></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.Deploy(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256,Meadow.Core.EthTypes.Address,Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>
|
|
</summary>
|
|
<param name="_nftAddress"><c>address</c></param>
|
|
<param name="_nftIdStart"><c>uint256</c></param>
|
|
<param name="_mintConfig"><c>address</c></param>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.New(Meadow.Core.EthTypes.Address,Meadow.Core.EthTypes.UInt256,Meadow.Core.EthTypes.Address,Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>
|
|
</summary>
|
|
<param name="_nftAddress"><c>address</c></param>
|
|
<param name="_nftIdStart"><c>uint256</c></param>
|
|
<param name="_mintConfig"><c>address</c></param>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.DEFAULT_ADMIN_ROLE">
|
|
<summary> <para/>Returns <c>bytes32</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.MANAGE_ROLE">
|
|
<summary> <para/>Notice: Only MANAGE_ROLE can change mint config <para/>Returns <c>bytes32</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.UPDATE_WL_ROLE">
|
|
<summary> <para/>Notice: Only UPDATE_WL_ROLE can add white listing <para/>Returns <c>bytes32</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.addParse1WL(System.Collections.Generic.IEnumerable{Meadow.Core.EthTypes.Address},System.Collections.Generic.IEnumerable{Meadow.Core.EthTypes.UInt256})">
|
|
<summary></summary>
|
|
<param name="_addressList"><c>address[]</c></param>
|
|
<param name="_nums"><c>uint256[]</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.addParse2WL(System.Collections.Generic.IEnumerable{Meadow.Core.EthTypes.Address})">
|
|
<summary></summary>
|
|
<param name="_addressList"><c>address[]</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.claim(Meadow.Core.EthTypes.UInt256)">
|
|
<summary>claim NFT</summary>
|
|
<param name="nftCount"><c>uint256</c>: nft count to claim</param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.getRoleAdmin(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>Returns the admin role that controls `role`. See {grantRole} and {revokeRole}. To change a role's admin, use {_setRoleAdmin}. <para/>Returns <c>bytes32</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.grantRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Grants `role` to `account`. If `account` had not been already granted `role`, emits a {RoleGranted} event. Requirements: - the caller must have ``role``'s admin role. May emit a {RoleGranted} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.hasRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Returns `true` if `account` has been granted `role`. <para/>Returns <c>bool</c></summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.mintConfig">
|
|
<summary> <para/>Returns <c>uint256,address,uint256,address,uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.mintParse">
|
|
<summary> <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.mintedNft">
|
|
<summary> <para/>Returns <c>uint256[]</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.mintedNum">
|
|
<summary> <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.nftAddress">
|
|
<summary> <para/>Returns <c>address</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.nftIdStart">
|
|
<summary> <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.renounceRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from the calling account. Roles are often managed via {grantRole} and {revokeRole}: this function's purpose is to provide a mechanism for accounts to lose their privileges if they are compromised (such as when a trusted device is misplaced). If the calling account had been revoked `role`, emits a {RoleRevoked} event. Requirements: - the caller must be `account`. May emit a {RoleRevoked} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.revokeParse1WL(System.Collections.Generic.IEnumerable{Meadow.Core.EthTypes.Address})">
|
|
<summary></summary>
|
|
<param name="_addressList"><c>address[]</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.revokeParse2WL(System.Collections.Generic.IEnumerable{Meadow.Core.EthTypes.Address})">
|
|
<summary></summary>
|
|
<param name="_addressList"><c>address[]</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.revokeRole(System.Collections.Generic.IEnumerable{System.Byte},Meadow.Core.EthTypes.Address)">
|
|
<summary>Revokes `role` from `account`. If `account` had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must have ``role``'s admin role. May emit a {RoleRevoked} event.</summary>
|
|
<param name="role"><c>bytes32</c></param>
|
|
<param name="account"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.supportsInterface(System.Collections.Generic.IEnumerable{System.Byte})">
|
|
<summary>See {IERC165-supportsInterface}. <para/>Returns <c>bool</c></summary>
|
|
<param name="interfaceId"><c>bytes4</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.totalCount">
|
|
<summary> <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.updateMintConfig(Meadow.Core.EthTypes.Address)">
|
|
<summary></summary>
|
|
<param name="config"><c>address</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.updateMintParse(Meadow.Core.EthTypes.UInt256)">
|
|
<summary></summary>
|
|
<param name="_mintParse"><c>uint256</c></param>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.NFTClaimStage2WL.whiteCount">
|
|
<summary> <para/>Returns <c>uint256</c></summary>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.NFTClaimStage2WL.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
<member name="T:Meadow.DebugSol.Generated.DbgEntry">
|
|
<summary>From file Test1.t.sol<para/></summary>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.DbgEntry.Deploy(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="M:Meadow.DebugSol.Generated.DbgEntry.New(Meadow.JsonRpc.Client.IJsonRpcClient,Meadow.JsonRpc.Types.TransactionParams,System.Nullable{Meadow.Core.EthTypes.Address})">
|
|
<summary>
|
|
Deploys the contract. <para/>
|
|
</summary>
|
|
<param name="rpcClient">The RPC client to be used for this contract instance.</param>
|
|
<param name="defaultFromAccount">If null then the first account returned by eth_accounts will be used.</param>
|
|
<returns>An contract instance pointed at the deployed contract address.</returns>
|
|
</member>
|
|
<member name="P:Meadow.DebugSol.Generated.DbgEntry.FallbackFunction">
|
|
<summary>The contract fallback function. <para/></summary>
|
|
</member>
|
|
</members>
|
|
</doc>
|