The RWA Pipeline

DobProtocol provides an end-to-end pipeline for bringing real-world assets on-chain. This page walks through every stage, from initial device submission to secondary market trading.

Pipeline Overview

+===========+     +============+     +=============+     +=============+
|  STAGE 1  |     |  STAGE 2   |     |  STAGE 3    |     |  STAGE 4    |
|           |     |            |     |             |     |             |
|  Submit   |---->| Verify &   |---->| Tokenize &  |---->| Trade &     |
|  Device   |     | Certify    |     | Distribute  |     | Exit        |
|           |     |            |     |             |     |             |
+===========+     +============+     +=============+     +=============+
  Asset Owner       DobValidator      Token Studio       Marketplace /
  uploads specs     TRUFA scoring     Pool creation       DobDex
                    Admin review      Share issuance
                    On-chain cert     Revenue claims

Stage 1: Device Submission

The pipeline begins when an asset owner submits a device or asset for verification.

What Gets Submitted

Asset owners provide structured metadata about their physical assets:

Hardware specifications -- model, manufacturer, serial number, capacity ratings
Operational data -- location, uptime history, network connectivity
Supporting documents -- purchase receipts, installation photos, maintenance records
Firmware information -- version, update history, integrity hashes

Submission Flow

Asset owner connects wallet on validator.dobprotocol.com
Fills out device submission form with required metadata
Uploads supporting documentation
Pays submission fee (covers verification costs)
Submission enters the review queue

At this point, the device is in Pending Review status.

Stage 2: Verification and Certification

DobValidator processes the submission using a combination of AI analysis and admin oversight.

TRUFA Scoring

TRUFA (Trust Factor) is DobProtocol's proprietary scoring model that evaluates submitted devices across multiple dimensions:

Dimension	What It Measures
Hardware Authenticity	Is the device genuine? Are specs consistent with known models?
Operational Viability	Can the device realistically generate the claimed output?
Documentation Quality	Are supporting documents complete and consistent?
Risk Assessment	What is the likelihood of default or misrepresentation?

The TRUFA score produces a numerical rating that helps admins make informed decisions.

Admin Review

After automated scoring, a DobProtocol admin reviews the submission:

Reviews TRUFA score and AI-generated analysis
Cross-references submitted data against known device databases
May request additional information from the asset owner
Makes a final Approve or Reject decision

Certificate Issuance

Upon approval, DobValidator issues an on-chain verification certificate:

Certificate is recorded on the blockchain as immutable proof
Contains device metadata hash, TRUFA score, and approval timestamp
Linked to the asset owner's wallet address
Can be referenced by Token Studio during pool creation

+-------------------+
| Verification      |
| Certificate       |
|-------------------|
| Device ID         |
| TRUFA Score       |
| Metadata Hash     |
| Approved By       |
| Timestamp         |
| Chain / TX Hash   |
+-------------------+

Stage 3: Tokenization and Distribution

With a verified certificate in hand, the asset owner moves to Token Studio to tokenize the asset.

Pool Creation

The asset owner creates a distribution pool -- a smart contract that represents the tokenized asset:

Configure pool parameters:
- Name, ticker symbol, description
- Maximum number of participants
- Access type (buy, request/airdrop, crowdfunding, staking)
- Distribution type (trusted, business, DAM)
- Estimated APR
- Token used for distributions
Define share structure:
- Total shares: 10,000 (representing 100%)
- Creator allocation: how many shares the owner retains
- Available for sale/distribution: remaining shares
Deploy smart contract:
- On Stellar Soroban: WASM contract deployed via Soroban RPC
- On EVM chains: Solidity contract deployed to selected network

Depending on the pool's access type, shares reach investors differently:

Access Type	How Shares Are Distributed
Buy (`p`)	Investors purchase shares at a set price on the marketplace
Request/Airdrop (`rtj`)	Users request access; admin approves and assigns shares
Crowdfunding	Users contribute funds; shares allocated proportionally
Staking (`stk`)	Users stake tokens to earn pool shares over time
QR Code (`qr`)	Shares distributed via QR code scanning (events, physical locations)

Revenue Distribution

As the underlying asset generates revenue, the pool creator distributes earnings to shareholders:

V1 Distribution (Push-Based)

Admin deposits revenue
        |
        v
Admin calls distribute()
        |
        v
Contract loops all shareholders
        |
        +---> Shareholder A receives proportional share
        +---> Shareholder B receives proportional share
        +---> Shareholder C receives proportional share
        +---> ... (up to ~500 shareholders)

V2 Distribution (Pull-Based -- Current)

Admin deposits revenue
        |
        v
Admin calls create_distribution()   <-- O(1) operation
        |
        v
Distribution round created on-chain
        |
  (each shareholder claims independently)
        |
        +---> Shareholder A calls claim()  --> receives share
        +---> Shareholder B calls claim()  --> receives share
        +---> Shareholder C calls claim()  --> receives share
        +---> ... (scales to 10,000+ shareholders)

V2 introduces additional controls:

Time-gating: Minimum interval between distributions (default 12 hours)
Claim windows: Configurable delay before claims open
Round expiry: Unclaimed funds can be reclaimed after expiration
Auto-scheduling: Set recurring distributions with defined intervals

Commission Structure

DobProtocol charges the following commissions:

Event	Commission	Deducted From
Distribution	0.5%	Distribution amount (at creation time)
Share Purchase	1.5%	Purchase price

Stage 4: Trading and Exit

Once shareholders hold shares, they have multiple options for secondary trading and exit.

Marketplace (Secondary Trading)

Token Studio includes a built-in marketplace where shareholders can list their shares for sale:

Seller creates a listing specifying:
- Number of shares to sell
- Price per share
- Payment token accepted
Buyer browses marketplace listings and purchases:
- Buyer pays in the specified token
- Smart contract transfers shares to buyer
- Seller receives payment minus commission
Settlement happens on-chain:
- Share ownership updated in the contract
- Transaction recorded in dob_buy_sale_transactions
- Both parties' dashboards updated after sync

DobDex (Zero-Slippage Exit)

For larger positions or immediate exits, DobDex provides a zero-slippage trading experience:

Quoted price equals execution price, regardless of order size
Liquidity provided by a network of nodes rather than an AMM curve
Designed specifically for RWA tokens where predictable pricing matters
Available at dex.dobprotocol.com

DobLink (Embedded Investment)

Asset owners can embed a DobLink widget on their own websites, allowing investors to:

View pool details and performance metrics
Purchase shares directly from the asset owner's domain
Track their investment without visiting DobProtocol directly

Complete Pipeline Example

Here is a concrete example walking through the entire pipeline:

1. Solar Farm operator submits 50kW installation to DobValidator
                                    |
2. TRUFA scores it 87/100, admin approves, certificate issued on Stellar
                                    |
3. Operator creates "SolarFarm Alpha" pool on Token Studio
   - 10,000 shares total (100%)
   - Operator keeps 3,000 shares (30%)
   - 7,000 shares available for purchase at $10/share each
   - Monthly distribution schedule
                                    |
4. 45 investors buy shares through the marketplace
   - Investor A buys 500 shares ($5,000 = 5% ownership)
   - Investor B buys 200 shares ($2,000 = 2% ownership)
   - ... etc
                                    |
5. Month 1: Solar farm generates $2,000 in revenue
   - Operator deposits $2,000 to pool contract
   - Creates distribution round
   - DobProtocol takes 0.5% ($10) commission
   - $1,990 available for claims
   - Investor A (5%) claims $99.50
   - Investor B (2%) claims $39.80
   - ... etc
                                    |
6. Investor A wants to exit early
   - Lists 300 of 500 shares on marketplace at $12/share
   - Investor C buys all 300 shares for $3,600
   - Or: Investor A exits via DobDex at zero slippage

Pipeline Status Tracking

Each asset moves through defined states as it progresses through the pipeline:

State	Location	Meaning
Submitted	DobValidator	Awaiting TRUFA scoring
Under Review	DobValidator	Admin reviewing submission
Certified	DobValidator	Certificate issued, ready for tokenization
Rejected	DobValidator	Submission did not pass verification
Pool Created	Token Studio	Smart contract deployed
Active	Token Studio	Shares issued, distributions flowing
Distributing	Token Studio	Active distribution round in progress
Trading	Marketplace	Shares listed for secondary sale

Pipeline Overview​

Stage 1: Device Submission​

What Gets Submitted​

Submission Flow​

Stage 2: Verification and Certification​

TRUFA Scoring​

Admin Review​

Certificate Issuance​

Stage 3: Tokenization and Distribution​

Pool Creation​

Share Issuance and Access​

Revenue Distribution​

V1 Distribution (Push-Based)​

V2 Distribution (Pull-Based -- Current)​

Commission Structure​

Stage 4: Trading and Exit​

Marketplace (Secondary Trading)​

DobDex (Zero-Slippage Exit)​

DobLink (Embedded Investment)​

Complete Pipeline Example​

Pipeline Status Tracking​