Conflicts & disclosures
Every conflict, on the record.
An auditor's conflicts don't disappear by being unmentioned. This page is the standing register: what Basis is paid for, what relationships exist, what can never be bought, and how bias would be detected if it occurred. It updates as facts change; absence of an entry means the relationship does not exist.
What can never be bought — at any price, on any rail
- Favorable labels, score changes, or CRI treatment
- Suppression, delay, or de-prioritization of findings
- Evidence-grading or source-treatment influence
- Requester-defined claim lists — requesters name a project or topic; Basis selects the claims
- Priority that changes evidence standards (queue position orders work, never outcomes)
- Corrections — free, token-less, account-less, permanently
Funded & requested work
Any record produced under paid or token-funded request carries a permanent disclosure: who requested, their stated affiliation, and how it was funded — with the standard restatement that evidence standards are identical for requested and unrequested work. A free editorial track (draft floor: ≥50% of capacity, reported publicly once Stage 2 volume exists) guarantees coverage is never gated by payment. Requester affiliation is a required intake field; self-requests are disclosed with extra prominence.
The Virtuals venue conflict
Basis covers Virtuals Protocol in its registry — including a flagship metric currently labeled unverified — and is simultaneously preparing to use Virtuals as a distribution rail: an agent profile and ACP service listings (Stages 1–2, no token involved), with a possible future token launch through the same platform (Stage 3, gated). If Basis uses Virtuals as a distribution rail, that relationship is disclosed and does not alter Basis methodology or findings.
- Virtuals coverage continues on its published re-check cadence — no recusal; coverage holes are worse than disclosed conflicts.
- Basis will not accept Virtuals ecosystem subsidies, grants, or boosted-revenue programs while covering Virtuals; offers are logged here even when declined.
- Stage 1 is live (2026-06-10): the read-only “Basis Agent” profile exists on Virtuals (agent id 019eb320-ba7b-743b-a3a7-059cf7ac7fa3). Not tokenized. Platform fees paid: none. A platform-assigned Base Builder Code (bc_j5xczmq5) exists — an attribution mechanism applied to platform transactions; any proceeds it ever routes to Basis will be itemized here (current: none). No ACP listings exist yet. Agent wallets (platform-provisioned, minimally funded, never treasury): EVM 0xdd72cae818a1cad418cca122c588fe3ddb41c1ad, Solana CnpcS6uvKoTBqhxhHC58gWzv4ifpZY5WyJYfu1qBYY8u.
- Virtuals-launched projects in Basis coverage (PRXVT, Reppo) gain adjacency disclosure if a Basis launch proceeds on the same rail.
- If Stage 3 tokenization ever occurs: the first scheduled post-launch Virtuals re-check is pre-announced and publishes in full, whatever it finds — the regime's first public test.
Token-related disclosures ($BASIS — planned, not live)
- No token is live. No contract exists; no proceeds of any kind exist today. The position change from the original no-token stance is documented in RFC-001.
- If tokenization occurs: all launch costs and ongoing trading-fee proceeds will be disclosed here monthly, in USD terms, with labeled treasury addresses; proceeds convert to USDC on a pre-published schedule (so treasury sales are never information-bearing about unpublished findings).
- Token revenue is never marketed as value accrual; no mechanism routes Basis revenue to the token; the registry is designed to be indifferent to token price.
- Token holders govern nothing about audit outcomes — no labels, claims, reports, scores, sources, or corrections, ever.
- Self-audit commitment: if $BASIS launches, Basis enters its own registry as a covered project — its own claims scored under the same CRI, its launch metrics published sybil-adjusted (raw alongside) using the same heuristics applied to everyone else.
Treasury & holdings policy
Basis takes no positions in covered projects' assets. Operator personal token holdings policy, treasury composition rules, and labeled addresses will be published here before any Stage 3 step (current draft: zero operator personal holdings; treasury holds only USDC and, if launched, $BASIS; no treasury exists today).
ACP / service fees (Stage 2 — under preparation)
When ACP service listings go live, this section will itemize: platform fee splits on jobs, Basis service pricing, and aggregate demand metrics with sybil-checked counterparty analysis. Correction intake remains free on every rail. Current: no listings exist; no ACP fees have been paid or received.
Disputes about anything on this page are evidence like everything else: corrections@basis.watch. See also the methodology and legal & disclaimers.