error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 131 | Before EIP-9999, for accounts with associated code (smart contracts), the account nonce is only used and incremented | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-link-first/

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 275 | These rules are defined in EIP-9999. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 500 | the opcode banning and storage access rules described in EIP-9999. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 514 | They may be propagated in the alternative mempool that allows them explicitly as defined in EIP-9999. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 526 | certain rules for the mempool transactions in EIP-9999. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 528 | A builder that chooses not to enforce the rules from EIP-9999 **must** take care to re-validate each transaction | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-00.md | 700 | * code: -32504 - transaction rejected because `paymaster` is throttled or banned, as defined by EIP-9999. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[markdown-refs]: unable to read file `eip-9999.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md') --> EIPS/eip-00.md | 131 | Before EIP-9999, for accounts with associated code (smart contracts), the account nonce is only used and incremented | = help: see https://ethereum.github.io/eipw/markdown-refs/

error[markdown-refs]: unable to read file `eip-9999.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md') --> EIPS/eip-00.md | 275 | These rules are defined in EIP-9999. |

error[markdown-refs]: unable to read file `eip-9999.md`: Io: JsValue(Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md' Error: ENOENT: no such file or directory, open 'EIPS/eip-9999.md') --> EIPS/eip-00.md | 500 | the opcode banning and storage access rules described in EIP-9999. |

EIPS/eip-00.md:340:1 MD051/link-fragments Link fragments should be valid [Context: "[Calculation of Transaction Type AA_TX_TYPE hash](#calculation-of-transaction-type-aatxtype-hash)"]

EIPS/eip-00.md:379:1 MD051/link-fragments Link fragments should be valid [Context: "[Calculation of Transaction Type AA_TX_TYPE hash](#calculation-of-transaction-type-aatxtype-hash)"]

Failed with exit code: 1