Changelog

TLDR: TGS12 introduces product multi-typing via a new productClassifications junction, an isSupported qualifier on product-country links, a typed-values overhaul of the attributes system, and inverse labels on the relationship enums.

A product is no longer limited to a single type: each product now holds one or more classifications, with exactly one marked primary. Country support links can now state that a product explicitly excludes a market, not just that it serves one. Attribute types now declare how their values are stored — boolean, free text, or a controlled-vocabulary option — via the new valueTypes enum. And two relationship enums can now be labelled correctly from either direction.

Product types in the UI: one product, many types

A product no longer just one type — it has types. Each product carries one or more classifications, with exactly one marked primary. The primary type is the product's identity; the rest are secondary. Sub-product types are represented this way too: not a separate hierarchy, just additional classifications on the same product.

In practice this changes very little on screen and a lot underneath. Wherever you showed a product's type before, show the primary. Cards, list rows, and headers look exactly as they did. Secondary types appear as supporting chips on detail views, answering "what else does this product do" without competing with the identity.

The payoff is in filtering: a product matches a type filter if any of its classifications match. A non-custodial wallet with secondary On/Off Ramp and Swaps classifications now surfaces for users filtering on ramps or swaps, instead of being invisible because it could only hold one type. Grouping and counting still use the primary only, so each product appears once and totals stay honest.

productClassifications {
  id
  productTypeId
  isPrimary
  productType {
    id
    name
  }
}

Relationships that read correctly from both ends

A relationship enum used to store only one side's phrasing. assetSupportTypes.name is written asset → product (Supported by, Native to, Managed by), so rendering the same row on a product page produced a label that read backwards. rootRelationshipTypes had the same problem between parent and child profiles.

Both enums now carry a nullable inverseName. Pick the label by the direction you are rendering: name when you are looking from the side the enum was written for, inverseName when you are looking from the other. It is nullable, so fall back to name when it is unset rather than rendering an empty label.

Migration note: products.productTypeId keeps working through the deprecation window — the change is additive. When you migrate, resolve a product's canonical type via productClassifications where isPrimary = 1.

Every profile on thegrid.id now uses the redesigned profile page. The layout leads with who the profile is: name, type, sector and status. We also improved how lenses are loaded The Grid models: products, assets, entities, socials and URLs.

The Network Portal gained an Insights section: published, data-driven reads over The Grid's dataset. The first insight, Where stablecoins are used, drills from high-level views down to individual profiles.

TGS11 introduces structured country and region data for products, a new ordinal ranking field on gridRank, and a firstClaimedAt timestamp on roots.

Products can now declare which countries they are available in, and every country links to a UN M49 sub-region (e.g. South America, Eastern Asia) for regional grouping and filtering.

Known limitation: country.region.parentRegion cannot be traversed in a single query yet — query parentRegionId and match it yourself.

TGS10 introduces a flexible attributes system that allows profiles, products and assets to have type-specific properties without requiring schema changes. The system keeps The Grid structured while providing the flexibility needed to scale attributes at any point.

The attributes system consists of core tables that follow The Grid's existing patterns.

TGS9 is our most significant user-focused update, addressing visual presentation and marketing capabilities.

Profile relationships finally solve the "multiple profiles problem" with systematic linking: the new rootRelationships table links a child profile to its parent with a typed relationship from the rootRelationshipTypes enum.

GraphQL subscriptions are now enabled on the API endpoint.

TGS7 moves on-chain data into dedicated tables and introduces typed product–asset relationships — e.g. Bitcoin is native to the Bitcoin network; Circle issues USDC. It also introduces the root concept: the canonical identity anchor every profile's data hangs off.

TGS6 adds tags to The Grid Schema — the foundation for classifying profiles by events, ecosystems, communities and technology.

Products that support many chains — Chainalysis for on-chain investigation, QuickNode for node hosting, wallets and custodians for asset management — can now express that directly: products.productSupports links a product to each product it supports.