Skip to content

Add ERC: ERC for Exit Format and State Channels #5328

Add ERC: ERC for Exit Format and State Channels

Add ERC: ERC for Exit Format and State Channels #5328

Triggered via pull request November 29, 2024 16:44
Status Cancelled
Total duration 7m 35s
Artifacts 1

ci.yml

on: pull_request
Save PR Number
2s
Save PR Number
HTMLProofer
7m 10s
HTMLProofer
Link Check
18s
Link Check
CodeSpell
10s
CodeSpell
EIP Walidator
8s
EIP Walidator
Markdown Linter
5s
Markdown Linter
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 1 warning
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'
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`): ERCS/erc-7824.md#L15
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`) --> ERCS/erc-7824.md | 15 | This ERC defines a standard **Exit Format** for specifying outcomes and asset allocations in state channels. The Exit Format support... | = info: the pattern in question: `(?i)erc[\s]*[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/
preamble header `description` should not contain `standard` (or similar words.): ERCS/erc-7824.md#L4
error[preamble-re-description]: preamble header `description` should not contain `standard` (or similar words.) --> ERCS/erc-7824.md:4:13 | 4 | description: A standard for defining outcomes and asset allocations in state channels using the Exit Format. | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ prohibited pattern was matched | = info: the pattern in question: `(?i)standar\w*\b` = help: see https://ethereum.github.io/eipw/preamble-re-description/
preamble header `discussions-to` should point to a thread on ethereum-magicians.org: ERCS/erc-7824.md#L6
error[preamble-re-discussions-to]: preamble header `discussions-to` should point to a thread on ethereum-magicians.org --> ERCS/erc-7824.md:6:16 | 6 | discussions-to: https://ethereum-magicians.org/c/ercs/57 (Coming soon) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 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/
the first match of the given pattern must be a link: ERCS/erc-7825.md#L16
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 16 | This ERC standardizes data types for state channels (Also known as Nitro Protocol), enabling efficient off-chain state execution and... | = 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: ERCS/erc-7825.md#L20
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 20 | State channels offer a mechanism for off-chain execution, improving scalability and reducing transaction costs. However, existing im... | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-7825.md#L115
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 115 | ### Integration with ERC-4337 | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-7825.md#L119
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 119 | 2. **Programmable Wallets:** Wallets using ERC-4337 can interact directly with Nitro-based state channels. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-7825.md#L137
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 137 | This ERC builds on the modularity of Nitro Protocol and the flexibility of ERC-4337, creating a unified standard for state channel ... | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-7825.md#L141
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7825.md | 141 | This ERC depends on ERC-4337 and assumes its availability for account abstraction functionality. Legacy state channel implementatio... | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
preamble header `description` value is too long (max 140): ERCS/erc-7825.md#L4
error[preamble-len-description]: preamble header `description` value is too long (max 140) --> ERCS/erc-7825.md:4:13 | 4 | ...on: A standard for implementing interoperable state channels on Ethereum using the State Channel Protocol, integrated with ERC-4337 for enhanced account abstraction. | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ too long | = help: see https://ethereum.github.io/eipw/preamble-len-description/
HTMLProofer
Canceling since a higher priority waiting request for 'Continuous Integration-728' exists
HTMLProofer
The operation was canceled.
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
86 Bytes