# Verifiable Claims & Where to Verify Each

Every claim DCS makes resolves to a public URL. Use this map to fact-check anything you plan to publish.

If a claim you've heard isn't on this list, email **press@dcsai.ai** with the specific claim and we'll either provide the verification URL or correct the claim.

---

## On-chain (Base mainnet — anyone can verify, no permission required)

| Claim | Verification URL |
|---|---|
| TRDWorkerSBT contract deployed | https://basescan.org/address/0xbDd1f5fC349D9a8EfCEb07Edbd491233b2540f5F |
| Soul-bound (non-transferable) | Read the contract source on Basescan; check that `transferFrom` reverts |
| Genesis Agent #0001 minted to founder wallet | Filter Transfer events on the above contract |
| Total Agent SBTs minted | Call `totalSupply()` on the contract OR check dcslabs.ai/stats live counter |
| Treasury settlement on Base | Filter Treasury transactions — addresses in Investor Package PDF appendix |

## npm registry (public, anonymous access)

| Claim | Verification URL |
|---|---|
| `@dcsplatform/mcp-server` published v0.1.1 | https://www.npmjs.com/package/@dcsplatform/mcp-server |
| `@dcsplatform/r2-verify` published v0.1.1 | https://www.npmjs.com/package/@dcsplatform/r2-verify |
| Weekly downloads | npmjs.com page → "Stats" tab — public |
| Source code | Click "Repository" link on each package page |

## Public web (anyone can hit and confirm)

| Claim | Verification URL |
|---|---|
| Open Provenance Standard published | https://dcslabs.ai/standard |
| Mint funnel live | https://dcslabs.ai/mint |
| Live telemetry dashboard | https://dcslabs.ai/stats |
| Sovereign Memory landing | https://dcslabs.ai/memory |
| Demo playground | https://dcslabs.ai/demo |
| Security disclosure policy | https://dcslabs.ai/security |
| Corporate one-pager | https://dcsai.ai |
| Launch blog post | https://dcsai.ai/blog/coming-live |
| Press kit | https://dcsai.ai/press |
| Investor Package PDF | https://dcsai.ai/Investor_Package.pdf |
| Investor One-Pager PDF | https://dcsai.ai/DCS_AI_Investor_OnePager.pdf |
| Privacy policy | https://dcsai.ai/privacy |
| Terms of Service | https://dcsai.ai/terms |
| DPDP §8 compliance statement | https://dcsai.ai/dpdp |
| About | https://dcsai.ai/about |
| FAQ | https://dcsai.ai/faq |
| Careers | https://dcsai.ai/careers |
| Competitive comparison | https://dcslabs.ai/compare |

## Source code (GitHub — public, MIT-licenced)

| Claim | Verification URL |
|---|---|
| R+2 standard source repo | https://github.com/DCS-LabsAI/r2-standard |
| r2-verify source | https://github.com/DCS-LabsAI/r2-verify |
| dcsai.ai source | https://github.com/DCS-LabsAI/dcsai.ai |
| dcslabs.ai source | https://github.com/DCS-LabsAI/dcslabs.ai |
| MIT license | Each repo's `LICENSE` file |
| No patents | Each repo's `LICENSE` includes explicit no-patent statement |

## Standards-body submissions (semi-verifiable)

| Claim | Verification |
|---|---|
| Anthropic Standards Program submission sent | Email metadata available on request to press@dcsai.ai; submission date May 22, 2026 |
| MeitY (India) submission sent | Email metadata available on request; submission date May 22, 2026; recipient secretary@meity.gov.in |
| ISRO submission sent | Email metadata available on request; submission date May 22, 2026; recipient pro@isro.gov.in |
| Status of each | Email press@dcsai.ai for current status — we share what we're allowed to share publicly |

## Business / company facts

| Claim | Verification |
|---|---|
| DCS AI Technologies L.L.C registered in Dubai | UAE Dubai DED record — available on request to press@dcsai.ai |
| Founded 2026 | DED registration date |
| Solo founder | Cap table — available to verified investors via data room |
| Pre-seed / seed round open | Investor Package PDF + investors@dcsai.ai for verification |
| $18-28M pre-money | Investor Package PDF |
| ~41 days of build | GitHub commit history starting April 10, 2026 (visible in DCS-LabsAI org) |

## Technical claims

| Claim | Verification |
|---|---|
| Ed25519 signatures (RFC 8032) | R+2 spec §5 + source code in lib/verify.js |
| RFC 8785 canonical JSON | R+2 spec §6 + uses `canonicalize` npm package |
| pgvector for memory | Public stats at dcslabs.ai/stats + architecture in About page |
| 1536-dim embeddings (text-embedding-3-large) | Demo at dcslabs.ai/demo + spec |
| 0.524 average cosine similarity | dcslabs.ai/stats live metric |
| 47ms P50 query latency | dcslabs.ai/stats live metric |
| 99.5%+ uptime (30-day) | Better Stack status page (link in stats footer) |
| 2.5% Treasury fee | Smart contract code + Investor Package §6 |

---

## What you CAN'T independently verify (yet)

These claims rely on private commercial / legal / regulatory data and require direct communication for verification:

- Specific marquee pilot conversations (we share names only with consent)
- Specific investor pipeline composition (we share aggregates, not individual fund names)
- Specific revenue figures pre-launch (pre-revenue; post-launch metrics live at /stats)
- Specific employee compensation (not disclosed pre-Series A)
- Internal financial projections beyond what's in the Investor Package PDF

For any of these, email **press@dcsai.ai** with what you're trying to verify and the angle. We typically respond same-day during IST business hours.

---

## Common false claims about DCS — please don't repeat these

- ❌ "DCS is launching a token" — we are NOT launching a token. The SBT identity contract is non-transferable. Treasury settles in USDC.
- ❌ "DCS is an AGI company" — we are an infrastructure company. We don't train models. We don't compete with Anthropic / OpenAI / DeepMind on capability.
- ❌ "DCS competes with LangChain" — we sit underneath LangChain. LangChain agents can use DCS for memory and provenance.
- ❌ "DCS is closed-source" — the standard and reference implementations are MIT-licenced.
- ❌ "DCS data is stored on a blockchain" — only agent IDENTITY is on-chain (SBT). Memory and action receipts are off-chain (Postgres + pgvector + optional IPFS pinning).

If you've seen any of these claims in coverage, please contact press@dcsai.ai so we can request a correction.
