@superfluid-finance/ethereum-contracts 1.0.1-dev.626581d.0 → 1.0.1-dev.921e7d4.0

package/build/contracts/AccessControl.json

@@ -7554,7 +7554,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.987Z",
+  "updatedAt": "2022-03-08T15:41:48.553Z",
   "devdoc": {
     "details": "Contract module that allows children to implement role-based access control mechanisms. 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: ``` 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}: ``` 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.",
     "events": {

package/build/contracts/Address.json

@@ -8088,7 +8088,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.039Z",
+  "updatedAt": "2022-03-08T15:41:48.595Z",
   "devdoc": {
     "details": "Collection of functions related to the address type",
     "kind": "dev",

package/build/contracts/AgreementBase.json

@@ -1562,7 +1562,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.092Z",
+  "updatedAt": "2022-03-08T15:41:48.634Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "The Superfluid agreement base boilerplate contract",

package/build/contracts/AgreementLibrary.json

@@ -14154,7 +14154,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.093Z",
+  "updatedAt": "2022-03-08T15:41:48.635Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Helper library for building super agreement",

package/build/contracts/BaseRelayRecipient.json

@@ -1130,7 +1130,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:04.019Z",
+  "updatedAt": "2022-03-08T15:41:49.357Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/contracts/BatchLiquidator.json

@@ -3516,7 +3516,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.984Z",
+  "updatedAt": "2022-03-08T15:41:49.326Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/BatchOperation.json

@@ -10432,7 +10432,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.241Z",
+  "updatedAt": "2022-03-08T15:41:48.745Z",
   "devdoc": {
     "details": "Batch operation library",
     "kind": "dev",

package/build/contracts/CFAv1Library.json

@@ -22236,7 +22236,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.201Z",
+  "updatedAt": "2022-03-08T15:41:48.715Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/CallUtils.json

@@ -3317,7 +3317,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.287Z",
+  "updatedAt": "2022-03-08T15:41:48.780Z",
   "devdoc": {
     "details": "Call utilities that is absent from the OpenZeppelin",
     "kind": "dev",

package/build/contracts/ClosingOnUpdateFlowTestApp.json

@@ -30185,7 +30185,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.316Z",
+  "updatedAt": "2022-03-08T15:41:48.802Z",
   "devdoc": {
     "details": "This is CFA SuperApp that closes an updated flow.",
     "kind": "dev",

package/build/contracts/ConstantFlowAgreementV1.json

@@ -79198,7 +79198,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.103Z",
+  "updatedAt": "2022-03-08T15:41:48.641Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "The ConstantFlowAgreementV1 implementation NOTE: - Please read IConstantFlowAgreementV1 for implementation notes. - For some deeper technical notes, please visit protocol-monorepo wiki area.",

package/build/contracts/Context.json

@@ -556,7 +556,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.044Z",
+  "updatedAt": "2022-03-08T15:41:48.598Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/ContextDefinitions.json

@@ -10432,7 +10432,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.247Z",
+  "updatedAt": "2022-03-08T15:41:48.748Z",
   "devdoc": {
     "details": "Context definitions library",
     "kind": "dev",

package/build/contracts/Create2.json

@@ -3237,7 +3237,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.044Z",
+  "updatedAt": "2022-03-08T15:41:48.599Z",
   "devdoc": {
     "details": "Helper to make usage of the `CREATE2` EVM opcode easier and safer. `CREATE2` can be used to compute in advance the address where a smart contract will be deployed, which allows for interesting new mechanisms known as 'counterfactual interactions'. See the https://eips.ethereum.org/EIPS/eip-1014#motivation[EIP] for more information.",
     "kind": "dev",

package/build/contracts/CustomSuperTokenBase.json

@@ -282,7 +282,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.241Z",
+  "updatedAt": "2022-03-08T15:41:48.744Z",
   "devdoc": {
     "details": "Custom super token base contract NOTE: - Because of how solidity is layouting its storages variables and custom   super token inherits the Super Token standard implementation, so it is   required that the custom token proxy would need to pad its implementation   with reserved storages 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

@@ -1425,7 +1425,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.993Z",
+  "updatedAt": "2022-03-08T15:41:48.558Z",
   "devdoc": {
     "details": "Implementation of the {IERC165} interface. Contracts may inherit from this and call {_registerInterface} to declare their support of an interface.",
     "kind": "dev",

package/build/contracts/ERC1820Implementer.json

@@ -1604,7 +1604,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.994Z",
+  "updatedAt": "2022-03-08T15:41:48.558Z",
   "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.",
     "kind": "dev",

package/build/contracts/ERC20.json

@@ -13558,7 +13558,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.007Z",
+  "updatedAt": "2022-03-08T15:41:48.569Z",
   "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.zeppelin.solutions/t/how-to-implement-erc20-supply-mechanisms/226[How to implement supply mechanisms]. We have followed general OpenZeppelin guidelines: functions revert instead of 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}.",
     "kind": "dev",

package/build/contracts/ERC20WithTokenInfo.json

@@ -534,7 +534,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.278Z",
+  "updatedAt": "2022-03-08T15:41:48.772Z",
   "devdoc": {
     "details": "Interface for ERC20 token with token info NOTE: Using abstract contract instead of interfaces because old solidity does not support interface inheriting other interfaces solhint-disable-next-line no-empty-blocks",
     "kind": "dev",

package/build/contracts/ERC721.json

@@ -25682,7 +25682,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.019Z",
+  "updatedAt": "2022-03-08T15:41:48.579Z",
   "devdoc": {
     "details": "see https://eips.ethereum.org/EIPS/eip-721",
     "kind": "dev",

package/build/contracts/ERC777Helper.json

@@ -6319,7 +6319,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.289Z",
+  "updatedAt": "2022-03-08T15:41:48.781Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/ERC777RecipientDrainingGas.json

@@ -16104,7 +16104,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.454Z",
+  "updatedAt": "2022-03-08T15:41:48.905Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/ERC777RecipientReverting.json

@@ -16090,7 +16090,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.460Z",
+  "updatedAt": "2022-03-08T15:41:48.911Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/EnumerableMap.json

@@ -14492,7 +14492,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.046Z",
+  "updatedAt": "2022-03-08T15:41:48.600Z",
   "devdoc": {
     "details": "Library for managing an enumerable variant of Solidity's https://solidity.readthedocs.io/en/latest/types.html#mapping-types[`mapping`] type. Maps have the following properties: - Entries are added, removed, and checked for existence in constant time (O(1)). - Entries are enumerated in O(n). No guarantees are made on the ordering. ``` contract Example {     // Add the library methods     using EnumerableMap for EnumerableMap.UintToAddressMap;     // Declare a set state variable     EnumerableMap.UintToAddressMap private myMap; } ``` As of v3.0.0, only maps of type `uint256 -> address` (`UintToAddressMap`) are supported.",
     "kind": "dev",

package/build/contracts/EnumerableSet.json

@@ -12454,7 +12454,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.059Z",
+  "updatedAt": "2022-03-08T15:41:48.609Z",
   "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. ``` 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.",
     "kind": "dev",

package/build/contracts/ExclusiveInflowTestApp.json

@@ -30444,7 +30444,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.329Z",
+  "updatedAt": "2022-03-08T15:41:48.813Z",
   "devdoc": {
     "details": "This is CFA SuperApp that maintains at most one inflw from a sender at any moment. This can test the deposit allowance logic in the deleteFlow as a recipient.",
     "kind": "dev",

package/build/contracts/FixedSizeData.json

@@ -3570,7 +3570,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.292Z",
+  "updatedAt": "2022-03-08T15:41:48.784Z",
   "devdoc": {
     "details": "Utilities for fixed size data in storage 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

@@ -30962,7 +30962,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.343Z",
+  "updatedAt": "2022-03-08T15:41:48.823Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/FullUpgradableSuperTokenProxy.json

@@ -2140,7 +2140,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.898Z",
+  "updatedAt": "2022-03-08T15:41:49.309Z",
   "devdoc": {
     "details": "Full upgradable super token proxy",
     "kind": "dev",

package/build/contracts/IConstantFlowAgreementV1.json

@@ -4988,7 +4988,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.233Z",
+  "updatedAt": "2022-03-08T15:41:48.739Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Superfluid's constant flow agreement interface",

package/build/contracts/IERC165.json

@@ -332,7 +332,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.995Z",
+  "updatedAt": "2022-03-08T15:41:48.559Z",
   "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

@@ -391,7 +391,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.995Z",
+  "updatedAt": "2022-03-08T15:41:48.559Z",
   "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

@@ -2374,7 +2374,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:02.995Z",
+  "updatedAt": "2022-03-08T15:41:48.560Z",
   "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

@@ -2050,7 +2050,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.014Z",
+  "updatedAt": "2022-03-08T15:41:48.575Z",
   "devdoc": {
     "details": "Interface of the ERC20 standard as defined in the EIP.",
     "events": {

package/build/contracts/IERC721.json

@@ -3051,7 +3051,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.032Z",
+  "updatedAt": "2022-03-08T15:41:48.589Z",
   "devdoc": {
     "details": "Required interface of an ERC721 compliant contract.",
     "events": {

package/build/contracts/IERC721Enumerable.json

@@ -1099,7 +1099,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.034Z",
+  "updatedAt": "2022-03-08T15:41:48.590Z",
   "devdoc": {
     "details": "See https://eips.ethereum.org/EIPS/eip-721",
     "kind": "dev",

package/build/contracts/IERC721Metadata.json

@@ -985,7 +985,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.035Z",
+  "updatedAt": "2022-03-08T15:41:48.591Z",
   "devdoc": {
     "details": "See https://eips.ethereum.org/EIPS/eip-721",
     "kind": "dev",

package/build/contracts/IERC721Receiver.json

@@ -507,7 +507,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.035Z",
+  "updatedAt": "2022-03-08T15:41:48.592Z",
   "devdoc": {
     "details": "Interface for any contract that wants to support safeTransfers from ERC721 asset contracts.",
     "kind": "dev",

package/build/contracts/IERC777.json

@@ -4210,7 +4210,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.036Z",
+  "updatedAt": "2022-03-08T15:41:48.592Z",
   "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}.",
     "kind": "dev",

package/build/contracts/IERC777Recipient.json

@@ -568,7 +568,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.038Z",
+  "updatedAt": "2022-03-08T15:41:48.594Z",
   "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

@@ -568,7 +568,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.039Z",
+  "updatedAt": "2022-03-08T15:41:48.594Z",
   "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/IInstantDistributionAgreementV1.json

@@ -9804,7 +9804,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.235Z",
+  "updatedAt": "2022-03-08T15:41:48.741Z",
   "devdoc": {
     "author": "Superfluid Notes:   - A publisher can create as many as indeces as possibily identifiable with `indexId`.     - `indexId` is deliberately limited to 32 bits, to avoid the chance for sha-3 collision.       Despite knowing sha-3 collision is only theoratical.   - A publisher can create subscription to an index for any subscriber.   - A subscription consists of:     - The index it subscribes to.     - Number of units subscribed.   - An index consists of:     - Current value as `uint128 indexValue`.     - Total units of the approved subscriptions as `uint128 totalUnitsApproved`.     - Total units of the non approved subscription as `uint128 totalUnitsPending`.   - A publisher can update index with new value that doesn't decrease.   - A publisher can update subscription with any number of units.   - A publisher or a subscriber can delete subscription and reset units to zero.   - A subscriber must approve the index in order to receive distributions from the publisher     each time the index is updated.     - The amount distributed is $$\\Delta{index} * units$$   - Distributions to a non approved subscription stays in the publisher's deposit until:     - the subscriber approve the subscription (side effect),     - the publisher update the subscription (side effect),     - the subscriber delete the subscription even if it is never approved (side effect),     - or the subscriber can explicitly claim them.",
     "kind": "dev",

package/build/contracts/IMaticBridgedNativeSuperToken.json

@@ -2513,7 +2513,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.279Z",
+  "updatedAt": "2022-03-08T15:41:48.773Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Matic Bridged Native SuperToken full interface",

package/build/contracts/IMaticBridgedNativeSuperTokenCustom.json

@@ -944,7 +944,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.280Z",
+  "updatedAt": "2022-03-08T15:41:48.774Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Functionality specific for Matic Bridged Native Super Tokens",

package/build/contracts/IMultiSigWallet.json

@@ -414,7 +414,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.240Z",
+  "updatedAt": "2022-03-08T15:41:48.744Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/INativeSuperToken.json

@@ -2389,7 +2389,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.281Z",
+  "updatedAt": "2022-03-08T15:41:48.775Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Native SuperToken full interface",

package/build/contracts/INativeSuperTokenCustom.json

@@ -820,7 +820,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.283Z",
+  "updatedAt": "2022-03-08T15:41:48.776Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Native SuperToken custom token functions",

package/build/contracts/IRelayRecipient.json

@@ -473,7 +473,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.286Z",
+  "updatedAt": "2022-03-08T15:41:48.779Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/contracts/IResolver.json

@@ -693,7 +693,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.287Z",
+  "updatedAt": "2022-03-08T15:41:48.779Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Abstraction for a address resolver contract",

package/build/contracts/ISETH.json

@@ -3656,7 +3656,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.283Z",
+  "updatedAt": "2022-03-08T15:41:48.776Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Super ETH (SETH) full interface",

package/build/contracts/ISETHCustom.json

@@ -2149,7 +2149,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.285Z",
+  "updatedAt": "2022-03-08T15:41:48.778Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Super ETH (SETH) custom token functions",

package/build/contracts/ISuperAgreement.json

@@ -758,7 +758,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.261Z",
+  "updatedAt": "2022-03-08T15:41:48.759Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ISuperApp.json

@@ -2944,7 +2944,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.262Z",
+  "updatedAt": "2022-03-08T15:41:48.759Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ISuperToken.json

@@ -10261,7 +10261,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.264Z",
+  "updatedAt": "2022-03-08T15:41:48.760Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/contracts/ISuperTokenFactory.json

@@ -1944,7 +1944,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.268Z",
+  "updatedAt": "2022-03-08T15:41:48.764Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/contracts/ISuperfluid.json

@@ -11073,7 +11073,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.269Z",
+  "updatedAt": "2022-03-08T15:41:48.765Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Superfluid host interface. It is the central contract of the system where super agreement, super app and super token features are connected together. The superfluid host contract is also the entry point for the protocol users, where batch call and meta transaction are provided for UX improvements.",

package/build/contracts/ISuperfluidGovernance.json

@@ -2869,7 +2869,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.274Z",
+  "updatedAt": "2022-03-08T15:41:48.769Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Superfluid's Governance interface",

package/build/contracts/ISuperfluidToken.json

@@ -7171,7 +7171,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-08T12:06:03.275Z",
+  "updatedAt": "2022-03-08T15:41:48.770Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {