error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-7699.md | 16 | The ERC-20 token standard has become the most widely used token standard on the Ethereum network. However, it does not provide a built-in mechanism for including a payment reference (message) in token transfers. This proposal extends the existing ERC20 token standard by adding minimal methods to include a payment reference in token transfers and transferFrom operations. The addition of a payment reference can help users, merchants, and service providers to associate and reconcile individual transactions with specific orders or invoices. | = 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 --> ERCS/erc-7699.md | 20 | The primary motivation for this proposal is to improve the functionality of the ERC-20 token standard by providing a mechanism for including a payment reference in token transfers, similar to the traditional finance systems where payment references are commonly used to associate and reconcile transactions with specific orders, invoices or other financial records. | = 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 --> ERCS/erc-7699.md | 24 | By extending the existing ERC-20 token standard with payment reference capabilities, this proposal will help bridge the gap between traditional finance systems and the world of decentralized finance, providing a more seamless experience for users, merchants, and service providers alike. | = 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 --> ERCS/erc-7699.md | 30 | Any contract complying with EIP-20 when extended with this ERC, MUST implement the following interface: | = 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 --> ERCS/erc-7699.md | 60 | The paymentReference parameter name also helps to clearly communicate the purpose of the parameter and its role in facilitating the association and reconciliation of transactions. By adopting terminology that is well-established in the financial industry, the proposal aims to foster a greater understanding and adoption of the extended ERC-20 token standard. | = 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 --> ERCS/erc-7699.md | 64 | This extension is fully backwards compatible with the existing ERC-20 token standard. The new functions can be used alongside the existing transfer and transferFrom functions. Existing upgradable ERC-20 tokens can be upgraded to include the new functionality without impact on the storage layout; new ERC-20 tokens can choose to implement the payment reference features based on their specific needs. | = 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 --> ERCS/erc-7699.md | 64 | This extension is fully backwards compatible with the existing ERC-20 token standard. The new functions can be used alongside the existing transfer and transferFrom functions. Existing upgradable ERC-20 tokens can be upgraded to include the new functionality without impact on the storage layout; new ERC-20 tokens can choose to implement the payment reference features based on their specific needs. | = 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 --> ERCS/erc-7699.md | 64 | This extension is fully backwards compatible with the existing ERC-20 token standard. The new functions can be used alongside the existing transfer and transferFrom functions. Existing upgradable ERC-20 tokens can be upgraded to include the new functionality without impact on the storage layout; new ERC-20 tokens can choose to implement the payment reference features based on their specific needs. | = 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 --> ERCS/erc-7699.md | 66 | ERC-20 requires its `Transfer(address indexed _from, address indexed _to, uint256 _value) ` event to be emitted during transfers, thus there will be duplicitous data logged (from, to, amount) in two events. | = 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 --> ERCS/erc-7699.md | 166 | Name Radek Svarz (@radeksvarz), "ERC-7699: ERC20 Payment reference extension" Ethereum Improvement Proposals, no. 7699, April 2024. [Online serial]. Available: https://eips.ethereum.org/EIPS/eip-7699. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.