01
Core principles
Crypto Yield Archive is a historical registry, not a live APY ranking, investment recommendation, trading tool, or real-time dashboard. It records platform history, customer outcome, terms risk, failure chain, products, and supporting evidence.
Unknown values are kept visible. A missing answer is preferable to an unsupported answer.
02
Scope
The current registry focuses on CeFi lending platforms, crypto interest accounts, centralized yield platforms, and borrowing or lending services.
Not prioritized in the current scope
- Pool- and vault-level records
- Chain deployment records
- Real-time APY or TVL tracking
- General exchanges with no meaningful Earn or lending context
- Ordinary staking products without a relevant historical case
03
Counting unit
CYA counts platform entities. Products, pools, vaults, deployments, and individual claim classes do not become separate platform records unless they are historically meaningful entities of their own.
04
Record model
- platform_entity
- The platform or historically meaningful yield service.
- platform_event
- Launches, withdrawal pauses, bankruptcy filings, restructurings, distributions, and other meaningful changes.
- platform_evidence
- Sources supporting entity, event, outcome, terms-risk, ownership, status, or URL-history claims.
- customer_outcome
- What happened to user funds, including repayment, ongoing claims, no recovery, or unknown outcomes.
- terms_risk
- How terms, product category, or legal process affected asset-treatment uncertainty.
- product_profile
- Interest accounts, lending products, Earn-like products, and other historically relevant offerings.
05
Evidence and reliability
Preferred sources include official statements, court and bankruptcy documents, regulatory notices, archived pages, and reputable reporting. Evidence is linked to the claim it supports whenever possible.
Reliability is marked high, medium, or low. A low-reliability item can remain visible as a research lead, but it should not be treated as definitive proof.
06
URL handling
Original URLs are preserved as historical records. For ended, dead, or repurposed platforms, archived URLs should be preferred. Unsafe, expired, or unrelated domains must not be treated as normal outbound destinations.
07
Uncertainty
Dates may be approximate, legal outcomes may remain unresolved, and customer recovery can differ by claim class. Confidence labels and known-unknown notes are used to expose those limits rather than hide them.
08
Corrections
A useful correction includes the platform name, CYA page URL, the disputed or missing claim, source links, and a short explanation.