Protocol Architecture
Token Standards & Architecture
How ubqty combines ERC standards, identity management, and oracle infrastructure to create permissioned, hierarchical RWA NFTs with real-time risk data.
ERC Standards Stack
UBQTY tokens are built on a layered architecture of Ethereum standards, each providing specific functionality for real-world asset tokenization.
ERC-721
The foundation for non-fungible tokens. Each RWA NFT is unique, representing a specific real-world asset with its own characteristics, valuation, and risk profile.
Provides the base NFT functionality—unique token IDs, ownership tracking, and transfer mechanics.
Every permissioned RWA NFT starts as an ERC-721 token with extended functionality.
ERC-3643
The T-REX protocol standard for compliant security tokens. Enables permissioned transfers, identity verification, and regulatory compliance built into the token itself.
Handles KYC/KYB requirements, transfer restrictions, and compliance rules at the token level.
All UBQTY fractional tokens are ERC-3643 compliant, ensuring only verified participants can hold and trade.
ERC-6150
Hierarchical NFT standard enabling parent-child relationships between tokens. Critical for representing complex asset structures where one asset contains or references others.
Enables asset hierarchies—a company NFT can contain equipment NFTs, IP NFTs, and receivables NFTs as children.
Projects, companies, and complex structures use ERC-6150 to maintain relationships between component assets.
ERC-20
The standard for fungible tokens. When RWA NFTs are fractionalized, the resulting UBQTY tokens are ERC-20 compatible for maximum interoperability.
Provides fungibility, divisibility, and compatibility with DeFi protocols, exchanges, and wallets.
Fractional ownership tokens are ERC-20 wrapped within ERC-3643 compliance for regulated trading.
Permissioned RWA NFT
The core innovation: non-fungible tokens that combine asset uniqueness with regulatory compliance. Every RWA NFT enforces identity verification and transfer restrictions at the protocol level.
KYC/KYB Verification
Every participant must complete identity verification before interacting with permissioned assets. Know Your Customer (KYC) for individuals, Know Your Business (KYB) for entities.
- Document verification and liveness checks
- Business registration and beneficial ownership
- AML/CFT screening and ongoing monitoring
- Jurisdiction-specific compliance requirements
onchainID Integration
Self-sovereign identity standard that stores verified claims on-chain. Your identity travels with you across the protocol without re-verification.
- Decentralized identity claims and attestations
- Selective disclosure of verification status
- Cross-protocol identity portability
- Issuer reputation and claim validity
ZK Credential Proofs
Zero-knowledge proofs enable compliance verification without exposing sensitive data. Prove you're accredited without revealing your net worth.
- Prove accreditation status privately
- Verify jurisdiction without revealing location
- Confirm identity without exposing documents
- Selective attribute disclosure
Transfer Restrictions
Smart contract-enforced rules that prevent non-compliant transfers. Tokens can only move between verified wallets that meet all requirements.
- Whitelist-based transfer validation
- Investor limits and concentration rules
- Lock-up periods and vesting schedules
- Geographic and regulatory restrictions
Hierarchical NFT Structure
Real-world assets are rarely standalone. A company contains equipment, IP, and receivables. A project involves multiple SPVs and asset classes. ERC-6150 enables these relationships on-chain.
Parent NFTs can own child NFTs, creating verifiable hierarchies. When you hold the parent, you have rights over all children. When you transfer the parent, the entire structure moves atomically.
Example Hierarchy
Company NFT
Operating entity with tangible and intangible assets
Equipment NFT
Manufacturing machinery
Patent NFT
Core technology IP
Receivables NFT
Trade receivables pool
Chainlink Oracle Integration
Every RWA NFT is linked to real-time data feeds through Chainlink oracles. Valuations, risk metrics, asset conditions, and market data flow directly to the token—enabling automated pricing, collateral management, and derivatives.
Asset Valuation
Fair Market Value
Current appraised value from certified valuators
Liquidation Value
Expected recovery in forced sale scenario
Replacement Cost
Cost to replace with equivalent asset
Income Value
NPV of expected cash flows from asset
Risk Metrics
Counterparty Score
Creditworthiness of obligors and guarantors
Volatility Index
Historical and implied value volatility
Liquidity Score
Secondary market depth and time-to-sale
Concentration Risk
Exposure concentration metrics
Asset Condition
Physical Condition
Inspection reports and condition assessments
Maintenance Status
Service history and upcoming requirements
Utilization Rate
Usage metrics and capacity utilization
Depreciation Curve
Expected value decline over time
Market Data
Comparable Sales
Recent transactions for similar assets
Market Indices
Sector and asset class benchmarks
Interest Rates
Reference rates for financing calculations
FX Rates
Currency conversion for multi-jurisdiction assets
How Oracle Data Flows
Off-Chain Data
Appraisers, inspectors, and data providers submit asset information
Oracle Network
Chainlink nodes validate, aggregate, and sign the data
On-Chain Update
Verified data is published to the asset's oracle contract
Token Reflection
RWA NFT reads oracle data for real-time valuation and risk
Supported Asset Types
The ubqty protocol supports a wide range of real-world assets, each with specialized tokenization approaches and oracle configurations.
Equipment
Machinery, vehicles, servers
Infrastructure
Data centers, utilities
Intellectual Property
Patents, trademarks, copyrights
Receivables
Invoices, contracts, royalties
Companies
Operating entities, holdings
Projects
SPVs, P3, joint ventures
Explore the protocol
Dive deeper into how ubqty tokenizes real-world assets and creates compliant digital capital.