@superfluid-finance/ethereum-contracts 1.7.3-dev.0b3c40b.0 → 1.7.3-dev.6bb2ebd.0

package/build/contracts/AccessControl.json

@@ -4196,7 +4196,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.912Z",
+  "updatedAt": "2023-08-14T13:02:43.717Z",
   "devdoc": {
     "details": "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.",
     "events": {

package/build/contracts/AccessControlEnumerable.json

@@ -1787,7 +1787,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.922Z",
+  "updatedAt": "2023-08-14T13:02:43.720Z",
   "devdoc": {
     "details": "Extension of {AccessControl} that allows enumerating the members of each role.",
     "events": {

package/build/contracts/Address.json

@@ -4371,7 +4371,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.957Z",
+  "updatedAt": "2023-08-14T13:02:43.756Z",
   "devdoc": {
     "details": "Collection of functions related to the address type",
     "kind": "dev",

package/build/contracts/AgreementBase.json

@@ -828,7 +828,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.992Z",
+  "updatedAt": "2023-08-14T13:02:43.788Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/contracts/AgreementLibrary.json

@@ -7358,7 +7358,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.992Z",
+  "updatedAt": "2023-08-14T13:02:43.789Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Helper library for building super agreement",

package/build/contracts/BaseRelayRecipient.json

@@ -624,7 +624,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.149Z",
+  "updatedAt": "2023-08-14T13:02:43.973Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "A base contract to be inherited by any contract that want to receive relayed transactions      A subclass must use \"_msgSender()\" instead of \"msg.sender\"      MODIFIED FROM: https://github.com/opengsn/forwarder/blob/master/contracts/BaseRelayRecipient.sol",

package/build/contracts/BatchLiquidator.json

@@ -7830,7 +7830,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.678Z",
+  "updatedAt": "2023-08-14T13:02:44.623Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract allows to delete multiple flows in a single transaction.",

package/build/contracts/BatchOperation.json

@@ -6654,7 +6654,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.115Z",
+  "updatedAt": "2023-08-14T13:02:43.932Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/CFAv1Forwarder.json

@@ -21263,7 +21263,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.682Z",
+  "updatedAt": "2023-08-14T13:02:44.627Z",
   "devdoc": {
     "author": "Superfluid The CFAv1Forwarder contract provides an easy to use interface to ConstantFlowAgreementV1 specific functionality of Super Tokens. Instances of this contract can operate on the protocol only if configured as \"trusted forwarder\" by protocol governance.",
     "kind": "dev",

package/build/contracts/CFAv1ForwarderDeployerLibrary.json

@@ -16561,7 +16561,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.723Z",
+  "updatedAt": "2023-08-14T13:02:44.678Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/contracts/CFAv1Library.json

@@ -16076,7 +16076,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.057Z",
+  "updatedAt": "2023-08-14T13:02:43.864Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "for working with the constant flow agreement within soliditythe first set of functions are each for callAgreement()the second set of functions are each for use in callAgreementWithContext()",

package/build/contracts/CallUtils.json

@@ -2483,7 +2483,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.149Z",
+  "updatedAt": "2023-08-14T13:02:43.973Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ClosingOnUpdateFlowTestApp.json

@@ -20692,7 +20692,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.171Z",
+  "updatedAt": "2023-08-14T13:02:43.999Z",
   "devdoc": {
     "details": "This is CFA SuperApp that closes an updated flow.",
     "kind": "dev",

package/build/contracts/ConstantFlowAgreementV1.json

@@ -83247,7 +83247,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.996Z",
+  "updatedAt": "2023-08-14T13:02:43.794Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Please read IConstantFlowAgreementV1 for implementation notes.For more technical notes, please visit protocol-monorepo wiki area.  Storage Layout Notes Agreement State NOTE The Agreement State slot is computed with the following function: keccak256(abi.encode(\"AgreementState\", msg.sender, account, slotId)) slotId           = 0 msg.sender       = address of CFAv1 account          = context.msgSender  Flow Agreement State stores the global FlowData state for an account.   Agreement Data NOTE The Agreement Data slot is calculated with the following function: keccak256(abi.encode(\"AgreementData\", agreementClass, agreementId)) agreementClass   = address of CFAv1 agreementId      = FlowId | FlowOperatorId  FlowId           = keccak256(abi.encode(flowSender, flowReceiver)) FlowId stores FlowData between a flowSender and flowReceiver.  FlowOperatorId   = keccak256(abi.encode(\"flowOperator\", flowSender, flowOperator)) FlowOperatorId stores FlowOperatorData between a flowSender and flowOperator.",

package/build/contracts/ConstantInflowNFT.json

@@ -18880,7 +18880,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.590Z",
+  "updatedAt": "2023-08-14T13:02:44.513Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract does not hold any storage, but references the ConstantOutflowNFT contract storage.",

package/build/contracts/ConstantOutflowNFT.json

@@ -21026,7 +21026,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.597Z",
+  "updatedAt": "2023-08-14T13:02:44.522Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract uses mint/burn interface for flow creation/deletion and holds the actual storage for both NFTs.",

package/build/contracts/Context.json

@@ -257,7 +257,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.958Z",
+  "updatedAt": "2023-08-14T13:02:43.760Z",
   "devdoc": {
     "details": "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.",
     "kind": "dev",

package/build/contracts/ContextDefinitions.json

@@ -6654,7 +6654,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.118Z",
+  "updatedAt": "2023-08-14T13:02:43.935Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/CustomSuperTokenBase.json

@@ -148,7 +148,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.115Z",
+  "updatedAt": "2023-08-14T13:02:43.931Z",
   "devdoc": {
     "author": "Superfluid NOTE: - Because of how solidity lays out its storage variables and how custom   super tokens inherit the SuperToken standard implementation, it is   required that the custom token proxy pads its implementation   with reserved storage used by the Super Token implementation. - You will need to append your own proxy implementation after the base   - Refer to SETH.sol for an example how it is used.",
     "kind": "dev",

package/build/contracts/ERC165.json

@@ -325,7 +325,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.960Z",
+  "updatedAt": "2023-08-14T13:02:43.762Z",
   "devdoc": {
     "details": "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.",
     "kind": "dev",

package/build/contracts/ERC1820Implementer.json

@@ -1198,7 +1198,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.961Z",
+  "updatedAt": "2023-08-14T13:02:43.762Z",
   "devdoc": {
     "details": "Implementation of the {IERC1820Implementer} interface. Contracts may inherit from this and call {_registerInterfaceForAddress} to declare their willingness to be implementers. {IERC1820Registry-setInterfaceImplementer} should then be called for the registration to be complete. CAUTION: This file is deprecated as of v4.9 and will be removed in the next major release.",
     "kind": "dev",

package/build/contracts/ERC1820RegistryCompiled.json

@@ -243,7 +243,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.150Z",
+  "updatedAt": "2023-08-14T13:02:43.975Z",
   "devdoc": {
     "details": "This is meant to be used by test framework to get the raw bytecode without compiling the origin contract",
     "kind": "dev",

package/build/contracts/ERC20.json

@@ -15059,7 +15059,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.927Z",
+  "updatedAt": "2023-08-14T13:02:43.740Z",
   "devdoc": {
     "details": "Implementation of the {IERC20} interface. This implementation is agnostic to the way tokens are created. This means that a supply mechanism has to be added in a derived contract using {_mint}. For a generic mechanism see {ERC20PresetMinterPauser}. TIP: For a detailed writeup see our guide https://forum.openzeppelin.com/t/how-to-implement-erc20-supply-mechanisms/226[How to implement supply mechanisms]. The default value of {decimals} is 18. To change this, you should override this function so it returns a different value. We have followed general OpenZeppelin Contracts guidelines: functions revert instead returning `false` on failure. This behavior is nonetheless conventional and does not conflict with the expectations of ERC20 applications. Additionally, an {Approval} event is emitted on calls to {transferFrom}. This allows applications to reconstruct the allowance for all accounts just by listening to said events. Other implementations of the EIP may not emit these events, as it isn't required by the specification. Finally, the non-standard {decreaseAllowance} and {increaseAllowance} functions have been added to mitigate the well-known issues around setting allowances. See {IERC20-approve}.",
     "events": {

package/build/contracts/ERC20WithTokenInfo.json

@@ -379,7 +379,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.143Z",
+  "updatedAt": "2023-08-14T13:02:43.966Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Using abstract contract instead of interfaces because old solidity      does not support interface inheriting other interfaces solhint-disable-next-line no-empty-blocks",

package/build/contracts/ERC777Helper.json

@@ -3270,7 +3270,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.151Z",
+  "updatedAt": "2023-08-14T13:02:43.975Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ERC777RecipientDrainingGas.json

@@ -10118,7 +10118,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.292Z",
+  "updatedAt": "2023-08-14T13:02:44.147Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/ERC777RecipientReverting.json

@@ -10227,7 +10227,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.295Z",
+  "updatedAt": "2023-08-14T13:02:44.151Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/EnumerableSet.json

@@ -7369,7 +7369,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.989Z",
+  "updatedAt": "2023-08-14T13:02:43.784Z",
   "devdoc": {
     "details": "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. ====",
     "kind": "dev",

package/build/contracts/EventsEmitter.json

@@ -398,7 +398,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.152Z",
+  "updatedAt": "2023-08-14T13:02:43.977Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "A library used for emitting missing and unaccessable events.",

package/build/contracts/ExclusiveInflowTestApp.json

@@ -20846,7 +20846,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.179Z",
+  "updatedAt": "2023-08-14T13:02:44.008Z",
   "devdoc": {
     "details": "This is a CFA SuperApp that maintains at most one inflow from a sender at any moment. This can test the deposit credit logic in the deleteFlow as a recipient.",
     "kind": "dev",

package/build/contracts/FixedSizeData.json

@@ -1841,7 +1841,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.153Z",
+  "updatedAt": "2023-08-14T13:02:43.978Z",
   "devdoc": {
     "author": "Superfluid When using solidity dynamic array, first word is used to store the length of the array. For use cases that the length doesn't change, it is better to use a fixed size data premitive. To use this library: - The pointer to the storage is `slot`, the user could use `keccak256(abi.encode(...))`   scheme to create collision-free slot ID for locating the data. - To load data, or erase data and get all gas refund, data length is always required.",
     "kind": "dev",

package/build/contracts/FlowExchangeTestApp.json

@@ -21477,7 +21477,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.187Z",
+  "updatedAt": "2023-08-14T13:02:44.017Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/FlowNFTBase.json

@@ -11506,7 +11506,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.605Z",
+  "updatedAt": "2023-08-14T13:02:44.532Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract inherits from IFlowNFTBase which inherits from IERC721Metadata and holds shared storage and functions for the two NFT contracts. This contract is upgradeable and it inherits from our own ad-hoc UUPSProxiable contract which allows. NOTE: the storage gap allows us to add an additional 16 storage variables to this contract without breaking child COFNFT or CIFNFT storage.",

package/build/contracts/FlowOperatorDefinitions.json

@@ -6654,7 +6654,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.120Z",
+  "updatedAt": "2023-08-14T13:02:43.938Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ForwarderBase.json

@@ -1391,7 +1391,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.690Z",
+  "updatedAt": "2023-08-14T13:02:44.637Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/FullUpgradableSuperTokenProxy.json

@@ -1498,7 +1498,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.610Z",
+  "updatedAt": "2023-08-14T13:02:44.538Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/IAccessControl.json

@@ -1036,7 +1036,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.923Z",
+  "updatedAt": "2023-08-14T13:02:43.721Z",
   "devdoc": {
     "details": "External interface of AccessControl declared to support ERC165 detection.",
     "events": {

package/build/contracts/IAccessControlEnumerable.json

@@ -522,7 +522,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.924Z",
+  "updatedAt": "2023-08-14T13:02:43.722Z",
   "devdoc": {
     "details": "External interface of AccessControlEnumerable declared to support ERC165 detection.",
     "events": {

package/build/contracts/IConstantFlowAgreementV1.json

@@ -6234,7 +6234,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.109Z",
+  "updatedAt": "2023-08-14T13:02:43.925Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/contracts/IConstantInflowNFT.json

@@ -839,7 +839,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.128Z",
+  "updatedAt": "2023-08-14T13:02:43.947Z",
   "devdoc": {
     "events": {
       "Approval(address,address,uint256)": {

package/build/contracts/IConstantOutflowNFT.json

@@ -1208,7 +1208,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.128Z",
+  "updatedAt": "2023-08-14T13:02:43.947Z",
   "devdoc": {
     "events": {
       "Approval(address,address,uint256)": {

package/build/contracts/IDAv1Forwarder.json

@@ -27559,7 +27559,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.692Z",
+  "updatedAt": "2023-08-14T13:02:44.640Z",
   "devdoc": {
     "author": "Superfluid The IDAv1Forwarder contract provides an easy to use interface to InstantDistributionAgreementV1 specific functionality of Super Tokens. Instances of this contract can operate on the protocol only if configured as \"trusted forwarder\" by protocol governance.",
     "kind": "dev",

package/build/contracts/IDAv1ForwarderDeployerLibrary.json

@@ -16561,7 +16561,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.729Z",
+  "updatedAt": "2023-08-14T13:02:44.686Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/contracts/IDAv1Library.json

@@ -18022,7 +18022,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.064Z",
+  "updatedAt": "2023-08-14T13:02:43.872Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Set a variable of type `InitData` in the contract, then call this library's functions directly `initData.functionName()`.",

package/build/contracts/IERC165.json

@@ -177,7 +177,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.970Z",
+  "updatedAt": "2023-08-14T13:02:43.763Z",
   "devdoc": {
     "details": "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}.",
     "kind": "dev",

package/build/contracts/IERC1820Implementer.json

@@ -210,7 +210,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.970Z",
+  "updatedAt": "2023-08-14T13:02:43.763Z",
   "devdoc": {
     "details": "Interface for an ERC1820 implementer, as defined in the https://eips.ethereum.org/EIPS/eip-1820#interface-implementation-erc1820implementerinterface[EIP]. Used by contracts that will be registered as implementers in the {IERC1820Registry}.",
     "kind": "dev",

package/build/contracts/IERC1820Registry.json

@@ -1286,7 +1286,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.970Z",
+  "updatedAt": "2023-08-14T13:02:43.764Z",
   "devdoc": {
     "details": "Interface of the global ERC1820 Registry, as defined in the https://eips.ethereum.org/EIPS/eip-1820[EIP]. Accounts may register implementers for interfaces in this registry, as well as query support. Implementers may be shared by multiple accounts, and can also implement more than a single interface for each account. Contracts can implement interfaces for themselves, but externally-owned accounts (EOA) must delegate this to a contract. {IERC165} interfaces can also be queried via the registry. For an in-depth explanation and source code analysis, see the EIP text.",
     "kind": "dev",

package/build/contracts/IERC20.json

@@ -1116,7 +1116,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.941Z",
+  "updatedAt": "2023-08-14T13:02:43.747Z",
   "devdoc": {
     "details": "Interface of the ERC20 standard as defined in the EIP.",
     "events": {

package/build/contracts/IERC20Metadata.json

@@ -506,7 +506,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.942Z",
+  "updatedAt": "2023-08-14T13:02:43.748Z",
   "devdoc": {
     "details": "Interface for the optional metadata functions from the ERC20 standard. _Available since v4.1._",
     "events": {

package/build/contracts/IERC20Permit.json

@@ -520,7 +520,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.942Z",
+  "updatedAt": "2023-08-14T13:02:43.749Z",
   "devdoc": {
     "details": "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.",
     "kind": "dev",

package/build/contracts/IERC721.json

@@ -1654,7 +1654,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.945Z",
+  "updatedAt": "2023-08-14T13:02:43.752Z",
   "devdoc": {
     "details": "Required interface of an ERC721 compliant contract.",
     "events": {

package/build/contracts/IERC721Metadata.json

@@ -646,7 +646,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.954Z",
+  "updatedAt": "2023-08-14T13:02:43.753Z",
   "devdoc": {
     "details": "See https://eips.ethereum.org/EIPS/eip-721",
     "events": {

package/build/contracts/IERC777.json

@@ -2300,7 +2300,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.955Z",
+  "updatedAt": "2023-08-14T13:02:43.754Z",
   "devdoc": {
     "details": "Interface of the ERC777Token standard as defined in the EIP. This contract uses the https://eips.ethereum.org/EIPS/eip-1820[ERC1820 registry standard] to let token holders and recipients react to token movements by using setting implementers for the associated interfaces in said registry. See {IERC1820Registry} and {ERC1820Implementer}.",
     "events": {

package/build/contracts/IERC777Recipient.json

@@ -306,7 +306,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.956Z",
+  "updatedAt": "2023-08-14T13:02:43.755Z",
   "devdoc": {
     "details": "Interface of the ERC777TokensRecipient standard as defined in the EIP. Accounts can be notified of {IERC777} tokens being sent to them by having a contract implement this interface (contract holders can be their own implementer) and registering it on the https://eips.ethereum.org/EIPS/eip-1820[ERC1820 global registry]. See {IERC1820Registry} and {ERC1820Implementer}.",
     "kind": "dev",

package/build/contracts/IERC777Sender.json

@@ -306,7 +306,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:51.956Z",
+  "updatedAt": "2023-08-14T13:02:43.756Z",
   "devdoc": {
     "details": "Interface of the ERC777TokensSender standard as defined in the EIP. {IERC777} Token holders can be notified of operations performed on their tokens by having a contract implement this interface (contract holders can be their own implementer) and registering it on the https://eips.ethereum.org/EIPS/eip-1820[ERC1820 global registry]. See {IERC1820Registry} and {ERC1820Implementer}.",
     "kind": "dev",

package/build/contracts/IFlowNFTBase.json

@@ -1318,7 +1318,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.129Z",
+  "updatedAt": "2023-08-14T13:02:43.948Z",
   "devdoc": {
     "events": {
       "Approval(address,address,uint256)": {

package/build/contracts/IInstantDistributionAgreementV1.json

@@ -5898,7 +5898,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.15",
-  "updatedAt": "2023-08-12T11:30:52.112Z",
+  "updatedAt": "2023-08-14T13:02:43.928Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {