# Sourcify

This provider exposes tools and data accessible through its parent verticals. Use the example prompts as inspiration for your queries.

**Slug:** `sourcify`

**Description:** Smart contract verification across EVM chains: whether a contract's source code is verified, its compiler, deployer, proxy implementation, functions and source, and decoding of function selectors.

## Verticals

This provider is available in the following verticals:

- [Dev](https://kirha.com/verticals/dev.md)
- [Crypto](https://kirha.com/verticals/crypto.md)

## Example prompts (non-exhaustive)

- `Is the DAI contract 0x6B175474E89094C44Da98b954EedeAC495271d0F verified, and on which chains?`
- `Who deployed the USDT contract on Ethereum and which compiler was used?`
- `What does the function selector 0x095ea7b3 do?`
- `Get the verified contract details of USDC 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Sourcify: proxy, implementation and functions`

## Available tools in this provider

Open a tool to see its input and output schemas.

### [`checkContractVerification`](https://kirha.com/providers/sourcify/checkContractVerification.md)

Check whether a smart contract address has verified source code on Sourcify, on one EVM chain or across every chain where it is deployed, with the match quality. Use it to vet a token, protocol or contract before interacting with it: unverified code cannot be audited.

### [`getVerifiedContract`](https://kirha.com/providers/sourcify/getVerifiedContract.md)

Details of a smart contract verified on Sourcify: contract name, compiler and settings, license, deployer and deployment transaction, whether it is a proxy and its implementation, its functions and events, and optionally the main source file. Use it to understand what a contract does and who deployed it.

### [`decodeFunctionSelectors`](https://kirha.com/providers/sourcify/decodeFunctionSelectors.md)

Decode EVM function selectors (4 bytes, or the first 4 bytes of calldata) and event topics (32 bytes) into readable signatures such as transfer(address,uint256), using the Sourcify signature database. Use it to understand what a transaction or a signature request will actually call, e.g., spotting a hidden approve or setApprovalForAll.

-----

**Tags:** smart contracts, verification, ethereum, evm, security, web3, crypto

[< Back to providers list](https://kirha.com/providers.md)