Content rights · AI collaboration · Settlement

Content with provenance.Collaboration that pays.

An independent permissioned chain, an AI compute network and smart contracts, working together so that content has a source, use is licensed, work can be verified and payment can be settled.

See how one order flows Explore the three ledgers

Project showcase · Network proposed, not yet live

Rights ledgerWork ledgerSettlement ledgerOne order number links all three ledgers, every step can be checkedSample order, not real business

The essentials

Rights, collaboration and settlementinfrastructure for the AI economy.

Content with provenance
Give content an identity, link its sources and evidence, and register rights statements.
Use with permission
The same content can carry different licenses for different purposes, users and terms.
Work with proof
Work receipts record what happened. Acceptance records show whether the result met this task's requirements.
Payment on agreed terms
Every payment can be traced to the license, work and delivery behind it.

Where we start

Starting with photos and images,validating every step in one order.

For photo agencies, licensed image libraries, content platforms and enterprise image users. Link originals, version history, source materials and use licenses, then provide search, deduplication, classification and licensed delivery.

For
Who uses it
- Photo agencies
- Licensed image libraries
- Content platforms
- Enterprise image users
Connects
What it connects
- Originals
- Version history
- Source materials
- Use licenses
Provides
What it provides
- Search
- Deduplication
- Classification
- Licensed delivery

The first phase takes on institutional image tasks with a clear scope, validating rights, processing, acceptance and settlement within the same order.

Rights ledger · Work ledger · Settlement ledger

One independent chain, three linked ledgers.Traceable from license to settlement.

The three ledgers are not three chains. They are three kinds of linked records on the same chain. Original files, model inference and payments are handled by off-chain services, and the chain holds only key records, business rules and state coordination.

Records content sources and licenses, making clear whether this use is allowed.

Use licenseL-2026-0417

Valid

PurposeInternal search

Term12 months

TerritoryMainland China

Model trainingNot licensed

Source documents 3Rights statement 1Review opinion 1

Records who did what processing, and whether the results passed acceptance.

Image curation taskT-0417

Running

Dedupededup-v3

Classificationclf-v2.1

TaggingIn progress

Version linkingQueued

Quality checkAwaiting acceptance

Checks licenses and acceptance results to confirm which fees can be paid.

Order settlementO-0417

Conditions met

License scope matchedRights ledger

Delivery acceptedWork ledger

Settlement conditions metAwaiting payment

Payment channel receiptNot received

One number links every record.

When the enterprise customer receives a delivery, it can check each item within its permissions: which content versions are included, which license applies, what processing was done, who completed acceptance and how far the fees have progressed.

Original files, contracts and prices are visible by role. The chain keeps only digests, references and key states.

C-0417Content version
L-0417Use license
R-0417Work receipt
A-0417Acceptance record
S-0417Settlement status

Rights ledgerWork ledgerSettlement ledger

How one order flows

From a batch of images to a finished order.Connecting not only content, but the business behind it.

From registration to delivery, one photo may involve a photo agency, an image agent, AI service providers, compute nodes, reviewers and an enterprise customer, linking three kinds of information: rights, work and settlement. In the sample order below, an enterprise customer needs a set of images for internal visual search.

Order O-0417Internal search · Image curation

In progress

01Content registration
12 originals, 3 source files, rights statement
Rights ledger
02Use license
Internal search · 12 months · No model training
Rights ledger
03AI processing
Dedupe, classification and tagging · clf-v2.1
Work ledger
04Task acceptance
Spot check to agreed criteria, all 12 pass
Work ledger
05Licensed delivery
Files, license details and processing report
Settlement ledger
06Settlement as agreed
Conditions met, awaiting payment receipt
Settlement ledger

One independent chain · Three linked ledgers

Rights ledgerSourced · Licensed

C-0417Registration record

L-0417License match

Work ledgerRecorded · Accepted

R-0417Work receipt

A-0417Accepted

Settlement ledgerDelivered · Settled

D-0417Delivery proof

S-0417Conditions met

Sample workflow, not real business data

01 / 06Content registrationRights ledger12 originals, 3 source files, rights statement

02 / 06Use licenseRights ledgerInternal search · 12 months · No model training

03 / 06AI processingWork ledgerDedupe, classification and tagging · clf-v2.1

04 / 06Task acceptanceWork ledgerSpot check to agreed criteria, all 12 pass

05 / 06Licensed deliverySettlement ledgerFiles, license details and processing report

06 / 06Settlement as agreedSettlement ledgerConditions met, awaiting payment receipt

01
Content registrationRights ledger
The content provider submits images, source materials and a rights statement, and the system creates a record for each file version. Completing registration does not mean the rights have been verified.
02
Use licenseRights ledger
The enterprise customer states the purpose, term, delivery format and whether the content may pass to third parties. Only content that meets the license conditions can enter processing and delivery for this order.
03
AI processingWork ledger
The order is split into tasks such as deduplication, classification and tag generation, and assigned to suitable AI service providers. Each task is bound to the input versions cleared for use, and records the model, compute node and output.
04
Task acceptanceWork ledger
The reviewer checks the results against the agreed scope, format and quality criteria. An AI service provider saying the work is done does not count as acceptance.
05
Licensed deliverySettlement ledger
The enterprise customer receives the files together with license details, a version list and a processing report. The access gateway controls downloads and API access according to valid licenses, and records the scope and time of delivery.
06
Settlement as agreedSettlement ledger
Once the conditions are met, fee details and a settlement basis are generated, and payment is made and reconciled through the connected payment channel. Content providers earn license income, AI service providers and reviewers earn service fees.

Use cases

Different use cases,the same business structure.

Learn more

Content recognition, curation and processing methods change with the media type, but the shared business structure stays the same: clear licenses, traceable tasks, deliveries that can be accepted and fees that can be checked.

Design assets
From file handoff to traceable collaboration
For design agencies and brand content teams, linking drafts, revisions, commission materials, scope of use and delivery records.
Design assets
From file handoff to traceable collaboration
For design agencies and brand content teams, linking drafts, revisions, commission materials, scope of use and delivery records.
AI helps organize assets and versions, and the system records processing and review. Downstream teams can check the delivered content and licenses, instead of just receiving a zip file.
Digital artwork archives
Connecting artwork records with expert opinion
Build digital archives for artworks, linking photos, scans, capture records, historical materials and expert opinions.
Digital artwork archives
Connecting artwork records with expert opinion
Build digital archives for artworks, linking photos, scans, capture records, historical materials and expert opinions, supporting curation, version linking and archive handover.
The system records physical identity, attribution, physical custody and image licenses separately. The artwork use case is adapted through dedicated capture and professional services, and image similarity is not used in place of authenticating the physical work.
AI data services
Delivered with licenses and processing records
For enterprise customers and AI application teams with clear data needs: deduplication, classification, tagging and dataset preparation for content cleared for use.
AI data services
Delivered with licenses and processing records
For enterprise customers and AI application teams with clear data needs: deduplication, classification, tagging and dataset preparation for content cleared for use.
Each delivery binds the content list, versions, purposes, licenses and processing records. Internal search, model training, public display and redistribution are licensed separately according to the actual business.
This use case can reuse the image processing foundation. What is opened up depends on licensed materials, delivery standards and pilot needs.
Video and audio
Extending the same business model
Later, through media adaptation, records extend to clips, time ranges, audio tracks, subtitles and derivative versions.
Video and audio
Extending the same business model
Later, through media adaptation, records extend to clips, time ranges, audio tracks, subtitles and derivative versions.
Recognizing, organizing and processing audio and video differs from images, but the business structure of licensing, tasks, acceptance and settlement stays the same.

Technology

One independent permissioned chain,working with off-chain services.

Learn more

Blockchain does not replace every business system. It provides verifiable shared records for what different participants all rely on: identity, licenses, work records, acceptance status and settlement basis.

Independent permissioned chain
Plans to build an independent permissioned chain with its own network identity, node admission, contracts and governance rules.
Independent permissioned chain
ORDIVA plans to build an independent permissioned chain with its own network identity, node admission, contracts and governance rules. Issuing an asset on another public chain is not treated as a substitute for building this network.
The base layer favors mature blockchain technology. R&D focuses on the rights data model, task records, license enforcement and settlement coordination, not on building a new consensus mechanism in the first phase.
As partner organizations join, independently operated validator and audit nodes are introduced step by step. The project running several nodes internally and multiple organizations each controlling their own nodes and keys are governance forms for different stages.
Smart contracts and business rules
Smart contracts manage identity, content and evidence references, rights statements, task acceptance, license conditions, settlement status and dispute processes.
Smart contracts and business rules
Smart contracts mainly manage identity and roles, content and evidence references, rights statement status, task and acceptance records, license conditions, settlement status, and dispute and correction processes.
Conditions that can be stated precisely are enforced by the system. Steps that need institutional verification, external payment confirmation or expert opinion are handled by explicitly authorized services that submit the corresponding receipts.
Original contracts, machine-readable conditions and the referenced policy versions stay linked. A model cannot generate new terms on the fly in place of the parties' consent, and cannot change payment or rights status on its own.
Off-chain content and data systems
Original images, contracts, creation records, full reports and sensitive materials go into controlled storage. The chain keeps the necessary digests and key states.
Off-chain content and data systems
Original images, contracts, creation records, full reports and sensitive materials go into controlled storage. Business databases and index systems support search, access control and daily operations, while the chain keeps the necessary digests and key states.
Search of private institutional materials, cross-institution matching, public display and model training each have their own use permissions. The system does not automatically add files submitted for duplicate checks to training data.
Access and payment connections
License status connects to file downloads, API calls or data delivery through the access gateway.
Access and payment connections
License status connects to file downloads, API calls or data delivery through the access gateway. License changes affect later controlled access as agreed. Copies that have already left the system fall under the relevant contracts and dispute handling.
Funds are handled by connected payment channels. The settlement basis on the chain and the channel's payment receipts are reconciled separately. System bookkeeping is not designed as a promise to hold customer funds unconditionally.
Open access and portability
Plans to connect image libraries, enterprise asset systems, AI service platforms and review systems through APIs and SDKs.
Open access and portability
ORDIVA plans to connect image libraries, enterprise asset systems, AI service platforms and review systems through APIs and SDKs. Enterprise customers can call registration, search, license checks, tasks and delivery within their existing workflows.
The system supports exporting data packages and verification information for important evidence and business records according to permissions, without depending on a single front end to view them.

Revenue

Revenue comes from services actually delivered,not registration counts or token prices.

Learn more

The total a customer pays may include fees owed to content providers, AI service providers or reviewers. ORDIVA's revenue and participants' revenue are accounted for separately, and the full order amount is not counted as platform revenue.

Institutional management services
Content management, licensing workflows, review collaboration, document storage and reconciliation for content providers, enterprise customers and reviewers.
Institutional management services
Content management, licensing workflows, review collaboration, document storage and reconciliation for content providers, enterprise customers and reviewers. Pricing can be designed around institutional accounts, usage capacity and service levels.
This revenue meets ongoing management needs and does not depend on enterprise customers making a content transaction every time.
AI processing services
Services around deduplication, classification, search, curation and data preparation, priced by task, volume or agreed outcome.
AI processing services
Services around deduplication, classification, search, curation and data preparation, priced by task, volume or agreed outcome.
In-house processing bears the actual compute, storage, quality review and retry costs. Third-party processing is settled according to the actual service relationship. Pricing reflects quality requirements and delivery responsibility, not just the number of model calls.
Licensing, delivery and settlement coordination
License checks, workflow coordination, controlled delivery, fee reconciliation and proof export, for a platform or protocol service fee.
Licensing, delivery and settlement coordination
For business completed through ORDIVA or connected channels, ORDIVA provides license checks, workflow coordination, controlled delivery, fee reconciliation and proof export, and charges a corresponding platform or protocol service fee.
Fees are based on the business steps actually covered. ORDIVA does not by default charge for all external use that the system cannot verify.
API and enterprise integration
Standard APIs, SDKs, institutional onboarding and workflow adaptation for third-party platforms.
API and enterprise integration
Standard APIs, SDKs, institutional onboarding and workflow adaptation for third-party platforms. Enterprise customers can purchase by call volume, subscription or agreed implementation support.

Commercial growth means raising the quality and frequency of use of deliverable services, not simply increasing registrations, compute capacity or book transaction volume.

Current stage and roadmap

First close the loop,then expand content and node coverage.

Learn more

The current materials present the project to investors and partners and do not mean a production system is live. The business demo on this site has not actually run AI, issued formal licenses, written to a chain or made payments.

Stage 1
Rights and content foundation
Build focus
Content identity, evidence management, institutional permissions, license data structures, an independent test network
Resulting capability
Able to manage a batch of content with its sources, statements and scope of use
Stage 2
AI collaboration and acceptance
Build focus
Classification and dedupe, search, task scheduling, work receipts, review workbench
Resulting capability
Able to run specified tasks, link the process and complete acceptance
Stage 3
Delivery and settlement pilot
Build focus
License enforcement, access gateway, delivery proof, fee rules, payment receipts and dispute process
Resulting capability
Able to complete real licensing, processing, delivery and payment reconciliation
Stage 4
Network and use case expansion
Build focus
Independent institutional nodes, external AI services, API access, media adaptation
Resulting capability
Able to let more participants collaborate under the same rules

The goal of the next stage is for a task initiated by a real need to complete licensing, processing, acceptance, delivery and settlement reconciliation, with records that clearly explain what happened at each step.

Content with provenance.Collaboration that pays.

Rights, collaboration and settlementinfrastructure for the AI economy.