@xyo-network/solidity - npm Package Compare versions

Comparing version 3.2.0 to 3.2.1

build/contracts/Context.json

@@ -344,3 +344,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.800Z",
+  "updatedAt": "2024-08-30T03:49:41.922Z",
   "devdoc": {
@@ -347,0 +347,0 @@ "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.",

build/contracts/DataStore.json

@@ -861,3 +861,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.804Z",
+  "updatedAt": "2024-08-30T03:49:41.934Z",
   "devdoc": {
@@ -864,0 +864,0 @@ "kind": "dev",

build/contracts/Erc721Store.json

@@ -1354,3 +1354,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.808Z",
+  "updatedAt": "2024-08-30T03:49:41.939Z",
   "devdoc": {
@@ -1357,0 +1357,0 @@ "kind": "dev",

build/contracts/IBurnable.json

@@ -135,3 +135,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.809Z",
+  "updatedAt": "2024-08-30T03:49:41.940Z",
   "devdoc": {
@@ -138,0 +138,0 @@ "kind": "dev",

build/contracts/IBurnableErc20.json

@@ -328,3 +328,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.808Z",
+  "updatedAt": "2024-08-30T03:49:41.939Z",
   "devdoc": {
@@ -331,0 +331,0 @@ "events": {

build/contracts/IDataStore.json

@@ -367,3 +367,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.809Z",
+  "updatedAt": "2024-08-30T03:49:41.940Z",
   "devdoc": {
@@ -370,0 +370,0 @@ "kind": "dev",

build/contracts/IERC165.json

@@ -181,3 +181,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.800Z",
+  "updatedAt": "2024-08-30T03:49:41.922Z",
   "devdoc": {
@@ -184,0 +184,0 @@ "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}.",

build/contracts/IERC20.json

@@ -1123,3 +1123,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.797Z",
+  "updatedAt": "2024-08-30T03:49:41.919Z",
   "devdoc": {
@@ -1126,0 +1126,0 @@ "details": "Interface of the ERC20 standard as defined in the EIP.",

build/contracts/IERC20Metadata.json

@@ -526,3 +526,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.797Z",
+  "updatedAt": "2024-08-30T03:49:41.920Z",
   "devdoc": {
@@ -529,0 +529,0 @@ "details": "Interface for the optional metadata functions from the ERC20 standard.",

build/contracts/IERC20Permit.json

@@ -524,3 +524,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.798Z",
+  "updatedAt": "2024-08-30T03:49:41.920Z",
   "devdoc": {
@@ -527,0 +527,0 @@ "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. ==== Security Considerations There are two important considerations concerning the use of `permit`. The first is that a valid permit signature expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be considered as an intention to spend the allowance in any specific way. The second is that because permits have built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be generally recommended is: ```solidity function doThingWithPermit(..., uint256 value, uint256 deadline, uint8 v, bytes32 r, bytes32 s) public {     try token.permit(msg.sender, address(this), value, deadline, v, r, s) {} catch {}     doThing(..., value); } function doThing(..., uint256 value) public {     token.safeTransferFrom(msg.sender, address(this), value);     ... } ``` Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also {SafeERC20-safeTransferFrom}). Additionally, note that smart contract wallets (such as Argent or Safe) are not able to produce permit signatures, so contracts should have entry points that don't rely on permit.",

build/contracts/IErc20Store.json

@@ -578,3 +578,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.808Z",
+  "updatedAt": "2024-08-30T03:49:41.939Z",
   "devdoc": {
@@ -581,0 +581,0 @@ "kind": "dev",

build/contracts/IErc721Store.json

@@ -613,3 +613,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.808Z",
+  "updatedAt": "2024-08-30T03:49:41.940Z",
   "devdoc": {
@@ -616,0 +616,0 @@ "kind": "dev",

build/contracts/ILockable.json

@@ -169,3 +169,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.809Z",
+  "updatedAt": "2024-08-30T03:49:41.940Z",
   "devdoc": {
@@ -172,0 +172,0 @@ "kind": "dev",

build/contracts/IMintable.json

@@ -612,3 +612,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.809Z",
+  "updatedAt": "2024-08-30T03:49:41.941Z",
   "devdoc": {
@@ -615,0 +615,0 @@ "kind": "dev",

build/contracts/IMintableErc721.json

@@ -521,3 +521,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.809Z",
+  "updatedAt": "2024-08-30T03:49:41.940Z",
   "devdoc": {
@@ -524,0 +524,0 @@ "events": {

build/contracts/IParentable.json

@@ -169,3 +169,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.810Z",
+  "updatedAt": "2024-08-30T03:49:41.941Z",
   "devdoc": {
@@ -172,0 +172,0 @@ "kind": "dev",

build/contracts/IPromises.json

@@ -624,3 +624,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.811Z",
+  "updatedAt": "2024-08-30T03:49:41.942Z",
   "devdoc": {
@@ -627,0 +627,0 @@ "kind": "dev",

build/contracts/IUniGenPair.json

@@ -1364,3 +1364,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.811Z",
+  "updatedAt": "2024-08-30T03:49:41.942Z",
   "devdoc": {
@@ -1367,0 +1367,0 @@ "kind": "dev",

build/contracts/PercentConstants.json

@@ -152,3 +152,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.810Z",
+  "updatedAt": "2024-08-30T03:49:41.941Z",
   "devdoc": {
@@ -155,0 +155,0 @@ "kind": "dev",

build/contracts/Promises.json

@@ -485,3 +485,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.811Z",
+  "updatedAt": "2024-08-30T03:49:41.942Z",
   "devdoc": {
@@ -488,0 +488,0 @@ "kind": "dev",

build/contracts/TimeConstants.json

@@ -444,3 +444,3 @@ {
   "schemaVersion": "3.4.16",
-  "updatedAt": "2024-08-30T03:35:59.810Z",
+  "updatedAt": "2024-08-30T03:49:41.942Z",
   "devdoc": {
@@ -447,0 +447,0 @@ "kind": "dev",

package.json

 {
   "name": "@xyo-network/solidity",
-  "version": "3.2.0",
+  "version": "3.2.1",
   "bugs": {
@@ -5,0 +5,0 @@ "url": "git+https://github.com/XYOracleNetwork/sdk-xyo-typechain/issues",

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No metric changes

No dependency changes