> For the complete documentation index, see [llms.txt](https://docs.blockdagnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockdagnetwork.io/block-explorer/evm/contract-listing/contract-details/contract-tab/code-tab.md).

# Code Tab

**Compiler Messages**\
Displays warnings, errors, or recommendations generated during the compilation process:

* Examples include missing SPDX license identifier warnings, unused declarations, or best practice suggestions.
* Helps developers understand potential issues or areas for improvement in the code.

**Contract Source Code**\
Shows the Solidity source code of the contract:

* Developers can review the code to understand its logic, methods, and structure.
* Includes key elements such as imports, state variables, functions, and event definitions.
* Helps users verify the contract’s functionality and compliance with coding standards.

**Contract ABI**\
The ABI *(Application Binary Interface)* defines how external applications or users can interact with the contract:

* Lists available functions, their names, and input/output parameters.
* Includes definitions for events triggered by the contract.
* Provides the necessary interface for wallets, dApps, and other integrations.

**Contract Creation Code**\
Displays the bytecode used to deploy the contract:

* Useful for developers, auditors, and miners who want to verify the contract’s deployment data.
* Ensures that the contract was deployed as intended without tampering or errors.

<figure><img src="/files/ExqTmGOQqk3XXCpUi7wi" alt=""><figcaption></figcaption></figure>


---

# 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://docs.blockdagnetwork.io/block-explorer/evm/contract-listing/contract-details/contract-tab/code-tab.md?ask=<question>&goal=<endgoal>
```

`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.