The Grid organizes all Web3 project data through four lenses: Profiles, Products, Assets, and Entities, plus three shared sections that appear across all of them: URLs, Socials, and Media. Each lens captures a different dimension of your project, and together they create a connected, discoverable picture of who you are and what you've built.
Understanding lenses helps you fill out your profile correctly and get the most out of The Grid's network
This article explains the conceptual model, why things are structured the way they are, and how the pieces connect. For a step-by-step editing walkthrough, see Editing Your Profile on The Grid
The Four Lenses
1. Profile Information
Your Profile is your project identity on The Grid. It answers the question: "Who are you?"
Your profile is organized into multiple lenses. Each one plays a role in how your project is represented across The Grid's network. Think of it as the homepage of your project — everything else (products, assets, entities) hangs off of it.
You'll find the core identity fields for your profile:
Profile Name: Your organization's display name as it appears across The Grid.
Profile Type: The type of entity (e.g., Company, DAO).
Profile Sector: The industry your organization operates in (e.g., Payments, Finance, Infrastructure, Gaming).
Profile Status: Your current operational status (e.g., Active, Announced).
Founding Date: When your organization was founded.
Short Description: A concise summary of what your organization does. This is used across directories and partner listings.
Long Description: A more detailed explanation of your organization, products, and services.
Marketing Description: An optional marketing-focused description for promotional contexts.
Tagline: A brief tagline
Tip: Keep your Short Description factual and concise, it's the one that appears most often across partner integrations. Avoid marketing fluff here; save that for the Marketing Description field.
Your Profile is the top-level lens that everything else connects to. Think of it as the "homepage" of your project in The Grid.
2. Products
The Products lens answers: "What have you built?"
Every distinct offering your project provides is a product: whether it's a wallet, exchange, protocol, dApp, bridge, or developer tool. You'll find the core identity fields for your product:
Product Name: The product name
Product Type: Product classification (e.g., On/Off Ramp, Wallet, DEX)
Product Status: Current status (e.g., Beta, Live, etc.)
Launch Date: When was the product launched
Description — What the product does
Is Main?: Whether this is your primary product (Yes/No)
Media: Product-specific branding assets. When uploading, select the correct Media type from the dropdown, same as the profile media section
Socials: Product-level social accounts
One profile can have multiple products. For example, a profile has both an On/Off Ramp product and a Wallet; those are two separate products under the same profile.
The URLs section on the right side of your product lets you manage all web links associated with your product. Each URL has a Type label, similar to Profile Info.
Product & Asset Support
Products are the most relationship-heavy lens. Each product has:
Product Deployments: Where the product is deployed (chain, type, asset standard)
Products Support: Bidirectional relationship mapping:
"This product uses": Other products/chains your product depends on (grouped by type, e.g., L1, L2)
"This product is used by": Other products that use your product
Related Assets: Assets connected to this product, with Support Type (e.g., "Supported by"), Asset Type, and Asset Status
Why this matters: The Products Support and Related Assets sections create bidirectional relationships. When you add the Solana chain or USDT as a related asset, your product automatically appears in those ecosystem directories. The more complete these are, the more discoverable you become.
3. Assets
The Assets lens answers: "What tokens or digital assets have you issued?"
If your project has created tokens, stablecoins, governance tokens, or other digital assets, this is where they live.
When you click into an asset, you'll find:
URLs: Asset-specific links
Asset Deployments: Where the asset is deployed onchain (Deployed On, Type like "Mint", and Asset Standard like "SPL" or "ERC-20")
Smart Contracts: Contract addresses with Name, Address, and Deployment Date
Derivative Assets: Assets derived from this one (e.g., wrapped versions like wETH, liquid staking tokens like stETH). This creates a parent-child relationship between the original asset and its derivatives.
Base Assets: The inverse of derivative assets. If this asset is a derivative, you link it back to the original base asset here.
Related to Products: This is the asset-side view of product relationships. It shows which products use or manage this asset, with a Support Type (e.g., "Managed by" for issuance platforms, or "Supported by" for protocols), the Product Type, and Product Status.
These derivative/base relationships are important for data accuracy; they let The Grid (and its data consumers) understand the full lineage of an asset rather than treating wrapped or staked versions as entirely separate tokens.
4. Entities
The Entities lens answers: "What's your legal structure?"
This covers the corporate and legal side of your project. The Entities table shows Name, Type, Country, and Address.
This matters for compliance-focused partners, institutional users, and regulatory contexts. Not every project fills this in fully right away, but it becomes increasingly important as you grow.
The entity editor includes:
Entity Name: Full legal name (e.g., "BONBYTE TECHNOLOGY sp. z o.o.")
Trade Name: The name your company trades under
Entity Type: Classification (e.g., Startup, Foundation, Corporation, DAO)
Local Registration Number: Your local company registration number
Tax Identification Number: Tax ID if applicable
Address: Registered address
LEI Number: Legal Entity Identifier (if applicable)
Country: Country of registration
Date of Incorporation: When the entity was legally formed
URLs: Entity-specific URLs (with Type label "Entity")
Socials: Entity-level social accounts
Shared Sections: URLs, Socials, and Media
These three sections appear at every level: profile, product, asset, and entity, because each lens can have its own web presence, social accounts, and branding.
1. URLs
The URLs section on the right side of your profile, product, asset, and entity. Each URL has a Type label:
Main: Your primary website
Documentation: Technical docs, API references, or Tokenomics
Product / Asset Info / Entity: Context-specific labels inside product, asset, and entity editors
Extra source: Any additional relevant links (Linktree, terms of use, etc.)
Why this matters: URLs are used by partner integrations and data consumers to verify and link to your project. Having the right URLs on the right lens (e.g., a product-specific docs link on the product, not just on the profile) ensures data accuracy at every level.
2. Media / Branding
Media appears at the profile, product and asset level, with four types:
Logo on white: Full rectangle logo (wordmark + icon) for white/light backgrounds. Preferably SVG. If PNG, minimum 256px height.
Logo on black: Full rectangle logo for dark backgrounds. Preferably SVG. If PNG, minimum 256px height.
Icon: A square profile icon that works on any background, in full colour. Preferably SVG or PNG. If PNG, minimum 256px height.
Header: A header banner image. Should be PNG, 1500px × 500px.
Important: Make sure your icon has a solid (non-transparent) background and full color. Transparent icons cause display issues across partner platforms. The icon is the most-used asset as it appears in search results, directories, and wallet listings everywhere.
3. Socials
Each lens can have its own social accounts, tracked with:
Social Name: Your handle as it is (eg, SolanaFndn or OfficialTether)
Social Type: Platform (e.g, Telegram, Twitter / X, LinkedIn)
Social Status: Whether the account is Active or Inactive
URL: Direct link to the account
Why this matters: Social links serve as verification signals and discovery pathways. They also feed into data quality checks during validation; broken or outdated social links are one of the most common reasons changes get flagged.
Tip: If your product has its own Twitter or Telegram community separate from the profile's, add those socials on the product, not just the profile.
How Lenses Connect
The real power of lenses is in the relationships they create between each other. The Grid isn't just a directory: it's a relationship map of the entire Web3 ecosystem.
Here's how the connections work:
Products → Chains (via Products Support): In the Products Support section, when you add chains under "This product uses:" (e.g., BNB Smart Chain, Ethereum Mainnet, Bitcoin Network under L1; Polygon PoS under L2), you will automatically appear in those chain ecosystem directories or platform/services using that ecosystem-specific data
Products → Assets (via Related Assets): In the Related Assets section, when you add an asset like USDT with Support Type "Supported by," you automatically appear in stablecoin directories and partner listings.
Products → Products (via Products Support): The "This product uses" and "This product is used by" sections create bidirectional product-to-product relationships, showing the full dependency map.
Assets → Chains (via Asset Deployments): In Asset Deployments, when your token is deployed on Solana Mainnet with standard SPL, that chain relationship is tracked and visible across the network.
Profile → Everything: Your profile is the parent. All products, assets, and entities connect back to it. The sum of all their relationships determines your overall visibility across the network.
These are bidirectional relationships, meaning the connection works both ways. You don't just show that you support Ethereum; Ethereum's ecosystem page shows you as a project building on it.
Why This Matters
The lens structure gives you three key benefits:
Single source of truth. Update your data once on The Grid, and it propagates across all connected directories, wallets, explorers, and partner platforms. No more manually submitting your project to dozens of ecosystem pages.
Automatic discoverability. Every relationship you add increases where and how your profile shows up. Ecosystem partners, investors, and users find you through the connections in your data, not just by searching your name.
Grid Rank. The more complete and connected your profile, the higher your Grid Rank. This influences how prominently your project appears across the network. Adding supported chains, assets, and deployments directly increases your rank.
Tips for Getting the Most From Lenses
Be comprehensive with Products. If your profile offers multiple products (a wallet and an on/off ramp, for example), add them separately. Each product creates its own set of relationships.
Don't skip Assets. Even if your token feels minor, adding it connects you to other projects that support it.
Map all chains, not just your primary one. If your product uses BNB Smart Chain, Ethereum Mainnet, and Polygon PoS, add all of them; each one is a new discovery pathway.
Keep Entities up to date. Legal information matters for compliance-focused partners and institutional users searching the directory.
Fill in all three description fields. The Short Description, Long Description, and Marketing Description serve different purposes across different integrations.