Skip to main content

DobValidator

DobValidator is the verification platform that produces TRUFA scores for tokenizable real-world assets, anchors them on-chain on EVM and Stellar, and feeds the validated USD price into the DobDex oracle.

Live at: validator.dobprotocol.com

What it does​

Before an asset can be tokenised through Token Studio or priced by DobDex, the validator answers: Is this asset real, compliant, financially viable, and environmentally sound? The output is a TRUFA score — Trustless Revenue Utility & Flow Automation — across four scoring dimensions plus an overall composite, attached to a hash of the canonical submission and written on-chain.

What you interact with​

The validator is a standalone application with three public surfaces:

SurfaceWhere to find it
Web UIvalidator.dobprotocol.com — submit assets, track status, download certificates
Public verify endpointGET /api/public/certificate/verify/:hash — anyone can verify a certificate by hash
On-chain registryThe DOBValidator contract (EVM) and the Projects contract (Soroban). Anyone can read TRUFA scores directly from chain

Authentication is wallet-based — sign a challenge with your wallet (Freighter for Stellar, MetaMask for EVM) and you get a session cookie scoped to .dobprotocol.com so the same session works across home.dobprotocol.com and validator.dobprotocol.com.

Pipeline​

Submission --> Review --> TRUFA Scoring --> Certificate (SHA-256) --> On-Chain Attestation
   (User)     (Admin)     (4 dims + overall)   (PDF + QR)              (EVM + Soroban)
  1. Submission — asset owner fills the multi-step form, uploads docs, pays the fee.
  2. Review — validators see the full submission; the AI assistant pre-scores and surfaces discrepancies.
  3. Scoring — four dimensions plus an overall composite (each 0–100, validated <=100 on-chain). Validators finalise the scores.
  4. Certificate — SHA-256 over the canonical submission + scores + wallets; PDF generated with QR linking to the public verify URL.
  5. On-chain attestation — addProject(hash) then setProjectApproved(hash, scores) on DOBValidator.sol (EVM) and the equivalent add_project / set_project_approved on the Soroban Projects contract.

On-chain attestation surfaces​

NetworkContract
Ethereum Sepolia, Polygon Amoy, Base Sepolia, Base MainnetDOBValidator
Stellar Soroban (Testnet + Mainnet)Projects — live on Soroban (entry points: add_project, set_project_approved, set_project_rejected, get_trufa_score, is_whitelisted).

The Soroban contract uses a whitelist model: only whitelisted addresses may approve / reject; admin manages the whitelist.

Wallet-based authentication​

  • Freighter — Stellar users; signs a challenge with their Stellar keypair.
  • MetaMask — EVM users; signs via personal_sign.

No password is required. The wallet address is the user identity.

Integration with Token Studio​

Once a certificate is issued, it can be linked to a Token Studio pool. The pool record stores validator_certificate_hash, validator_submission_id, validator_overall_score, validated_at, validation_status. The pool dashboard shows the TRUFA breakdown and a link to the public verify endpoint (GET /api/public/certificate/verify/:hash).

Next steps​