Veris

We Breaking Down Walls in Real-World Asset Tokenization

Today, most “tokenized RWA” projects are just marketplaces—opaque, hardcoded, with legal/compliance data buried in PDFs and high friction for users.

Veris is fundamentally different:

A programmable, composable metadata, compliance, cross-jurisdiction protocol for RWAs—public, on-chain, and developer-friendly.

An Infra, not a marketplace: A full protocol for publishing, registering, and exploring any asset (property, fund, legal wrapper) as structured, queryable data—using The Graph’s Knowledge Graph Framework (GRC-20 standard).

Composable legal & compliance: Not just asset details, but all the relationships—owners, managers, jurisdictions, audits, KYC tiers, legal wrappers— open, and on-chain interoperable.

Seamless USDC gas UX for users: On Veris, asset purchase and registry interactions can be paid using USDC via Circle Paymaster—no native tokens required.

Metadata Explorer & Developer Tools: Our UI exposes everything: decoded proto metadata, legal docs, full entity/ownership graphs, on-chain proofs, and pointer relationships—plus developer exports and API endpoints.

For RWA protocols: Instantly publish, update, and verify asset metadata, legal docs, and compliance rules—no more random PDFs or hidden admin panels.

For auditors & regulators: Inspect the full graph of entities, docs, compliance controls—on-chain and provable.

For developers/integrators: Reuse and compose asset metadata on any EVM chain—no lock-in, open-source, powerful APIs for integration, analytics, or dashboards.

For users: Explore, verify, and interact with real assets, pay gas in USDC, and avoid complex technical friction.

This isn’t just another marketplace. It’s open, programmable RWA protocol infra—composable, auditable, and truly accessible. Breaking down the walls for the next era of on-chain assets.

Core Architecture

Smart Contracts:

We deployed an upgradable ERC-721 (PropertyToken) contract for each property.

The MetadataRegistry contract maps each property token address to a content identifier (CID) on IPFS.

Metadata Publishing:

We use @graphprotocol/grc-20-ts to encode complex, multi-entity metadata (legal, compliance, audit, manager, KYC, jurisdiction, etc) as GRC-20 “edits.”

The edit (protobuf binary, not JSON) is published to IPFS via the GRC-20 Knowledge Graph.

The resulting CID is then stored on-chain in the registry, linked to the property token address.

Backend:

Node.js/Express API server for:

Publishing metadata (triggering GRC-20 edit, pinning to IPFS, registering CID on-chain)

Fetching and decoding metadata from IPFS and GRC-20 proto

Integrates with a local IPFS node for reliable file availability (not relying solely on public gateways).

Supports Circle Paymaster (ERC-4337) for gas abstraction (users pay gas in USDC, not native tokens).

Frontend:

React + Vite (SPA).

Connects to the backend API for live on-chain/IPFS metadata.

Inspector panel: shows raw and decoded metadata, legal/audit pointers, pointer mapping.

Dynamic property explorer—users can browse, inspect, and verify any RWA token’s metadata.

Partner Technologies & Integrations

The Graph Knowledge Graph (GRC-20): Allowed us to encode and structure property metadata as rich, composable, and queryable data, rather than flat JSON. This benefits cross-project composability, not just simple viewing.

Circle Paymaster (ERC-4337): Lets users interact with the registry using USDC for gas, removing the friction of acquiring native tokens.

Web3.storage/IPFS: Used for decentralized storage, but we ensure our backend pins and serves the correct protobuf-encoded files, guaranteeing accessibility even if public gateways are slow.

Notable Hacks & Lessons

Proto Decoding: GRC-20 metadata is stored as protobuf binary, not plain JSON, requiring a custom backend decoder so the frontend can present human-readable data.

Pointer dereferencing: To reconstruct entity graphs (like owner → auditor → jurisdiction), we implemented a recursive dereferencing function, so even deeply-nested or linked data is usable in the UI.

Multi-network support: All configs (contracts, RPC, registry) are .env-driven for easy redeploy to new chains (Polygon Amoy, OP Sepolia, etc).

Why it matters

This is not a property marketplace. It’s a trustless, programmable metadata layer for RWA tokens, with full compliance and transparency built-in.

Developers, not just users, can inspect, query, and build on top of our data layer—just like Etherscan, but for RWA metadata.