@superfluid-finance/ethereum-contracts 1.0.1-dev.d7224df.0 → 1.0.1-dev.fbe38e2.0

package/build/contracts/BatchOperation.json

@@ -10399,7 +10399,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.027Z",
+  "updatedAt": "2022-03-16T15:02:42.155Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/CFAv1Library.json

@@ -22431,7 +22431,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.979Z",
+  "updatedAt": "2022-03-16T15:02:42.098Z",
   "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

@@ -4929,7 +4929,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.064Z",
+  "updatedAt": "2022-03-16T15:02:42.198Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ClosingOnUpdateFlowTestApp.json

@@ -31588,7 +31588,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.088Z",
+  "updatedAt": "2022-03-16T15:02:42.226Z",
   "devdoc": {
     "details": "This is CFA SuperApp that closes an updated flow.",
     "kind": "dev",

package/build/contracts/ConstantFlowAgreementV1.json

@@ -25034,7 +25034,7 @@
           17519,
           6924,
           18335,
-          36875,
+          36935,
           2593
         ],
         "name": "ConstantFlowAgreementV1",
@@ -60293,7 +60293,7 @@
           17519,
           6924,
           18335,
-          36875,
+          36935,
           2593
         ],
         "name": "ConstantFlowAgreementV1",
@@ -95199,7 +95199,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.884Z",
+  "updatedAt": "2022-03-16T15:02:41.988Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Please read IConstantFlowAgreementV1 for implementation notes.For more technical notes, please visit protocol-monorepo wiki area.",

package/build/contracts/Context.json

@@ -493,7 +493,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.856Z",
+  "updatedAt": "2022-03-16T15:02:41.956Z",
   "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

@@ -10399,7 +10399,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.031Z",
+  "updatedAt": "2022-03-16T15:02:42.159Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/Create2.json

@@ -3231,7 +3231,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.857Z",
+  "updatedAt": "2022-03-16T15:02:41.956Z",
   "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

@@ -285,7 +285,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.027Z",
+  "updatedAt": "2022-03-16T15:02:42.154Z",
   "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

@@ -603,7 +603,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.861Z",
+  "updatedAt": "2022-03-16T15:02:41.961Z",
   "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

@@ -1887,7 +1887,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.861Z",
+  "updatedAt": "2022-03-16T15:02:41.961Z",
   "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

@@ -20792,7 +20792,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.818Z",
+  "updatedAt": "2022-03-16T15:02:41.910Z",
   "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 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}.",
     "kind": "dev",

package/build/contracts/ERC20WithTokenInfo.json

@@ -518,7 +518,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.056Z",
+  "updatedAt": "2022-03-16T15:02:42.189Z",
   "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/ERC721.json

@@ -33160,7 +33160,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.831Z",
+  "updatedAt": "2022-03-16T15:02:41.925Z",
   "devdoc": {
     "details": "Implementation of https://eips.ethereum.org/EIPS/eip-721[ERC721] Non-Fungible Token Standard, including the Metadata extension, but not including the Enumerable extension, which is available separately as {ERC721Enumerable}.",
     "kind": "dev",

package/build/contracts/ERC777Helper.json

@@ -6249,7 +6249,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.066Z",
+  "updatedAt": "2022-03-16T15:02:42.200Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/contracts/ERC777RecipientDrainingGas.json

@@ -17678,7 +17678,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.206Z",
+  "updatedAt": "2022-03-16T15:02:42.363Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/ERC777RecipientReverting.json

@@ -17787,7 +17787,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.212Z",
+  "updatedAt": "2022-03-16T15:02:42.370Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/contracts/EnumerableSet.json

@@ -14101,7 +14101,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:12.871Z",
+  "updatedAt": "2022-03-16T15:02:41.973Z",
   "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

@@ -31742,7 +31742,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.099Z",
+  "updatedAt": "2022-03-16T15:02:42.239Z",
   "devdoc": {
     "details": "This is a CFA SuperApp that maintains at most one inflow 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

@@ -3659,7 +3659,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.069Z",
+  "updatedAt": "2022-03-16T15:02:42.203Z",
   "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

@@ -32373,7 +32373,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.4",
-  "updatedAt": "2022-03-14T21:09:13.112Z",
+  "updatedAt": "2022-03-16T15:02:42.254Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},