# Smart Contract Deployments by Chain: New Contracts per Day > Smart contract deployments by chain per day: new EVM contracts, Solana programs, Sui and Aptos packages, NEAR and TON contracts, deployers and factory share. Markdown copy of https://voltfincrypto.com/apps/smart-contract-deployments-by-chain **Question:** How many new smart contracts are deployed on each chain per day? - Kind: Dashboard in Voltfin Vantage - Topic: [Layer 1 chains](https://voltfincrypto.com/topics/chains) - Chains: Multi-chain, Ethereum, Base, Arbitrum, BNB Chain, Polygon, Avalanche, Monad, Sonic, Berachain, HyperEVM, Plasma, Solana, Sui, Aptos, NEAR, TON - Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is. Every new smart contract is created on-chain by a transaction, so deployments are a measure of building that anyone can check. This dashboard counts them on each covered chain per day: EVM contracts from creation calls, Solana programs, Sui and Aptos packages, NEAR contracts and new TON contracts, along with how many distinct accounts deployed them and how many came from factories. Deployments do not compare across virtual machines: a Solana program serves many users, while an EVM chain deploys a contract for every token, pool or smart wallet. So each chain is read against its own history, and the share created by factories and launchpads is shown apart from deployments by developers. Every count links to the transactions behind it. ## Blueprint ### Overview New EVM contracts, Solana programs and Move packages, with the accounts that deployed them. - **EVM contracts, latest day** (count): Contracts created on the covered EVM chains on the latest complete UTC day, from create and create2 calls in traces. - **Solana programs, latest day** (count): New programs deployed on Solana on the latest complete day, through the upgradeable loader and loader-v4. - **Move packages, latest day** (count): Packages published on Sui and on Aptos on the latest complete day, shown per chain. - **Distinct deployers, latest day** (count): Accounts that signed at least one deployment on the latest complete day, following factory calls back to the signer. - **New EVM contracts by chain** (count): Contracts created each day over the selected period on each covered EVM chain, stacked by chain. ### By chain Factory share, upgrades, first-time deployers and each chain's own figures. - **Factory share** (%): EVM contracts created by other contracts rather than directly by accounts, as a share of the latest day's EVM deployments. - **Upgrades, latest day** (count): Solana program upgrades and Sui and Aptos package upgrades on the latest complete day, counted apart from new deployments. - **First-time deployers** (count): Accounts that deployed a contract for the first time on a given chain on the latest complete day. - **Top 10 deployers' share** (%): The share of the latest day's EVM deployments signed by the ten most active deploying accounts. - **Deployments by chain**: Each covered chain with its deployments, distinct deployers, factory share and upgrades over the last 30 days, under the rule that fits its virtual machine. Filters: Chain (Every covered chain); Period (Last 30 days, 90 days or a year). ## How it will be measured - A deployment is counted once, on the day its creating transaction succeeded: create and create2 calls in EVM traces, new programs on Solana, published packages on Sui and Aptos, DeployContract actions on NEAR and new contracts on TON. - Counts are never added across virtual machines, since a Solana program, a Move package and an EVM contract are different units; EVM chains are summed only with each other. - Factory share is the part of EVM contracts created by another contract rather than by an account directly; launchpads, DEXs and wallet factories can create them in large numbers, so the share sets automated deployments apart. - Distinct deployers are the accounts that signed each day's deployments, found by following factory calls back to the signer, and every figure carries a receipt with the block and transaction. ## Data it needs - `chain_activity_daily` (to build): Transactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions. - `address_labels` (to build): Labels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers. - Source: EVM chains: create and create2 calls in execution traces, with the creator and whether it is a contract - Source: Solana: upgradeable loader DeployWithMaxDataLen and Upgrade instructions, and loader-v4 deployments - Source: Sui: Publish and Upgrade commands in programmable transaction blocks; Aptos: code::publish_package_txn calls - Source: NEAR: DeployContract actions; TON: messages carrying a state_init that deploy a new contract - Source: Factory, launchpad and wallet factory labels, recorded with their source ## Questions ### Do contract deployments measure developer activity? Partly. A deployment is a verifiable on-chain act, but one team can deploy many contracts, and factories such as token launchpads create contracts automatically. The dashboard separates factory deployments and counts distinct deployers, which says more about how many builders are active than raw counts do. ### Why are Solana programs counted differently from EVM contracts? On Solana, code lives in programs that many users share, and a new token needs no new program: it is an account of the existing token program. EVM chains deploy a contract for each token or smart wallet. Solana's program count therefore runs far lower for the same activity, so each chain is read against its own history. ### What is a factory contract? A contract that creates other contracts, such as a DEX creating a pool for each new pair, a launchpad creating each token or a wallet factory creating each smart account. The factory share tile shows how much of each day's EVM deployments come from them. ### Are contract upgrades counted as deployments? No. Upgrading a Solana program or a Sui or Aptos package changes code at an existing address, so those upgrades are counted on their own. On EVM chains a new implementation behind a proxy is a new contract and counts as a deployment, while repointing the proxy does not. ### Which chains are covered? EVM chains including Ethereum, Base, Arbitrum, BNB Chain, Polygon, Avalanche, Monad, Sonic, Berachain, HyperEVM and Plasma, plus Solana, Sui, Aptos, NEAR and TON, each counted under the rule that fits its virtual machine. More chains are added as their traces are built. ## Glossary - **create2**: The EVM operation that deploys a contract at an address computed in advance from the deployer, a salt and the code. - **Factory**: A contract whose job is to deploy other contracts, such as pools, tokens or smart accounts. - **Program**: Solana's name for deployed code; programs hold no state of their own and serve every account that uses them. - **Package**: A published bundle of Move modules on Sui or Aptos, the unit of deployment on those chains. ## Related apps - [Daily Transactions by Blockchain: Leaderboard](https://voltfincrypto.com/apps/daily-transactions-by-blockchain) - [Active Addresses by Blockchain: Daily and Monthly](https://voltfincrypto.com/apps/active-addresses-by-blockchain) - [New Layer 1 Blockchains: Activity Since Mainnet](https://voltfincrypto.com/apps/new-layer-1-blockchains) - [Smart Contract Upgrade Tracker: Proxy and Owner Changes](https://voltfincrypto.com/apps/smart-contract-upgrade-tracker) - [Layer 1 Blockchain List: Activity, Fees and Staking](https://voltfincrypto.com/apps/layer-1-blockchain-list) - [Blockchain Revenue Rankings: Monthly League Table](https://voltfincrypto.com/apps/blockchain-revenue-rankings) Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F