Add EIP: Add wallet_signIntendedValidatorData method #16757
ci.yml
on: pull_request
Save PR Number
3s
HTMLProofer
4m 28s
Link Check
15s
CodeSpell
9s
EIP Walidator
4s
Markdown Linter
3s
Annotations
15 errors and 6 warnings
Markdown Linter
Process completed with exit code 1.
|
Markdown Linter
Unable to process file command 'env' successfully.
|
Markdown Linter
Invalid value. Matching delimiter not found 'EOF'
|
the first match of the given pattern must be a link:
EIPS/eip-x.md#L23
error[markdown-link-first]: the first match of the given pattern must be a link
--> EIPS/eip-x.md
|
23 | Currently, signing messages relies heavily on ERC-191 version 0x45 (`eth_sign`) and EIP-712 (`eth_signTypedData`). While EIP-712 provides a more structured approach, it is often seen as complex. On the other hand, ERC-191 version 0x45 is widely used but poses significant phishing risks due to the lack of data parsing.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
= help: see https://ethereum.github.io/eipw/markdown-link-first/
|
the first match of the given pattern must be a link:
EIPS/eip-x.md#L23
error[markdown-link-first]: the first match of the given pattern must be a link
--> EIPS/eip-x.md
|
23 | Currently, signing messages relies heavily on ERC-191 version 0x45 (`eth_sign`) and EIP-712 (`eth_signTypedData`). While EIP-712 provides a more structured approach, it is often seen as complex. On the other hand, ERC-191 version 0x45 is widely used but poses significant phishing risks due to the lack of data parsing.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
the first match of the given pattern must be a link:
EIPS/eip-x.md#L25
error[markdown-link-first]: the first match of the given pattern must be a link
--> EIPS/eip-x.md
|
25 | ERC-191 defines three versions: 0x45, 0x01, and 0x00. This proposal aims to fully support EIP-191 by introducing the rpc call for 0x00 version, which enables signing data with an intended validator address. This new method will:
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
the first match of the given pattern must be a link:
EIPS/eip-x.md#L29
error[markdown-link-first]: the first match of the given pattern must be a link
--> EIPS/eip-x.md
|
29 | - Provide a simpler alternative to EIP-712, offering a balance between usability and security.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
the first match of the given pattern must be a link:
EIPS/eip-x.md#L87
error[markdown-link-first]: the first match of the given pattern must be a link
--> EIPS/eip-x.md
|
87 | The `wallet_signIntendedValidatorData` method aims to bridge the gap between the simplicity of ERC-191 version 0x45 and the structured approach of EIP-712. By specifying the intended validator address, it reduces phishing risks and provides a more secure signing method for smart contract accounts and other use cases requiring a specific validator address.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
references to proposals with a `category` of `ERC` must use a prefix of `ERC`:
EIPS/eip-x.md#L25
error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC`
--> EIPS/eip-x.md
|
25 | ERC-191 defines three versions: 0x45, 0x01, and 0x00. This proposal aims to fully support EIP-191 by introducing the rpc call for 0x00 version, which enables signing data with an intended validator address. This new method will:
|
= help: see https://ethereum.github.io/eipw/markdown-refs/
|
non-relative link or image:
EIPS/eip-x.md#L15
error[markdown-rel-links]: non-relative link or image
--> EIPS/eip-x.md
|
15 | This EIP introduces a new JSON-RPC method, `wallet_signIntendedValidatorData`, which allows signing data with an intended validator address using [ERC-191](https://github.com/ethereum/ercs/blob/master/ERCS/erc-191.md) version 0x00 with this format:
|
= help: see https://ethereum.github.io/eipw/markdown-rel-links/
|
preamble header `discussions-to` is not a valid URL:
EIPS/eip-x.md#L5
error[preamble-discussions-to]: preamble header `discussions-to` is not a valid URL
--> EIPS/eip-x.md:5:16
|
5 | discussions-to: TBD
| ^^^^ relative URL without a base
|
= help: see https://ethereum.github.io/eipw/preamble-discussions-to/
|
preamble header `title` value is too long (max 44):
EIPS/eip-x.md#L2
error[preamble-len-title]: preamble header `title` value is too long (max 44)
--> EIPS/eip-x.md:2:7
|
2 | title: Add wallet_signIntendedValidatorData JSON-RPC method
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ too long
|
= help: see https://ethereum.github.io/eipw/preamble-len-title/
|
preamble header `discussions-to` should point to a thread on ethereum-magicians.org:
EIPS/eip-x.md#L5
error[preamble-re-discussions-to]: preamble header `discussions-to` should point to a thread on ethereum-magicians.org
--> EIPS/eip-x.md:5:16
|
5 | discussions-to: TBD
| ^^^^ required pattern was not matched
|
= info: the pattern in question: `^https://ethereum-magicians.org/t/[^/]+/[0-9]+$`
= help: see https://ethereum.github.io/eipw/preamble-re-discussions-to/
|
HTMLProofer
Canceling since a higher priority waiting request for 'Continuous Integration-8774' exists
|
HTMLProofer
The operation was canceled.
|
Save PR Number
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Markdown Linter
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
EIP Walidator
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
CodeSpell
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Link Check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "pr_number".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
pr_number
|
87 Bytes |
|