error[markdown-link-first]: the first match of the given pattern must be a link --> EIPS/eip-8900 | 23 | Most ERC-20 Tokens representing E.V.M. Blockchain-based companies (or also called "Protocols"), DO NOT work the same way as a Publicly Traded Stock that represents a Share of ownership of the equity of that such company (so the user who buys a Protocol's ERC-20, is also now a share-holder and co-owner of the business, its profits and/or its dividends), but rather function as "Commodities" such as oil; they are consumable items created by said E.V.M. Blockchain-based company (or "Protocol") to be spent in their platform. They are Publicly Traded and advertised to be representing the underlying Protocol like a Share, working in practice the same way as a Commodity and without any Public, Transparent and *Clear* Financial Information as publicly traded stocks have. | = 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-8900 | 23 | Most ERC-20 Tokens representing E.V.M. Blockchain-based companies (or also called "Protocols"), DO NOT work the same way as a Publicly Traded Stock that represents a Share of ownership of the equity of that such company (so the user who buys a Protocol's ERC-20, is also now a share-holder and co-owner of the business, its profits and/or its dividends), but rather function as "Commodities" such as oil; they are consumable items created by said E.V.M. Blockchain-based company (or "Protocol") to be spent in their platform. They are Publicly Traded and advertised to be representing the underlying Protocol like a Share, working in practice the same way as a Commodity and without any Public, Transparent and *Clear* Financial Information as publicly traded stocks have. | = 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-8900 | 34 | All Transparent Financial Statements Standard implementations MUST implement ERC-20 to represent shares, and the financial numbers displayed in a StableCoin's value. | = 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-8900 | 36 | All Transparent Financial Statements MUST implement ERC-20's optional metadata extensions. | = 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-8900 | 57 | - E.P.S.: Earnings per Share Token (ERC-20), showing profit allocated per share. | = 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-8900 | 344 | ERC-20 is enforced because implementation details like Earnings Per Token calculation directly carry over to the accounting. This standardization makes the Transparent Financial Statements compatible with all ERC-20 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-8900 | 344 | ERC-20 is enforced because implementation details like Earnings Per Token calculation directly carry over to the accounting. This standardization makes the Transparent Financial Statements compatible with all ERC-20 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-8900 | 352 | Transparent Financial Statements Standard is fully backward compatible with the ERC-20 standard and has no known compatibility issues with other standards. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

error[preamble-file-name]: file name must reflect the preamble header `eip` --> EIPS/eip-8900:2:5 | 2 | eip: 8900 | ^^^^^ this value | = help: this file's name should be `eip-8900.md` = help: see https://ethereum.github.io/eipw/preamble-file-name/

error[preamble-re-discussions-to]: preamble header `discussions-to` should point to a thread on ethereum-magicians.org --> EIPS/eip-8900:6:16 | 6 | discussions-to: https://ethereum-magicians.org/t/e-i-p-8900-transparent-financial-statements/21191?u=nachoxt17 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 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 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/