Contracts

Smart contract configuration is the easiest way to set up your analytics at Spock.

You just need to provide smart contract details, and Spock will start syncing the data. The data syncing time can vary depending on the number of wallets that have interacted with the contracts, the number of transactions, and the age of the contracts.

By providing smart contract addresses, you will unlock the majority of data points in Understand section, which includes:

Let's explore some common scenarios related to the structure of smart contracts.

Case #1

Single Instance Contract

If there is one contract that handles all the transactions, then just provide the contract address and ABI. You can leave the ABI field blank if the contract is already verified on Etherscan.

Example : Consider an example of the Unipilot Staking contract which handles all stake, un-stake, and reward redemption transactions.

Case #2

Several Contracts Deployed By An EOA

If there are multiple smart contract addresses associated with the same given ABI deployed by an EOA, you need to toggle the "several contracts deployed by an EOA" option to "Yes". This will prompt you to provide additional contract addresses as input separated by commas. Example: Let's consider an example of the Compound cDAI market contract. In this case, we have multiple market contract addresses that correspond to the same cDAI ABI.

Case #3

Several Contracts Deployed By A Factory

If the provided smart contract address is deployed by a factory contract, then you need to toggle the "several contracts deployed by a factory" field to "Yes". This allows us to retrieve the factory contract address, and other sibling contract addresses associated, and extract the data for the entire ecosystem.

Example : Let's consider the example of the Uniswap v3 USDC/ETH pool contract. By toggling the "several contracts deployed by a factory" field to "Yes", you will be able to retrieve data for all Uniswap v3 pools.