Contract Tab

The Contract Tab provides detailed technical information about a smart contract, enabling users to analyze its functionality, verify its integrity, and explore its components. This tab is divided into the following sections:

• FR 11.007a: Compiler Details This section displays information about the contract’s compilation and verification process:

  • Verification Status: Indicates whether the contract is partially or fully verified.

  • Contract Name: The identifier for the contract (e.g., TICS).

  • Compiler Version: Specifies the Solidity compiler version used for the contract (e.g., v0.8.20).

  • EVM Version: Indicates the specific version of the Ethereum Virtual Machine (EVM) used to compile and execute the smart contract. This helps developers ensure compatibility between the contract's bytecode and the runtime environment on the blockchain, and is essential for understanding opcode behavior and potential upgrade constraints.

  • Optimization Enabled: States whether optimization was applied during compilation (e.g., False).

  • Optimization Runs: The number of optimization runs performed (e.g., 200).

  • Verified At: The date and time when the contract was verified (e.g., 23rd Jul 2024, 15:29:17).

  • Deployed Bytecode: The final compiled bytecode of the smart contract that is actually deployed on-chain. It includes initialization logic stripped out after deployment and reflects the active contract code stored at the contract address. Useful for verification, auditing, and comparing on-chain code with source code repositories.

• FR 11.007b: 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.

• FR 11.007c: 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.

• FR 11.007d: 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.

• FR 11.007e: Contract Creation Code Displays the bytecode used to deploy the contract:

  • Useful for developers, auditors, and validators who want to verify the contract’s deployment data.

  • Ensures that the contract was deployed as intended without tampering or errors.