> For the complete documentation index, see [llms.txt](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-49-not-conforming-to-eip-standards.md). # Tutorial 49: Not Conforming To EIP standards {% hint style="info" %} [**Book an audit with Zokyo**](https://www.zokyo.io/) {% endhint %} Ethereum Improvement Proposals (EIPs) are guidelines that establish standardized methods for smart contract design and interaction on the Ethereum network. These standards, such as EIP-2981, EIP-165, EIP-2612, and others, define the structure and functionality for contracts to ensure consistency, security, and interoperability across the ecosystem. However, when developers fail to adhere to these established standards, various risks can be introduced into decentralized applications. Non-conformance can lead to **bugs**, **incompatibilities with external systems**, and **security vulnerabilities** that can undermine the integrity of the contract. For example, missing replay attack protection in cross-chain environments or failing to implement proper domain separation in signed transactions can expose contracts to exploits that attackers may leverage across different chains or applications. In this section, we will discuss how failing to conform to EIP standards such as EIP-2981, EIP-165, EIP-2612, and others can introduce specific bugs and vulnerabilities. We will also cover the importance of standards like EIP-155 for replay attack protection and EIP-1967 for storage management, highlighting real-world examples of vulnerabilities caused by these oversights. Understanding the significance of following these standards is crucial for developers looking to build robust and secure decentralized applications. Conforming to widely accepted EIPs not only ensures compatibility with other systems but also protects contracts from well-known attack vectors and reduces the risk of unintended behavior in production environments. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-49-not-conforming-to-eip-standards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.