Add ERC: App Keys for Fully Embedded Accounts #4386
Annotations
8 errors and 2 warnings
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L16
error[markdown-link-first]: the first match of the given pattern must be a link
--> ERCS/erc-7763.md
|
16 | This ERC proposes a standard for wallets to generate and manage exposed application-specific key pairs, building upon the concepts introduced in ERC-1775 and complementing ERC-7716. It defines exposed keys that allow free signing by the current site. This approach enhances flexibility in managing permissions for decentralized applications (dApps) while maintaining a balance with security considerations.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
= help: see https://ethereum.github.io/eipw/markdown-link-first/
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L16
error[markdown-link-first]: the first match of the given pattern must be a link
--> ERCS/erc-7763.md
|
16 | This ERC proposes a standard for wallets to generate and manage exposed application-specific key pairs, building upon the concepts introduced in ERC-1775 and complementing ERC-7716. It defines exposed keys that allow free signing by the current site. This approach enhances flexibility in managing permissions for decentralized applications (dApps) while maintaining a balance with security considerations.
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L20
error[markdown-link-first]: the first match of the given pattern must be a link
--> ERCS/erc-7763.md
|
20 | As the ecosystem of dApps grows, there's an increasing need for more granular and flexible key management. This ERC simplifies the ideas presented in ERC-1775 and ERC-7715 by providing a standard for exposed app keys that a wallet can use to manage permissions for a dApp:
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L20
error[markdown-link-first]: the first match of the given pattern must be a link
--> ERCS/erc-7763.md
|
20 | As the ecosystem of dApps grows, there's an increasing need for more granular and flexible key management. This ERC simplifies the ideas presented in ERC-1775 and ERC-7715 by providing a standard for exposed app keys that a wallet can use to manage permissions for a dApp:
|
= info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L119
error[markdown-order-section]: body has extra section(s)
--> ERCS/erc-7763.md
|
119 | ## Conclusion
|
= help: see https://ethereum.github.io/eipw/markdown-order-section/
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L13
error[markdown-req-section]: body is missing section(s): `Rationale`, `Copyright`
--> ERCS/erc-7763.md
|
|
= help: must be at the second level (`## Heading`)
= help: see https://ethereum.github.io/eipw/markdown-req-section/
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f:
ERCS/erc-7763.md#L4
error[preamble-re-description]: preamble header `description` should not contain `standard` (or similar words.)
--> ERCS/erc-7763.md:4:13
|
4 | description: A standard for generating and managing exposed application-specific key pairs
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ prohibited pattern was matched
|
= info: the pattern in question: `(?i)standar\w*\b`
= help: see https://ethereum.github.io/eipw/preamble-re-description/
|
Run ethereum/eipw-action@6785fa283773db4819cb0abf17a185a1d9b6eb9f
validation found errors :(
|
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/
|
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/
|
Loading