error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-XXXX.md | 32 | This is a step towards fulfilling the purposes as described in the Motivation of EIP-2930: | = 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-XXXX.md | 69 | such as transaction bundlers, as well as in-protocol with EIP-3074. | = 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-XXXX.md | 73 | Akin to `TLOAD`, as described in EIP-1153, the `ACCESS_KEY` opcode provides contracts with a view that is global | = 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-XXXX.md | 82 | Generally the gas cost savings achieved with EIP-2930 are not applicable in as many use-cases. | = 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-XXXX.md | 98 | specifically the `BLOBHASH` opcode of EIP-4844: | = 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-XXXX.md | 102 | The `BLOBHASH` functionality of EIP-4844 is not re-usable for the purposes of this EIP however, | = 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-XXXX.md | 114 | With EIP-2930, the access-list contents are already readily available in the transaction-context during EVM execution, | = 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-XXXX.md | 134 | The access-list attributes are already gas-metered in EIP-2930, | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[preamble-eip]: preamble header `eip` must be an unsigned integer --> EIPS/eip-XXXX.md:2:5 | 2 | eip: XXXX | ^^^^^ not a non-negative integer | = help: see https://ethereum.github.io/eipw/preamble-eip/

validation found errors :(