@cfxjs/sirius-next-i18n 0.1.26 → 0.1.28

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
 
-> @cfxjs/sirius-next-i18n@0.1.26 build /Users/mac/Desktop/code/sirius-next/packages/i18n
+> @cfxjs/sirius-next-i18n@0.1.28 build /Users/mac/Desktop/code/sirius-next/packages/i18n
 > tsc
 

package/cspace/en/translation.json

@@ -297,12 +297,22 @@
       "third": "3. Only single-file verification is supported.",
       "fourth": "4. Constructor arguments are not supported currently."
     },
+    "vyperNotice": {
+      "first": "1. Does not support external libraries or optimization settings.",
+      "second": "2. Source code should fit inside a single .vy file."
+    },
+    "stepTitle": {
+      "step1": "Contract Details",
+      "step2": "Upload Contract Source Code"
+    },
     "upload": "Upload Contract File",
     "submit": "Submit",
     "contractAddress": "Contract Address",
     "runs": "Runs",
+    "advancedConfiguration": "Advanced Configuration",
     "contractName": "Contract Name",
-    "compiler": "Compiler",
+    "compilerType": "Compiler Type",
+    "compilerVersion": "Compiler Version",
     "optimization": "Optimization",
     "license": "License",
     "evmVersion": "EVM Version to target",
@@ -311,6 +321,11 @@
     "libraryName": "Library_{{index}} Name",
     "libraryContractAddress": "Library_{{index}} Contract Address",
     "contractSourceCode": "Contract Source Code",
+    "button": {
+      "reset": "Reset",
+      "previous": "Previous",
+      "continue": "Continue"
+    },
     "error": {
       "required": "Required",
       "min": "The minimum value is 0",

package/cspace/zh_cn/translation.json

@@ -296,12 +296,22 @@
       "third": "3. 仅支持单文件验证。",
       "fourth": "4. 目前暂不支持构造函数。"
     },
+    "vyperNotice": {
+      "first": "1. 不支持外部库或优化设置。",
+      "second": "2. 源代码应包含在单个 .vy 文件中。"
+    },
+    "stepTitle": {
+      "step1": "合约信息",
+      "step2": "上传合约代码"
+    },
     "upload": "上传合约文件",
     "submit": "提交",
     "contractAddress": "合约地址",
     "runs": "运行",
+    "advancedConfiguration": "高级配置",
     "contractName": "合约名称",
-    "compiler": "编译器",
+    "compilerType": "编译器类型",
+    "compilerVersion": "编译器版本",
     "optimization": "优化",
     "license": "许可协议",
     "evmVersion": "EVM 版本",
@@ -310,6 +320,11 @@
     "libraryName": "Library_{{index}} 合约名称",
     "libraryContractAddress": "Library_{{index}} 合约地址",
     "contractSourceCode": "合约源码",
+    "button": {
+      "reset": "重置",
+      "previous": "上一步",
+      "continue": "继续"
+    },
     "error": {
       "required": "请输入",
       "min": "最小值为 0",

package/dist/cspace/en/translation.json

@@ -297,12 +297,22 @@
             "third": "3. Only single-file verification is supported.",
             "fourth": "4. Constructor arguments are not supported currently."
         },
+        "vyperNotice": {
+            "first": "1. Does not support external libraries or optimization settings.",
+            "second": "2. Source code should fit inside a single .vy file."
+        },
+        "stepTitle": {
+            "step1": "Contract Details",
+            "step2": "Upload Contract Source Code"
+        },
         "upload": "Upload Contract File",
         "submit": "Submit",
         "contractAddress": "Contract Address",
         "runs": "Runs",
+        "advancedConfiguration": "Advanced Configuration",
         "contractName": "Contract Name",
-        "compiler": "Compiler",
+        "compilerType": "Compiler Type",
+        "compilerVersion": "Compiler Version",
         "optimization": "Optimization",
         "license": "License",
         "evmVersion": "EVM Version to target",
@@ -311,6 +321,11 @@
         "libraryName": "Library_{{index}} Name",
         "libraryContractAddress": "Library_{{index}} Contract Address",
         "contractSourceCode": "Contract Source Code",
+        "button": {
+            "reset": "Reset",
+            "previous": "Previous",
+            "continue": "Continue"
+        },
         "error": {
             "required": "Required",
             "min": "The minimum value is 0",

package/dist/evm/base/en/translation.json

@@ -287,12 +287,22 @@
             "third": "3. Only single-file verification is supported.",
             "fourth": "4. Constructor arguments are not supported currently."
         },
+        "vyperNotice": {
+            "first": "1. Does not support external libraries or optimization settings.",
+            "second": "2. Source code should fit inside a single .vy file."
+        },
+        "stepTitle": {
+            "step1": "Contract Details",
+            "step2": "Upload Contract Source Code"
+        },
         "upload": "Upload Contract File",
         "submit": "Submit",
         "contractAddress": "Contract Address",
         "runs": "Runs",
+        "advancedConfiguration": "Advanced Configuration",
         "contractName": "Contract Name",
-        "compiler": "Compiler",
+        "compilerType": "Compiler Type",
+        "compilerVersion": "Compiler Version",
         "optimization": "Optimization",
         "license": "License",
         "evmVersion": "EVM Version to target",
@@ -301,6 +311,11 @@
         "libraryName": "Library_{{index}} Name",
         "libraryContractAddress": "Library_{{index}} Contract Address",
         "contractSourceCode": "Contract Source Code",
+        "button": {
+            "reset": "Reset",
+            "previous": "Previous",
+            "continue": "Continue"
+        },
         "error": {
             "required": "Required",
             "min": "The minimum value is 0",
@@ -389,7 +404,6 @@
         "r": "r",
         "s": "s",
         "tooltip": {
-            "delegationTransaction": "Delegation transaction: Transactions with type 0x4 set a delegation designator (0xef0100 + target address) in the EOA’s code field. When such an EOA receives a call, the EVM executes the bytecode at the designated target address within the context of the EOA, giving the target contract access to the EOA’s storage and balance. This transaction type enables smart contract-like behavior—such as batched transactions (e.g., ERC-20 approvals and swaps) and custom permission control—while preserving the EOA’s original address and signing key. ",
             "delegateTo": "Account’s executable code address",
             "valid": "Indicates if the EOA’s signed EIP-7702 envelope meets all validity checks (signature, nonce, chain ID, etc.). If valid, the account instantly delegates execution to the designated delegated contract."
         }
@@ -1649,7 +1663,8 @@
             "txnType": {
                 "0": "Legacy transaction: Transactions with type 0x0 are legacy transactions that use the transaction format existing before typed transactions were introduced in EIP-2718. They contain the parameters nonce, gasPrice, gasLimit, to, value, data, v, r,and s.",
                 "1": "Access list transaction: Transactions with type 0x1 are transactions introduced in EIP-2930. They contain, along with the legacy parameters, an accessList parameter, which specifies an array of addresses and storage keys that the transaction plans to access .",
-                "2": "EIP-1559 transaction: Transactions with type 0x2 are transactions introduced in EIP-1559. They use an in-protocol dynamically changing base fee per gas at each pivot block, the base fee per gas is adjusted to address network congestion as measured by a gas target."
+                "2": "EIP-1559 transaction: Transactions with type 0x2 are transactions introduced in EIP-1559. They use an in-protocol dynamically changing base fee per gas at each pivot block, the base fee per gas is adjusted to address network congestion as measured by a gas target.",
+                "4": "Delegation transaction: Transactions with type 0x4 set a delegation designator (0xef0100 + target address) in the EOA’s code field. When such an EOA receives a call, the EVM executes the bytecode at the designated target address within the context of the EOA, giving the target contract access to the EOA’s storage and balance. This transaction type enables smart contract-like behavior—such as batched transactions (e.g., ERC-20 approvals and swaps) and custom permission control—while preserving the EOA’s original address and signing key. "
             },
             "getRawTxJson": "Get raw Tx JSON"
         },

package/evm/base/en/translation.json

@@ -287,12 +287,22 @@
       "third": "3. Only single-file verification is supported.",
       "fourth": "4. Constructor arguments are not supported currently."
     },
+    "vyperNotice": {
+      "first": "1. Does not support external libraries or optimization settings.",
+      "second": "2. Source code should fit inside a single .vy file."
+    },
+    "stepTitle": {
+      "step1": "Contract Details",
+      "step2": "Upload Contract Source Code"
+    },
     "upload": "Upload Contract File",
     "submit": "Submit",
     "contractAddress": "Contract Address",
     "runs": "Runs",
+    "advancedConfiguration": "Advanced Configuration",
     "contractName": "Contract Name",
-    "compiler": "Compiler",
+    "compilerType": "Compiler Type",
+    "compilerVersion": "Compiler Version",
     "optimization": "Optimization",
     "license": "License",
     "evmVersion": "EVM Version to target",
@@ -301,6 +311,11 @@
     "libraryName": "Library_{{index}} Name",
     "libraryContractAddress": "Library_{{index}} Contract Address",
     "contractSourceCode": "Contract Source Code",
+    "button": {
+      "reset": "Reset",
+      "previous": "Previous",
+      "continue": "Continue"
+    },
     "error": {
       "required": "Required",
       "min": "The minimum value is 0",
@@ -389,7 +404,6 @@
     "r": "r",
     "s": "s",
     "tooltip": {
-      "delegationTransaction": "Delegation transaction: Transactions with type 0x4 set a delegation designator (0xef0100 + target address) in the EOA’s code field. When such an EOA receives a call, the EVM executes the bytecode at the designated target address within the context of the EOA, giving the target contract access to the EOA’s storage and balance. This transaction type enables smart contract-like behavior—such as batched transactions (e.g., ERC-20 approvals and swaps) and custom permission control—while preserving the EOA’s original address and signing key. ",
       "delegateTo": "Account’s executable code address",
       "valid": "Indicates if the EOA’s signed EIP-7702 envelope meets all validity checks (signature, nonce, chain ID, etc.). If valid, the account instantly delegates execution to the designated delegated contract."
     }
@@ -1649,7 +1663,8 @@
       "txnType": {
         "0": "Legacy transaction: Transactions with type 0x0 are legacy transactions that use the transaction format existing before typed transactions were introduced in EIP-2718. They contain the parameters nonce, gasPrice, gasLimit, to, value, data, v, r,and s.",
         "1": "Access list transaction: Transactions with type 0x1 are transactions introduced in EIP-2930. They contain, along with the legacy parameters, an accessList parameter, which specifies an array of addresses and storage keys that the transaction plans to access .",
-        "2": "EIP-1559 transaction: Transactions with type 0x2 are transactions introduced in EIP-1559. They use an in-protocol dynamically changing base fee per gas at each pivot block, the base fee per gas is adjusted to address network congestion as measured by a gas target."
+        "2": "EIP-1559 transaction: Transactions with type 0x2 are transactions introduced in EIP-1559. They use an in-protocol dynamically changing base fee per gas at each pivot block, the base fee per gas is adjusted to address network congestion as measured by a gas target.",
+        "4": "Delegation transaction: Transactions with type 0x4 set a delegation designator (0xef0100 + target address) in the EOA’s code field. When such an EOA receives a call, the EVM executes the bytecode at the designated target address within the context of the EOA, giving the target contract access to the EOA’s storage and balance. This transaction type enables smart contract-like behavior—such as batched transactions (e.g., ERC-20 approvals and swaps) and custom permission control—while preserving the EOA’s original address and signing key. "
       },
       "getRawTxJson": "Get raw Tx JSON"
     },

package/evm/base/zh_cn/translation.json

@@ -286,12 +286,22 @@
       "third": "3. 仅支持单文件验证。",
       "fourth": "4. 目前暂不支持构造函数。"
     },
+    "vyperNotice": {
+      "first": "1. 不支持外部库或优化设置。",
+      "second": "2. 源代码应包含在单个 .vy 文件中。"
+    },
+    "stepTitle": {
+      "step1": "合约信息",
+      "step2": "上传合约代码"
+    },
     "upload": "上传合约文件",
     "submit": "提交",
     "contractAddress": "合约地址",
     "runs": "运行",
+    "advancedConfiguration": "高级配置",
     "contractName": "合约名称",
-    "compiler": "编译器",
+    "compilerType": "编译器类型",
+    "compilerVersion": "编译器版本",
     "optimization": "优化",
     "license": "许可协议",
     "evmVersion": "EVM 版本",
@@ -300,6 +310,11 @@
     "libraryName": "Library_{{index}} 合约名称",
     "libraryContractAddress": "Library_{{index}} 合约地址",
     "contractSourceCode": "合约源码",
+    "button": {
+      "reset": "重置",
+      "previous": "上一步",
+      "continue": "继续"
+    },
     "error": {
       "required": "请输入",
       "min": "最小值为 0",
@@ -388,7 +403,6 @@
     "r": "r",
     "s": "s",
     "tooltip": {
-      "delegationTransaction": "委托交易：类型为 0x4 的交易会在 EOA（外部拥有账户）的代码字段中设置一个“委托标识符”（0xef0100 + 目标地址）。当该 EOA 接收到调用时，EVM 会在该 EOA 的上下文中执行目标地址中的字节码，从而使目标合约能够访问该 EOA 的存储和余额。该交易类型实现了类智能合约的功能，例如批量交易（如 ERC-20 授权与交换）和权限管理，同时保留了原始 EOA 的地址和签名能力。",
       "delegateTo": "账户可执行代码地址",
       "valid": "检查 EOA 账户签署的 EIP-7702 信封是否通过所有验证（签名、随机数、链 ID 等）；如果通过，账户会立即执行指定的委托合约代码。"
     }
@@ -1646,7 +1660,8 @@
       "txnType": {
         "0": "传统交易: 0x0交易类型是传统交易, 使用 EIP-2718 引入类型交易之前存在的交易格式。交易包含参数: nonce、gasPrice、gasLimit、to、value、data、v、r和s。",
         "1": "访问列表交易: 类型为0x1的交易是EIP-2930引入的交易。除了传统参数外, 还包含一个访问列表参数, 该参数指定了交易计划访问的地址数组和存储键。",
-        "2": "EIP-1559交易: 类型为0x2的交易是EIP-1559引入的交易。交易使用协议中在每个Pivot区块动态变化的基础Gas费用, 基础Gas费用会根据Gas目标进行调整, 以应对网络拥塞。"
+        "2": "EIP-1559交易: 类型为0x2的交易是EIP-1559引入的交易。交易使用协议中在每个Pivot区块动态变化的基础Gas费用, 基础Gas费用会根据Gas目标进行调整, 以应对网络拥塞。",
+        "4": "委托交易：类型为 0x4 的交易会在 EOA（外部拥有账户）的代码字段中设置一个“委托标识符”（0xef0100 + 目标地址）。当该 EOA 接收到调用时，EVM 会在该 EOA 的上下文中执行目标地址中的字节码，从而使目标合约能够访问该 EOA 的存储和余额。该交易类型实现了类智能合约的功能，例如批量交易（如 ERC-20 授权与交换）和权限管理，同时保留了原始 EOA 的地址和签名能力。"
       },
       "getRawTxJson": "获取原始交易JSON"
     },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cfxjs/sirius-next-i18n",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "files": [
     "*/**"
   ],