error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-321 | 19 | The advancement of blockchain technology and the proliferation of decentralized applications (dApps) underscore the need for a dynamic, interoperable protocol for managing smart contracts. A standardized mechanism for tokenization, exchange, and aggregation is necessary. This EIP, with its ERC-321Metadata extension, proposes a structured interface for lifecycle management of smart contracts within marketplaces. | = 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-321 | 34 | ERC-321 is designed with backward compatibility in mind, ensuring seamless interaction with existing ERC standards and the broader Ethereum ecosystem. | = 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-321 | 106 | Securing the implementation of ERC-321 is crucial, focusing on managing contract ownership and metadata integrity. Adhering to smart contract security best practices and opting for decentralized storage solutions for metadata are essential to mitigate risks. | = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`

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

validation found errors :(