The PTVS Compatibility Program enables RWA platforms, oracle providers, custodians, and PTCE training organizations to formally integrate with the Prop Trust Verified Standard v1.0. Certified entities receive the official “PTVS Compatible” seal, technical support, and listing in the PTVS Ecosystem Directory. This program ensures interoperability, quality assurance, and trust across the PFOI ecosystem.
What is PTVS Compatibility?
PTVS Compatibility is a formal certification that verifies an organization’s technical integration with the Prop Trust Verified Standard v1.0. Unlike simple API access, compatibility certification ensures that your platform, oracle, custodian service, or training program meets the rigorous technical, operational, and governance requirements defined in the PTVS v1.0 Reference Architecture (DOI: 10.5281/zenodo.21719175).
1.1 Why Compatibility Matters
The Physical Oracle Gap cannot be solved by a single entity. It requires an ecosystem of interoperable components: platforms that tokenize assets, oracles that feed data, custodians that safeguard physical evidence, and experts who perform inspections. The PTVS Compatibility Program ensures that all ecosystem participants speak the same technical language, follow the same verification protocols, and maintain the same standards of quality and trust.
1.2 Compatibility vs. Integration
Integration means your system can technically call PTVS APIs or interact with PTVSClaimInjector.sol. Compatibility means your system has been independently verified to correctly implement PTVS v1.0 specifications, handle Verifiable Claims according to the standard, and maintain ongoing compliance with PTVS governance requirements.
Four Compatibility Tiers
The PTVS Compatibility Program offers four distinct certification tiers, each tailored to a specific role in the RWA ecosystem:
Platform Compatible
RWA tokenization platforms that issue asset-backed tokens and need to integrate PTVS verification into their issuance and compliance workflows.
Oracle Compatible
Oracle providers that feed physical verification data into smart contracts, bridging off-chain forensic evidence with on-chain Verifiable Claims.
Custodian Compatible
Digital asset custodians and trust companies that safeguard tokenized RWAs and need to verify physical asset integrity for compliance and risk management.
PTCE Provider Compatible
Training organizations, universities, and professional associations that deliver PTVS certification programs for Prop Trust Certified Experts.
Technical Requirements
Each compatibility tier has specific technical requirements. All tiers must meet the core requirements, plus tier-specific additions:
3.1 Core Requirements (All Tiers)
| Requirement | Specification | Status |
|---|---|---|
| PTVS v1.0 Compliance | Full adherence to PTVS v1.0 Reference Architecture (DOI: 10.5281/zenodo.21719175) | ✓ Required |
| Canonical JSON Support | Correct implementation of canonical JSON serialization (sorted keys, no whitespace, UTF-8) | ✓ Required |
| SHA-256 Hashing | Correct SHA-256 hash generation from canonical JSON (FIPS 180-4) | ✓ Required |
| PTVSClaimInjector Integration | Correct interaction with PTVSClaimInjector.sol (injectClaim, renewClaim, revokeClaim, getClaim) | ✓ Required |
| PTVS Score Calculation | Correct implementation of weighted score formula (Structural 40%, Legal 25%, Environmental 20%, Documentation 10%, Insurance 5%) | ✓ Required |
| Verifiable Claim Lifecycle | Correct handling of claim states: VERIFIED, CONDITIONAL, EXPIRED, REVOKED | ✓ Required |
| Security Audit | Independent security audit of integration code (for smart contracts) | ✓ Required |
| Documentation | Complete technical documentation of integration | ✓ Required |
3.2 Tier-Specific Requirements
| Tier | Additional Requirements |
|---|---|
| Platform |
• ERC-3643/T-REX compatibility • Circuit breaker integration (trading pause, margin calls) • ONCHAINID identity layer integration • MiCA Art. 36 compliance workflow |
| Oracle |
• Real-time Verifiable Claim feeds • Decentralized node architecture • SLA guarantees (99.9% uptime) • Data source verification |
| Custodian |
• Physical asset custody protocols • Quarterly re-audit workflows • Insurance verification integration • Regulatory reporting automation |
| PTCE Provider |
• 40-hour curriculum approval • Examination quality assurance • PTCE mentorship program • Continuing education framework |
Certification Process
The PTVS Compatibility certification follows a rigorous 5-step process designed to ensure technical correctness, operational readiness, and ongoing compliance:
Application & Self-Assessment
Submit the Compatibility Application Form with your organization’s details, technical architecture overview, and self-assessment against PTVS v1.0 requirements. Our team reviews your application within 5 business days.
Duration: 1-2 weeksTechnical Review & Sandbox Testing
Our technical team reviews your integration code, architecture diagrams, and documentation. You deploy your integration in the PTVS Sandbox environment and perform test scenarios with mock Verifiable Claims.
Duration: 2-3 weeksSecurity Audit (if applicable)
For smart contract integrations, an independent security audit is conducted by a PTVS-approved auditor. Critical vulnerabilities must be resolved before proceeding.
Duration: 2-4 weeksProduction Deployment & Monitoring
Deploy your integration to production with PTVS monitoring enabled. Our team monitors Verifiable Claim flows, error rates, and compliance metrics for 30 days.
Duration: 4 weeksCertification & Listing
Upon successful completion, you receive the official “PTVS Compatible” certificate, digital seal, and listing in the PTVS Ecosystem Directory. Annual recertification required.
Duration: 1 weekBenefits of PTVS Compatibility
Why Become PTVS Compatible?
Use the “PTVS Compatible” seal on your website, marketing materials, and regulatory filings to demonstrate compliance with the leading RWA verification standard.
Listing in the official PTVS Ecosystem Directory, visible to banks, insurers, and RWA platforms seeking compatible partners.
Priority access to PTVS technical support team, including integration assistance, troubleshooting, and architecture reviews.
Early access to PTVS v1.1 and v2.0 specifications, allowing you to plan upgrades and maintain competitive advantage.
Observer seat in PTVS Technical Board working groups, influencing the evolution of the standard.
Differentiate from competitors by demonstrating formal compliance with the European standard for RWA verification under MiCA.
Fees & Timeline
PTVS Compatibility certification fees are structured to be accessible while ensuring program sustainability. Fees cover technical review, security audit coordination, ongoing monitoring, and annual recertification:
| Compatibility Tier | Initial Certification Fee | Annual Recertification | Timeline |
|---|---|---|---|
| Platform Compatible |
€15,000
One-time
|
€5,000
Per year
|
8-10 weeks |
| Oracle Compatible |
€20,000
One-time
|
€7,500
Per year
|
10-12 weeks |
| Custodian Compatible |
€25,000
One-time
|
€10,000
Per year
|
10-12 weeks |
| PTCE Provider Compatible |
€10,000
One-time
|
€3,500
Per year
|
6-8 weeks |
Note: Security audit fees (if required) are paid directly to the approved auditor and are not included in the certification fee. Academic institutions and non-profit organizations may apply for fee waivers through the PFOI Research Grant Program.
Apply for PTVS Compatibility
Ready to Become PTVS Compatible?
Join the growing ecosystem of platforms, oracles, custodians, and training organizations that are building the future of RWA verification. Start your compatibility certification today.
Apply Now →Response time: 5 business days
7.1 What to Include in Your Application
When applying, please provide:
- Organization details: Legal name, jurisdiction, website, contact person
- Compatibility tier: Platform, Oracle, Custodian, or PTCE Provider
- Technical architecture: High-level overview of your system and how it will integrate with PTVS
- Timeline: Expected certification completion date
- Previous audits: Any existing security audits or compliance certifications
7.2 Frequently Asked Questions
Can I apply for multiple compatibility tiers?
Yes. Organizations operating in multiple roles (e.g., a platform that also provides oracle services) can apply for multiple tiers. Each tier requires separate certification and fees.
What happens if I fail the technical review?
If your integration does not meet PTVS v1.0 requirements, our technical team will provide detailed feedback and a remediation plan. You can reapply after addressing the issues (no additional fee for first reapplication).
Is the certification transferable?
No. PTVS Compatibility certification is specific to the certified organization and cannot be transferred to subsidiaries, partners, or acquirers without re-certification.
How long is the certification valid?
PTVS Compatibility certification is valid for one year from the date of issuance. Annual recertification is required to maintain compatibility status and continue using the “PTVS Compatible” seal.