If your organization has deployed smart contracts onchain or runs products across multiple blockchains, mapping those deployments on The Grid ensures your project is properly connected to the chains you build on. Deployment data also powers future integrations like price feeds and TVL tracking.
This guide explains where and how to add deployment information to your profile.
What Is a Deployment?
A deployment is a record of where your product or asset lives on-chain. It can be a smart contract address tied to a specific blockchain, or simply a record that your product operates on a given chain.
For example:
A token contract deployed on Solana Mainnet as an SPL token with a Mint address
The same token bridged to Ethereum with a separate ERC-20 contract
A wallet product deployed across BNB Smart Chain, Ethereum Mainnet, and Polygon PoS
Each of these is a distinct deployment.
Two Types of Deployments
Deployments are tracked in two different places in the admin portal, depending on what you're mapping:
1. Product Deployments
When you edit a product, you'll find a Product Deployments section with a table showing:
Deployed On: Which blockchain (e.g., BNB Smart Chain, Ethereum Mainnet)
Type: The deployment type
Asset Standard: The token standard used on that chain (if applicable)
Click Add to add a new product deployment. Use this for products like dApps, protocols, exchanges, or wallets that operate on specific chains.
Note: Product Deployments are separate from Product Supports. Deployments track where your product is deployed onchain. Product Supports (the "This product uses" section) tracks the broader relationship, which chains and products your product depends on. For maximum discoverability, fill in both.
2. Asset Deployments
When you edit an asset, you'll find an Asset Deployments section with a table showing:
Deployed On: Which blockchain (e.g., Solana Mainnet)
Type: The contract type (e.g., Mint)
Asset Standard: The token standard (e.g., SPL, ERC-20)
Below that, there's a Smart Contracts section where you add the actual onchain addresses:
Name: An optional label for the contract
Address: The onchain contract address
Deployment Date: When the contract was deployed
Click + Add row to add more smart contracts.
This is particularly important for tokens that exist on multiple chains. For example, if your stablecoin is deployed on Ethereum as ERC-20 and on Solana as SPL, each deployment should be listed separately with its respective contract address.
How to Add Product Deployments
Navigate to the Products section of your profile.
Click on the product you want to edit.
Scroll to the Product Deployments section.
Click Add to add a new deployment.
Select the chain your product is deployed on, the type, and the asset standard (if applicable).
The progress is saved automatically. Your changes will enter the validation queue.
How to Add Asset Deployments
Navigate to the Assets section of your profile.
Click on the asset you want to edit (or click Add Asset to create a new one).
In the Asset Deployments section, add each chain your asset is deployed on, with the deployment type and asset standard.
In the Smart Contracts section, click + Add row for each contract:
Enter the contract address
Add the deployment date if known
Optionally add a name label
While you're in the asset editor, also check these related sections:
Derivative Assets: If this asset has wrapped or staked versions (e.g., wETH, stETH), link them here.
Base Assets: If this asset is a derivative, link it back to the original base asset.
Related to Products: Connect the asset to products that manage or support it (with Support Types like "Managed by" or "Supported by").
The progress is saved automatically. They'll enter the validation queue.
Why Deployment Mapping Matters
Discoverability
Deployment data creates the same bi-directional relationships as product supports. When you map an asset deployment to Solana Mainnet, your project shows up in Solana ecosystem directories. When you map to Ethereum, you appear in Ethereum listings. Each deployment is a new pathway for discovery.
Data Verification
Onchain contract addresses are publicly verifiable. Adding them strengthens the credibility of your profile, and partners & users can independently confirm your deployments on block explorers.
Tips for Mapping Deployments
Map every chain. If your token exists on 8 chains, add all 8 deployments, not just the main one.
Set the correct Asset Standard. Use the right standard for each chain: ERC-20 for Ethereum/EVM chains, SPL for Solana, TRC-20 for Tron, etc.
Keep deployment dates accurate. This helps build a timeline of your project's growth and multi-chain expansion.
Update when you launch on new chains. Every new deployment should be reflected on your profile promptly.
Don't forget Product Deployments too. If your product (not just your token) operates on multiple chains, map those in the Product Deployments section as well.
Common Questions
Q. What if my product isn't a smart contract?
Not every product needs contract-level deployment data. If you run a centralized service (like an exchange or payment gateway), you'd map chain support through the Products Support section ("This product uses") rather than adding smart contract addresses.
Q. What about the difference between Product Deployments and Product Supports? Product Deployments track the specific onchain deployment details (chain, type, standard). Product Supports ("This product uses") track the broader relationship map, which chains and products your product integrates with. Both contribute to discoverability, so fill in both when applicable.
Q. What about testnet deployments?
The Grid tracks mainnet deployments only. Testnet contracts should not be added to your profile.
Need Help?
If you're unsure how to structure your deployments or which contracts to include, reach out through the chat widget on network.thegrid.id