Contracts

On the Contracts page you will find full information about smart contracts deployed on the STORY network. We provide access to basic data about each contract, including its address, source code and functions. Explorer allows you to quickly search and view the details of contracts, including their status and interaction with other contracts, as well as interact with the contract itself using its functions. This is an ideal place for developers and users who want to gain a deeper understanding of the logic and operation of smart contracts on the platform.

Statistics

Total Contracts: The total number of smart contracts deployed on the blockchain.
Verified Contracts: The number of smart contracts that have undergone a verification process, indicating they meet certain security.

Contract List

Each contract in the list includes the following fields:

Contract Name: A label or identifier for the smart contract, helping users recognize or reference it.
Contract Address: The unique blockchain address where the smart contract is deployed. This is used for interacting with or tracking the contract.
Verification Status: A status indicator, such as a badge, showing whether the contract has been verified.
Timestamp: The time or date of the contract's deployment or when it was verified, providing context on how recent the contract is.

Smart Contract Verification Process

Smart contract verification is essential to ensure the integrity and transparency of the contract's source code. Below are the steps and fields required to verify a smart contract.

Select the Language
- You must specify the language used to write the contract:
  - Solidity: The most widely used language for Ethereum and EVM-compatible contracts.
  - Vyper: An alternative language, known for being more secure and less complex.
Specify Compiler Version
- Choose the exact version of the compiler that was used to compile the smart contract. It is important to match the same version used during deployment to avoid mismatches in bytecode.
- Ensuring the correct version of the compiler is critical as different versions may produce different bytecodes, even for the same source code.
Upload JSON Metadata File
- You will need to provide a JSON file, which contains metadata about the contract. This file typically includes:
  - Contract's source code.
  - Compilation settings such as optimization flags.
  - ABI details.
  - Links to libraries, if any are used.
- This JSON file is usually generated during the contract's deployment or compilation process and ensures that the verification process matches the deployed contract exactly.

Contract details

Contract: The unique blockchain address where the smart contract is deployed. This is used for interacting with or tracking the contract.
Balance: The current balance of the contract, displayed in both token units and USD value. It shows the amount of tokens held by the contract.
Creator: Displays information about the creator or deployer of the contract. This helps in identifying the origin of the contract.
Name: The name of the contract, which helps users recognize or reference the smart contract.
Implementation: This field indicates the version or implementation details of the contract, typically used for upgradeable contracts.
Transactions: A list of recent transactions involving the contract, including the transaction ID, status, date, amount, and fee associated with each.
Verification Status: A badge or indicator showing whether the contract has been verified for authenticity and security.
Timestamp: The date and time associated with contract events, such as deployment or verification. This provides context on the contract’s activity.
View All Contract Files: Users can access the full set of files related to the smart contract, including the source code and any associated metadata. This is useful for auditing the contract or understanding its functionality.
Interact with the Contract: Users can utilize the contract by executing functions directly from the interface, such as triggering specific methods or interacting with its features. This provides direct access to the smart contract's functionality without needing external tools.

The Contracts page provides you with all the necessary tools to analyze and understand smart contracts. Explore the source code, track features and interactions, and stay up to date with changes on the network. We strive to make access to contract information as convenient and understandable as possible so that you can work effectively with STORY

PreviousAssets NextNetwork

Last updated 26 days ago

Smart Contract Verification Process

Smart contract verification is essential to ensure the integrity and transparency of the contract's source code. Below are the steps and fields required to verify a smart contract.

Select the Language

You must specify the language used to write the contract:
- Solidity: The most widely used language for Ethereum and EVM-compatible contracts.
- Vyper: An alternative language, known for being more secure and less complex.

Specify Compiler Version

Choose the exact version of the compiler that was used to compile the smart contract. It is important to match the same version used during deployment to avoid mismatches in bytecode.
Ensuring the correct version of the compiler is critical as different versions may produce different bytecodes, even for the same source code.

Upload JSON Metadata File

You will need to provide a JSON file, which contains metadata about the contract. This file typically includes:
- Contract's source code.
- Compilation settings such as optimization flags.
- ABI details.
- Links to libraries, if any are used.
This JSON file is usually generated during the contract's deployment or compilation process and ensures that the verification process matches the deployed contract exactly.

Contract details

Contract: The unique blockchain address where the smart contract is deployed. This is used for interacting with or tracking the contract.

Balance: The current balance of the contract, displayed in both token units and USD value. It shows the amount of tokens held by the contract.

Creator: Displays information about the creator or deployer of the contract. This helps in identifying the origin of the contract.

Name: The name of the contract, which helps users recognize or reference the smart contract.

Implementation: This field indicates the version or implementation details of the contract, typically used for upgradeable contracts.

Transactions: A list of recent transactions involving the contract, including the transaction ID, status, date, amount, and fee associated with each.

Verification Status: A badge or indicator showing whether the contract has been verified for authenticity and security.

Timestamp: The date and time associated with contract events, such as deployment or verification. This provides context on the contract’s activity.

View All Contract Files: Users can access the full set of files related to the smart contract, including the source code and any associated metadata. This is useful for auditing the contract or understanding its functionality.

Interact with the Contract: Users can utilize the contract by executing functions directly from the interface, such as triggering specific methods or interacting with its features. This provides direct access to the smart contract's functionality without needing external tools.