DobValidator
DobValidator is an AI-powered verification platform that provides trusted attestation for real-world assets (RWAs). It bridges the gap between physical infrastructure and blockchain-based tokenization by offering a structured review, scoring, and certification pipeline.
Live at: validator.dobprotocol.com
Purpose
Before a real-world asset can be tokenized and traded on DobProtocol, it needs to be verified. DobValidator answers the fundamental question: Is this asset real, compliant, financially viable, and environmentally sound?
The platform produces a TRUFA score -- a composite metric across four dimensions -- and issues a tamper-proof certificate anchored on-chain. This certificate can then be linked to distribution pools on Token Studio or referenced by the DobDex for oracle-backed pricing.
Architecture
DobValidator is a standalone application with its own frontend and backend:
| Layer | Technology | Details |
|---|---|---|
| Frontend | Next.js 15 | React-based UI with server components |
| Backend | Express.js | RESTful API with middleware-based auth |
| ORM | Prisma | Type-safe database access |
| Database | PostgreSQL | Hosted on Google Cloud SQL |
| Storage | Google Cloud Storage | Document and file attachments |
| Auth | Wallet-based | Freighter (Stellar) and MetaMask (EVM) |
Cross-Platform SSO
DobValidator shares authentication with the main DobProtocol platform through a cross-subdomain SSO mechanism:
- A
dob_auth_tokencookie is set on the.dobprotocol.comdomain - JWT payloads include
walletAddress,source, andproviderfields - Users who authenticate on
home.dobprotocol.comare automatically signed in onvalidator.dobprotocol.comand vice versa
Core Pipeline
The verification process follows a linear pipeline from submission to on-chain attestation:
Submission --> Review --> Scoring --> Certificate --> On-Chain Attestation
(User) (Admin) (TRUFA) (SHA-256) (Stellar / EVM)
- Submission -- Asset owners fill out a multi-step form describing the device, location, financials, and supporting documents.
- Review -- Validators (admins) review the submission data and attached evidence.
- Scoring -- Each submission is scored across the four TRUFA dimensions (0--100 each), producing a composite score.
- Certificate -- A SHA-256 hash is computed over the canonical submission data and scores, then a PDF certificate is generated with a QR code for public verification.
- On-Chain Attestation -- The certificate hash and TRUFA scores are written to the
DOBValidator.solsmart contract on supported EVM chains, and optionally to Stellar Soroban.
Wallet-Based Authentication
DobValidator uses wallet signatures for authentication rather than passwords:
- Freighter -- For Stellar-native users. Signs a challenge message with the user's Stellar keypair.
- MetaMask -- For EVM-native users. Signs a challenge message via
personal_sign.
No email or password is required. The wallet address serves as the user's identity across the platform.
Integration with Token Studio
Once a certificate is issued, it can be linked to a distribution pool on Token Studio:
- Pool creators can attach a certificate hash during pool creation or afterward via the pool dashboard
- The TRUFA score badge appears on pool cards across the marketplace
- The certificate hash is stored in the
poolstable (validator_certificate_hash,validator_overall_score, etc.) - A public verification endpoint allows anyone to verify a certificate's authenticity
Deployment Targets
On-chain attestation is supported on the following networks:
| Network | Contract | Status |
|---|---|---|
| Ethereum Sepolia | DOBValidator.sol | Deployed |
| Polygon Amoy | DOBValidator.sol | Deployed |
| Base Sepolia | DOBValidator.sol | Deployed |
| Base Mainnet | DOBValidator.sol | Deployed |
| Stellar Soroban | Planned | In development |
Next Steps
- Submission Process -- How asset owners submit data for verification
- TRUFA Scoring -- The four-dimensional scoring methodology
- Certificates -- Certificate issuance, verification, and on-chain anchoring