Lenses

At The Grid, we use lenses as a conceptual framework to organize data that's relevant to different user needs. Think of lenses as different perspectives or filters through which you can view Web3 data, similar to how a camera lens focuses on specific subjects.

The 9 Core Lenses

The Grid currently organizes data through eight primary lenses:
    Profiles - Contains information about the core profile and tags.
    Products - Contains information about products, its deployment info and any other relationships.
    Assets - Contains information about assets, its deployment info and any other relationships.
    Entities - Contains information about entities.
    Socials - Contains social media accounts and community channels.
    URLs - Contains web addresses and online resources.
    Smart Contract Deployments - Contains information about smart contract deployments, this can either be an asset or product deployments.
    Attributes - A general lens where attributes can be attached to various other lenses. Each attribute has strict def of where it can be used.
    Internal Helpers - System and metadata utilities


How Lenses Work: A Practical Example

Jerry walks up to the store.... He sees it through a profile lens, with it contains many things:

Profile Lens: The Quick Overview

Jerry approaches a store. This lens shows him:
  • What is the name of the profile?
  • What is the profile type and sector?
  • What does the profile do?
Use when: You need a quick high level information of what an profile is.


Product Lens: Specific Offerings

Jerry explores what's inside. This lens reveals:
  • What each product does
  • How it describes itself
  • What it works with
  • Launch date and status
Use when: You need details about specific tools or services.


Asset Lens: Tokens & Currencies

Jerry checks payment options. This lens shows:
  • Which currencies are supported
  • Whether they issued their own token
  • Network compatibility
  • Token type and technical details
Use when: You're researching tokens or checking payment methods.


Entity Lens: Legal Structure

Jerry verifies legitimacy. This lens reveals:
  • Legal registration details
  • Corporate structure
  • Licenses and compliance
  • Geographic presence
Use when: You need to verify legitimacy or conduct due diligence.


Socials Lens: Community Channels

Jerry wants to join the community. This lens provides:
  • Official social accounts (Twitter, Discord, Telegram, GitHub)
  • Account status (Active, Inactive)
  • Social types
Use when: You want to find official channels or assess community presence.


URLs Lens: Web Presence

Jerry needs resources. This lens shows:
  • Primary websites
  • Documentation and white papers
  • Web applications
  • Blogs and support pages
Use when: You need direct links to resources.


Smart Contract Helpers Lens: Blockchain Data

Jerry needs on-chain details. This lens provides:
  • Contract addresses
  • Deployment networks
  • Token standards (ERC-20, SPL, etc.)
  • Deployment history
Use when: You need technical blockchain information.


Attributes Lens: Custom Properties

Jerry discovers unique features. This lens captures:
  • Custom characteristics
  • Special designations
  • Project-specific metadata
Use when: You need specialized or unique information about an entity.


Internal Helpers Lens: Data Architecture

Jerry (as a developer) builds with the data. This lens shows:
  • Data relationships
  • System identifiers
  • How everything connects
Use when: You're building applications or need to understand data structure.