error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7818.md | 73 | Enforcing `FIFO` priority ensures that tokens nearing expiration are processed before newer ones, aligning with the token lifecycle ... | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+` = help: see https://ethereum.github.io/eipw/markdown-link-first/

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 16 | Introduces an extension for `ERC-20` tokens , which facilitates the implementation of an expiration mechanism. Through this extensio... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+` = help: see https://ethereum.github.io/eipw/markdown-no-backticks/

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 16 | Introduces an extension for `ERC-20` tokens , which facilitates the implementation of an expiration mechanism. Through this extensio... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 20 | This extension standard facilitates the development of `ERC-20` standard compatible tokens featuring expiration dates. This capabili... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 31 | The rationale for developing an expirable `ERC-20` token extension is based on several key requirements that ensure its practicality... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 33 | - Compatibility with the existing `ERC-20` standard. The extension should integrate smoothly with the `ERC-20` interface, This ensur... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 33 | - Compatibility with the existing `ERC-20` standard. The extension should integrate smoothly with the `ERC-20` interface, This ensur... | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 370 | - Purpose: This function works similarly to `ERC-20` transfer but allows to move tokens within specific eras and slots. | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-no-backticks]: EIP references should not be in backticks --> ERCS/erc-7818.md | 383 | - Purpose: This function works similarly to `ERC-20` transferFrom but allows to move tokens within specific eras and slots. | = info: the pattern in question: `(?i)(eip|erc)-[0-9]+`

error[markdown-order-section]: body has extra section(s) --> ERCS/erc-7818.md | 395 | ## Token Receipt and Transaction Likelihood across various block time | = help: see https://ethereum.github.io/eipw/markdown-order-section/

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/