@superfluid-finance/ethereum-contracts 1.13.1-dev.8ac8ca4.0 → 1.13.1-dev.abd1497.0

package/build/truffle/AccessControl.json

@@ -4202,7 +4202,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.420Z",
+  "updatedAt": "2025-06-30T11:42:57.312Z",
   "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/truffle/AccessControlEnumerable.json

@@ -1792,7 +1792,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.422Z",
+  "updatedAt": "2025-06-30T11:42:57.314Z",
   "devdoc": {
     "details": "Extension of {AccessControl} that allows enumerating the members of each role.",
     "events": {

package/build/truffle/AdditionalMonetaryTypeHelpers.json

@@ -31332,7 +31332,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.465Z",
+  "updatedAt": "2025-06-30T11:42:57.377Z",
   "devdoc": {
     "details": "Additional helper functions for the monetary types Note that due to solidity current limitations, operators for mixed user defined value types are not supported, hence the need of this library. Read more at: https://github.com/ethereum/solidity/issues/11969#issuecomment-1448445474",
     "kind": "dev",

package/build/truffle/Address.json

@@ -4390,7 +4390,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.449Z",
+  "updatedAt": "2025-06-30T11:42:57.350Z",
   "devdoc": {
     "details": "Collection of functions related to the address type",
     "kind": "dev",

package/build/truffle/AgreementBase.json

@@ -833,7 +833,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.478Z",
+  "updatedAt": "2025-06-30T11:42:57.398Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/truffle/AgreementLibrary.json

@@ -7332,7 +7332,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.478Z",
+  "updatedAt": "2025-06-30T11:42:57.398Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "Helper library for building super agreement",

package/build/truffle/BaseRelayRecipient.json

@@ -640,7 +640,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.595Z",
+  "updatedAt": "2025-06-30T11:42:57.557Z",
   "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/truffle/BatchLiquidator.json

@@ -11411,7 +11411,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.856Z",
+  "updatedAt": "2025-06-30T11:42:57.899Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract allows to delete multiple flows in a single transaction.",

package/build/truffle/BatchOperation.json

@@ -6905,7 +6905,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.578Z",
+  "updatedAt": "2025-06-30T11:42:57.537Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/BeaconProxiable.json

@@ -255,7 +255,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.854Z",
+  "updatedAt": "2025-06-30T11:42:57.896Z",
   "devdoc": {
     "events": {
       "Initialized(uint8)": {

package/build/truffle/BeaconProxy.json

@@ -4505,7 +4505,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.432Z",
+  "updatedAt": "2025-06-30T11:42:57.324Z",
   "devdoc": {
     "details": "This contract implements a proxy that gets the implementation address for each call from an {UpgradeableBeacon}. The beacon address is stored in storage slot `uint256(keccak256('eip1967.proxy.beacon')) - 1`, so that it doesn't conflict with the storage layout of the implementation behind the proxy. _Available since v3.4._",
     "events": {

package/build/truffle/CFASuperAppBase.json

@@ -7956,7 +7956,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.551Z",
+  "updatedAt": "2025-06-30T11:42:57.499Z",
   "devdoc": {
     "author": "Superfluid",
     "details": "This contract provides a more convenient API for implementing CFA callbacks. It allows to write more concise and readable SuperApps when the full flexibility of the low-level agreement callbacks isn't needed. The API is tailored for the most common use cases, with the \"beforeX\" and \"afterX\" callbacks being abstrated into a single \"onX\" callback for create|update|delete flows. For use cases requiring more flexibility (specifically if more data needs to be provided by the before callbacks) it's recommended to implement the low-level callbacks directly instead of using this base contract.",

package/build/truffle/CFAv1Forwarder.json

@@ -23671,7 +23671,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.859Z",
+  "updatedAt": "2025-06-30T11:42:57.902Z",
   "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/truffle/CFAv1ForwarderDeployerLibrary.json

@@ -18442,7 +18442,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.884Z",
+  "updatedAt": "2025-06-30T11:42:57.937Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/CallUtils.json

@@ -2592,7 +2592,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.595Z",
+  "updatedAt": "2025-06-30T11:42:57.558Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/CallbackUtils.json

@@ -1504,7 +1504,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.596Z",
+  "updatedAt": "2025-06-30T11:42:57.558Z",
   "devdoc": {
     "details": "## Problem Statement When calling an untrusted external callback (or hook), gas limit is usually provided to prevent grief attack from them. However, such gas limits are nested. From the callback invoking site, one might need to differentiate the cases between the outer-layer induced out-of-gas vs. the callback resulted out-of-gas. This library solves such challenge by safely marking the second case with an explicit flag of insufficient-callback-gas-provided. In order to use this library, one must first understand the concept of callback gas limit zones. ## Definitions: callback gas limit zones +---------------------------+--------------+---------------------+ | insufficient-callback-gas | transitional | out-of-callback-gas | +---------------------------+--------------+---------------------+ - insufficient-callback-gas zone   This zone includes all outer gas limits that are below callback gas limit. The invariance of   this zone is that calling the callback shall return with the insufficient-callback-gas-provided   set to true if more gas is needed to execute the callback. - out-of-callback-gas zone   Within this continuous zone, the invariance is that calling the callback shall never return   with the insufficient-callback-gas-provided flag set to true. - transitional zone   Between the insufficient-callback-gas zone to the out-of-callback-gas zone, there is a zone of   unspecified size where insufficient-callback-gas-provided may be set to true. This is due the   factors of EIP-150 Magic N and callback setup overhead. ## EIP-150 Magic N \"If a call asks for more gas than the maximum allowed amount (i.e. the total amount of gas remaining in the parent after subtracting the gas cost of the call and memory expansion), do not return an OOG error; instead, if a call asks for more gas than all but one 64th of the maximum allowed amount, call with all but one 64th of the maximum allowed amount of gas (this is equivalent to a version of EIP-90 plus EIP-114). CREATE only provides all but one 64th of the parent gas to the child call.\" Another article about this topic: https://medium.com/%40wighawag/ethereum-the-concept-of-gas-and-its-dangers-28d0eb809bb2",
     "kind": "dev",

package/build/truffle/ClosingOnUpdateFlowTestApp.json

@@ -22434,7 +22434,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.610Z",
+  "updatedAt": "2025-06-30T11:42:57.574Z",
   "devdoc": {
     "details": "This is CFA SuperApp that closes an updated flow.",
     "kind": "dev",

package/build/truffle/ConstantFlowAgreementV1.json

@@ -83932,7 +83932,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.480Z",
+  "updatedAt": "2025-06-30T11:42:57.401Z",
   "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/truffle/Context.json

@@ -341,7 +341,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.450Z",
+  "updatedAt": "2025-06-30T11:42:57.353Z",
   "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/truffle/ContextDefinitions.json

@@ -6905,7 +6905,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.579Z",
+  "updatedAt": "2025-06-30T11:42:57.539Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/Counters.json

@@ -864,7 +864,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.450Z",
+  "updatedAt": "2025-06-30T11:42:57.353Z",
   "devdoc": {
     "author": "Matt Condon (@shrugs)",
     "details": "Provides counters that can only be incremented, decremented or reset. This can be used e.g. to track the number of elements in a mapping, issuing ERC721 ids, or counting request ids. Include with `using Counters for Counters.Counter;`",

package/build/truffle/CustomSuperTokenBase.json

@@ -149,7 +149,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.578Z",
+  "updatedAt": "2025-06-30T11:42:57.537Z",
   "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/truffle/ECDSA.json

@@ -5290,7 +5290,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.452Z",
+  "updatedAt": "2025-06-30T11:42:57.356Z",
   "devdoc": {
     "details": "Elliptic Curve Digital Signature Algorithm (ECDSA) operations. These functions can be used to verify that a message was signed by the holder of the private keys of a given address.",
     "kind": "dev",

package/build/truffle/EIP712.json

@@ -2752,7 +2752,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.454Z",
+  "updatedAt": "2025-06-30T11:42:57.359Z",
   "devdoc": {
     "custom:oz-upgrades-unsafe-allow": "state-variable-immutable state-variable-assignment",
     "details": "https://eips.ethereum.org/EIPS/eip-712[EIP 712] is a standard for hashing and signing of typed structured data. The encoding specified in the EIP is very generic, and such a generic implementation in Solidity is not feasible, thus this contract does not implement the encoding itself. Protocols need to implement the type-specific encoding they need in their contracts using a combination of `abi.encode` and `keccak256`. This contract implements the EIP 712 domain separator ({_domainSeparatorV4}) that is used as part of the encoding scheme, and the final step of the encoding to obtain the message digest that is then signed via ECDSA ({_hashTypedDataV4}). The implementation of the domain separator was designed to be as efficient as possible while still properly updating the chain id to protect against replay attacks on an eventual fork of the chain. NOTE: This contract implements the version of the encoding known as \"v4\", as implemented by the JSON RPC method https://docs.metamask.io/guide/signing-data.html[`eth_signTypedDataV4` in MetaMask]. NOTE: In the upgradeable version of this contract, the cached values will correspond to the address, and the domain separator of the implementation contract. This will cause the `_domainSeparatorV4` function to always rebuild the separator from the immutable values, which is cheaper than accessing a cached version in cold storage. _Available since v3.4._",

package/build/truffle/ERC165.json

@@ -326,7 +326,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.454Z",
+  "updatedAt": "2025-06-30T11:42:57.359Z",
   "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/truffle/ERC1820Implementer.json

@@ -1275,7 +1275,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.455Z",
+  "updatedAt": "2025-06-30T11:42:57.361Z",
   "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/truffle/ERC1820RegistryCompiled.json

@@ -245,7 +245,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.597Z",
+  "updatedAt": "2025-06-30T11:42:57.559Z",
   "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/truffle/ERC1967Upgrade.json

@@ -3953,7 +3953,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.428Z",
+  "updatedAt": "2025-06-30T11:42:57.320Z",
   "devdoc": {
     "details": "This abstract contract provides getters and event emitting update functions for https://eips.ethereum.org/EIPS/eip-1967[EIP1967] slots. _Available since v4.1._",
     "events": {

package/build/truffle/ERC20.json

@@ -16424,7 +16424,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.438Z",
+  "updatedAt": "2025-06-30T11:42:57.331Z",
   "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/truffle/ERC20Permit.json

@@ -2628,7 +2628,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.445Z",
+  "updatedAt": "2025-06-30T11:42:57.342Z",
   "devdoc": {
     "details": "Implementation 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. _Available since v3.4._",
     "events": {

package/build/truffle/ERC2771Forwarder.json

@@ -4724,7 +4724,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.863Z",
+  "updatedAt": "2025-06-30T11:42:57.909Z",
   "devdoc": {
     "kind": "dev",
     "methods": {

package/build/truffle/ERC777Helper.json

@@ -3281,7 +3281,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.597Z",
+  "updatedAt": "2025-06-30T11:42:57.559Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/ERC777RecipientDrainingGas.json

@@ -10456,7 +10456,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.637Z",
+  "updatedAt": "2025-06-30T11:42:57.608Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/ERC777RecipientReverting.json

@@ -10610,7 +10610,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.639Z",
+  "updatedAt": "2025-06-30T11:42:57.611Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/EnumerableSet.json

@@ -7382,7 +7382,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.464Z",
+  "updatedAt": "2025-06-30T11:42:57.374Z",
   "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/truffle/ExclusiveInflowTestApp.json

@@ -22616,7 +22616,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.614Z",
+  "updatedAt": "2025-06-30T11:42:57.580Z",
   "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/truffle/FixedSizeData.json

@@ -1883,7 +1883,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.598Z",
+  "updatedAt": "2025-06-30T11:42:57.560Z",
   "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/truffle/FlowExchangeTestApp.json

@@ -23504,7 +23504,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.619Z",
+  "updatedAt": "2025-06-30T11:42:57.585Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/FlowOperatorDefinitions.json

@@ -6905,7 +6905,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.581Z",
+  "updatedAt": "2025-06-30T11:42:57.541Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/ForwarderBase.json

@@ -1807,7 +1807,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.864Z",
+  "updatedAt": "2025-06-30T11:42:57.910Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/FullUpgradableSuperTokenProxy.json

@@ -1589,7 +1589,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.801Z",
+  "updatedAt": "2025-06-30T11:42:57.825Z",
   "devdoc": {
     "author": "Superfluid",
     "kind": "dev",

package/build/truffle/GDAv1Forwarder.json

@@ -25768,7 +25768,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.865Z",
+  "updatedAt": "2025-06-30T11:42:57.911Z",
   "devdoc": {
     "author": "Superfluid The GDAv1Forwarder contract provides an easy to use interface to GeneralDistributionAgreementV1 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/truffle/GDAv1ForwarderDeployerLibrary.json

@@ -18442,7 +18442,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.888Z",
+  "updatedAt": "2025-06-30T11:42:57.943Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/GeneralDistributionAgreementV1.json

@@ -93776,7 +93776,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.513Z",
+  "updatedAt": "2025-06-30T11:42:57.445Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/truffle/IAccessControl.json

@@ -1041,7 +1041,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.423Z",
+  "updatedAt": "2025-06-30T11:42:57.314Z",
   "devdoc": {
     "details": "External interface of AccessControl declared to support ERC165 detection.",
     "events": {

package/build/truffle/IAccessControlEnumerable.json

@@ -527,7 +527,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.426Z",
+  "updatedAt": "2025-06-30T11:42:57.318Z",
   "devdoc": {
     "details": "External interface of AccessControlEnumerable declared to support ERC165 detection.",
     "events": {

package/build/truffle/IBeacon.json

@@ -145,7 +145,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.434Z",
+  "updatedAt": "2025-06-30T11:42:57.326Z",
   "devdoc": {
     "details": "This is the interface that {BeaconProxy} expects of its beacon.",
     "kind": "dev",

package/build/truffle/IConstantFlowAgreementV1.json

@@ -6239,7 +6239,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.572Z",
+  "updatedAt": "2025-06-30T11:42:57.530Z",
   "devdoc": {
     "author": "Superfluid",
     "events": {

package/build/truffle/IConstantInflowNFT.json

@@ -28624,7 +28624,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.802Z",
+  "updatedAt": "2025-06-30T11:42:57.826Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/IConstantOutflowNFT.json

@@ -28624,7 +28624,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.808Z",
+  "updatedAt": "2025-06-30T11:42:57.833Z",
   "devdoc": {
     "kind": "dev",
     "methods": {},

package/build/truffle/IERC165.json

@@ -178,7 +178,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.455Z",
+  "updatedAt": "2025-06-30T11:42:57.361Z",
   "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/truffle/IERC1820Implementer.json

@@ -211,7 +211,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.455Z",
+  "updatedAt": "2025-06-30T11:42:57.362Z",
   "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/truffle/IERC1820Registry.json

@@ -1290,7 +1290,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.455Z",
+  "updatedAt": "2025-06-30T11:42:57.362Z",
   "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/truffle/IERC1822Proxiable.json

@@ -144,7 +144,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.427Z",
+  "updatedAt": "2025-06-30T11:42:57.319Z",
   "devdoc": {
     "details": "ERC1822: Universal Upgradeable Proxy Standard (UUPS) documents a method for upgradeability through a simplified proxy whose upgrades are fully controlled by the current implementation.",
     "kind": "dev",

package/build/truffle/IERC1967.json

@@ -301,7 +301,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.427Z",
+  "updatedAt": "2025-06-30T11:42:57.319Z",
   "devdoc": {
     "details": "ERC-1967: Proxy Storage Slots. This interface contains the events defined in the ERC. _Available since v4.8.3._",
     "events": {

package/build/truffle/IERC20.json

@@ -1120,7 +1120,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.445Z",
+  "updatedAt": "2025-06-30T11:42:57.338Z",
   "devdoc": {
     "details": "Interface of the ERC20 standard as defined in the EIP.",
     "events": {

package/build/truffle/IERC20Metadata.json

@@ -510,7 +510,7 @@
   },
   "networks": {},
   "schemaVersion": "3.4.16",
-  "updatedAt": "2025-06-30T11:25:30.446Z",
+  "updatedAt": "2025-06-30T11:42:57.343Z",
   "devdoc": {
     "details": "Interface for the optional metadata functions from the ERC20 standard. _Available since v4.1._",
     "events": {