@cfxjs/sirius-next-i18n 0.1.24 → 0.1.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/.turbo/turbo-build.log
CHANGED
|
@@ -372,6 +372,28 @@
|
|
|
372
372
|
"apy": "(APY 4%)",
|
|
373
373
|
"viewLockedDetails": "Click to view lock history"
|
|
374
374
|
},
|
|
375
|
+
"authList": {
|
|
376
|
+
"authorizations": "Authorizations",
|
|
377
|
+
"authorizationList": "Authorization List",
|
|
378
|
+
"delegateTo": "Delegate to",
|
|
379
|
+
"authority": "Authority",
|
|
380
|
+
"delegatedAddress": "Delegated Address",
|
|
381
|
+
"nonce": "Nonce",
|
|
382
|
+
"valid": "Valid",
|
|
383
|
+
"yes": "Yes",
|
|
384
|
+
"no": "No",
|
|
385
|
+
"delegatedCode": "Delegated Code",
|
|
386
|
+
"txSender": "Tx Sender",
|
|
387
|
+
"eoaWithCode": "EOA+CODE",
|
|
388
|
+
"yParity": "yParity",
|
|
389
|
+
"r": "r",
|
|
390
|
+
"s": "s",
|
|
391
|
+
"tooltip": {
|
|
392
|
+
"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. ",
|
|
393
|
+
"delegateTo": "Account’s executable code address",
|
|
394
|
+
"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."
|
|
395
|
+
}
|
|
396
|
+
},
|
|
375
397
|
"blocks": {
|
|
376
398
|
"title": "Blocks",
|
|
377
399
|
"description": "Blocks",
|
|
@@ -372,6 +372,28 @@
|
|
|
372
372
|
"apy": "(APY 4%)",
|
|
373
373
|
"viewLockedDetails": "Click to view lock history"
|
|
374
374
|
},
|
|
375
|
+
"authList": {
|
|
376
|
+
"authorizations": "Authorizations",
|
|
377
|
+
"authorizationList": "Authorization List",
|
|
378
|
+
"delegateTo": "Delegate to",
|
|
379
|
+
"authority": "Authority",
|
|
380
|
+
"delegatedAddress": "Delegated Address",
|
|
381
|
+
"nonce": "Nonce",
|
|
382
|
+
"valid": "Valid",
|
|
383
|
+
"yes": "Yes",
|
|
384
|
+
"no": "No",
|
|
385
|
+
"delegatedCode": "Delegated Code",
|
|
386
|
+
"txSender": "Tx Sender",
|
|
387
|
+
"eoaWithCode": "EOA+CODE",
|
|
388
|
+
"yParity": "yParity",
|
|
389
|
+
"r": "r",
|
|
390
|
+
"s": "s",
|
|
391
|
+
"tooltip": {
|
|
392
|
+
"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. ",
|
|
393
|
+
"delegateTo": "Account’s executable code address",
|
|
394
|
+
"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."
|
|
395
|
+
}
|
|
396
|
+
},
|
|
375
397
|
"blocks": {
|
|
376
398
|
"title": "Blocks",
|
|
377
399
|
"description": "Blocks",
|
|
@@ -371,6 +371,28 @@
|
|
|
371
371
|
"lockedDetailUnlockTime": "预计解锁时间",
|
|
372
372
|
"viewLockedDetails": "点击查看锁定历史"
|
|
373
373
|
},
|
|
374
|
+
"authList": {
|
|
375
|
+
"authorizations": "委托记录",
|
|
376
|
+
"authorizationList": "授权列表",
|
|
377
|
+
"delegateTo": "委托地址",
|
|
378
|
+
"authority": "授权方",
|
|
379
|
+
"delegatedAddress": "委托地址",
|
|
380
|
+
"nonce": "随机数",
|
|
381
|
+
"valid": "是否有效",
|
|
382
|
+
"yes": "Yes",
|
|
383
|
+
"no": "No",
|
|
384
|
+
"delegatedCode": "委托代码",
|
|
385
|
+
"txSender": "交易发起方",
|
|
386
|
+
"eoaWithCode": "EOA+CODE",
|
|
387
|
+
"yParity": "yParity",
|
|
388
|
+
"r": "r",
|
|
389
|
+
"s": "s",
|
|
390
|
+
"tooltip": {
|
|
391
|
+
"delegationTransaction": "委托交易:类型为 0x4 的交易会在 EOA(外部拥有账户)的代码字段中设置一个“委托标识符”(0xef0100 + 目标地址)。当该 EOA 接收到调用时,EVM 会在该 EOA 的上下文中执行目标地址中的字节码,从而使目标合约能够访问该 EOA 的存储和余额。该交易类型实现了类智能合约的功能,例如批量交易(如 ERC-20 授权与交换)和权限管理,同时保留了原始 EOA 的地址和签名能力。",
|
|
392
|
+
"delegateTo": "账户可执行代码地址",
|
|
393
|
+
"valid": "检查 EOA 账户签署的 EIP-7702 信封是否通过所有验证(签名、随机数、链 ID 等);如果通过,账户会立即执行指定的委托合约代码。"
|
|
394
|
+
}
|
|
395
|
+
},
|
|
374
396
|
"blocks": {
|
|
375
397
|
"title": "区块",
|
|
376
398
|
"description": "区块",
|
package/package.json
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cfxjs/sirius-next-i18n",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.26",
|
|
4
4
|
"files": [
|
|
5
5
|
"*/**"
|
|
6
6
|
],
|
|
7
7
|
"devDependencies": {
|
|
8
8
|
"@turbo/gen": "^1.12.4",
|
|
9
9
|
"typescript": "^5.4.2",
|
|
10
|
-
"@cfxjs/sirius-next-
|
|
11
|
-
"@cfxjs/sirius-next-
|
|
10
|
+
"@cfxjs/sirius-next-typescript-config": "0.0.0",
|
|
11
|
+
"@cfxjs/sirius-next-eslint-config": "0.0.0"
|
|
12
12
|
},
|
|
13
13
|
"publishConfig": {
|
|
14
14
|
"access": "public"
|