Explore a curated library of official crypto whitepapers and substantive project documentation, each verified against the project's own site and supported by plain-language context. Move from a quick scan to the original source without relying on aggregator copies or second-hand commentary.
Project pages, social posts, and third-party summaries all interpret the original claim for you. A verified whitepaper or documentation source lets you examine the design, assumptions, and limitations in the project's own material.
Whitepapers are useful because they show how a project describes its own problem, architecture, incentives, and trade-offs. The hard part is locating the right source, understanding what it actually covers, and knowing when the document is historical or incomplete.
Scattered sources and inconsistent context
Verified sources with a consistent learning layer
Every record follows the same core structure so you can identify the project, understand the source, and decide what to read next. Approved summaries may also receive a narrated version after a separate audio review.
Each record uses the same information architecture, moving from exact project identity to source verification, interpretation, and optional listening.
Project and symbol
The official project name and native ticker identify the exact asset or protocol represented, helping distinguish the canonical project from forks, wrappers, and similarly named assets.
Two direct links establish where the project and its core material live.
Official website
A direct link to the project's current official site lets you cross-check present-day claims, documentation, and operating status.
Official whitepaper or documentation
The verified source points to an official paper or substantive documentation page, keeping research anchored to primary material rather than an aggregator copy.
Three learner-facing layers let you choose the depth that fits the task.
Plain-language description
A short overview explains what the project does and why its source matters, helping you decide whether the full document is relevant to your question.
Critical source summary
A deeper synthesis explains the design, assumptions, strengths, omissions, and currentness limits without replacing the original source.
Narrated summary
An approved summary may also be published as a two-to-three-minute narrated version after separate listening review and exact-record verification.
The collection spans foundational networks, DeFi mechanisms, infrastructure, privacy, tokenised assets, and newer application models. These source families help learners connect course concepts to the systems that implement them.
Read across categories to build a connected mental model, or go directly to the project family relevant to your research.
Base layers and original protocols
Consensus, transaction models, execution environments, network security, issuance, and the design choices behind foundational blockchain systems.
Scaling and interoperability
Layer 2 systems, rollups, shared security, bridges, cross-chain messaging, and the trade-offs involved in moving data or value between networks.
DeFi protocols and market mechanisms
Decentralised exchanges, lending, liquidity, derivatives, collateral, governance, incentives, and the assumptions that keep onchain financial systems operating.
Stablecoins and tokenised assets
Reserve models, collateral design, minting and redemption, synthetic exposure, real-world asset structures, and the offchain dependencies behind onchain claims.
Infrastructure and developer systems
Oracles, indexing, storage, compute, identity, data availability, middleware, and the supporting services that applications rely on but users may not see.
Privacy and cryptographic design
Confidential transactions, zero-knowledge systems, anonymity models, verification methods, and the practical limits or trust assumptions of privacy-preserving networks.
AI, data, and decentralised infrastructure
Machine-learning networks, data marketplaces, decentralised compute, physical infrastructure coordination, rewards, and the link between digital tokens and real resource provision.
Ecosystems, applications, and community models
Exchange ecosystems, gaming, virtual worlds, community-led assets, wrapped instruments, and application models that show how protocol design reaches end users.
The mix is learner-led rather than quota-led. New project families are added only when the source is official, the system is relevant, and the record adds distinct educational value.
A project does not qualify simply because it publishes a polished document. Each candidate must clear sequential checks for identity, current operation, official-source quality, real-world relevance, and distinct learner value.
The checks run in sequence. A decisive failure stops the review, while a passing project still needs to add meaningful learning value before a record can be approved.
Exact project identity
The project, asset, ticker, contract, chain, migration state, website, and record unit must resolve to one canonical identity.
Independent market-significance gate
For an ordinary token-bearing candidate, the same canonical asset must currently rank within the top 600 on both CoinMarketCap and CoinGecko. This is an entry gate, not a quality score.
Live, maintained operation
The project must be operating in production and clearly distinguished from testnet, beta, roadmap-only, inactive, or deprecated states.
Substantive official source
The approved source must be official, bounded, reproducible, and detailed enough to support genuine source-based learning.
Current adoption evidence
The review looks for credible production-use evidence, normally including a quantitative signal and corroboration where reasonably available.
Credible market viability
Token-bearing projects need realistic current spot-market activity for the exact canonical asset rather than thin, artificial, or mismatched trading evidence.
Distinct learner value
The final question is whether the project adds an important mechanism, category, historical reference, or design perspective not already represented more clearly elsewhere.
Learner value comes first
Rank, documentation quality, and market activity provide evidence. None of them automatically authorises inclusion or turns the record into an endorsement.
Review continues after publication
Monthly and trigger-based checks review links, source quality, project status, material changes, and whether the record still meets the standard.
A project does not qualify simply because it publishes a polished document. Each candidate must clear sequential checks for identity, current operation, official-source quality, real-world relevance, and distinct learner value.
The checks run in sequence. A decisive failure stops the review, while a passing project still needs to add meaningful learning value before a record can be approved.
Exact project identity
The project, asset, ticker, contract, chain, migration state, website, and record unit must resolve to one canonical identity.
Independent market-significance gate
For an ordinary token-bearing candidate, the same canonical asset must currently rank within the top 600 on both CoinMarketCap and CoinGecko. This is an entry gate, not a quality score.
Live, maintained operation
The project must be operating in production and clearly distinguished from testnet, beta, roadmap-only, inactive, or deprecated states.
Substantive official source
The approved source must be official, bounded, reproducible, and detailed enough to support genuine source-based learning.
Current adoption evidence
The review looks for credible production-use evidence, normally including a quantitative signal and corroboration where reasonably available.
Credible market viability
Token-bearing projects need realistic current spot-market activity for the exact canonical asset rather than thin, artificial, or mismatched trading evidence.
Distinct learner value
The final question is whether the project adds an important mechanism, category, historical reference, or design perspective not already represented more clearly elsewhere.
Learner value comes first
Rank, documentation quality, and market activity provide evidence. None of them automatically authorises inclusion or turns the record into an endorsement.
Review continues after publication
Monthly and trigger-based checks review links, source quality, project status, material changes, and whether the record still meets the standard.
You do not need to read every document from beginning to end. Use the structured fields to decide what matters, then return to the official source when you need evidence, detail, or comparison.
Start with orientation, move into interpretation, verify the exact point in the primary source, and compare only after the research question is clear.
Begin with the description
Confirm the project's purpose and decide whether its source is relevant to the concept, mechanism, or question you are researching.
Read the critical summary
Identify the main design, trust assumptions, strengths, omissions, and historical boundaries before opening a long or highly technical source.
Open the official source
Return to the exact paper or documentation page when you need definitions, diagrams, formulas, implementation detail, or support for a specific claim.
Use one fixed question
Compare projects around one mechanism at a time, such as consensus, collateral, governance, privacy, or scaling, instead of treating every paper as directly equivalent.
AI helps discover sources, analyse long documents, draft learner-facing text, and run recurring maintenance checks across the collection. Editors verify the evidence and approve every inclusion, summary, update, and published audio file.
AI accelerates research and production across a growing source library. Editors remain responsible for identity, evidence, inclusion, learner-facing text, maintenance decisions, and every published audio attachment.
AI-assisted work
Scale the research and production tasks
Source discovery
Search official domains and supporting evidence to locate likely canonical papers or documentation packages while filtering out mirrors and aggregators.
Document analysis and drafting
Read the approved source in depth and prepare the description and critical summary around its design, assumptions, omissions, and currentness boundaries.
Recurring maintenance checks
Surface broken links, moved documents, lifecycle changes, and records that may require a fresh source or revised learner-facing text.
Approved Summary-to-audio production
Generate a narrated version from the exact approved summary after the written record is final and ready for the separate audio workflow.
Editor-controlled decisions
Protect source quality and learner trust
Confirm identity and source authority
Resolve the exact project and verify that the selected paper or documentation is official, current enough, bounded, and reproducible.
Approve inclusion and written content
Judge learner value, verify the evidence, edit the description and summary, and authorise the exact Airtable record change.
Decide maintenance action
Determine whether a surfaced change requires no action, a corrected link, rewritten text, a status change, or a deeper re-review.
Listen, approve, attach, and verify audio
Review the complete narration, approve the file, attach it to the exact record, and verify that the learner-facing audio matches the current summary.
Expert brings the structured course together with the research and due-diligence resources used for deeper, ongoing study. Compare the plans to see exactly what is included, or begin with the free course first.
Not sure which plan fits? Take the learning-path quiz.
These answers explain what the collection includes, how sources are selected, and how to use the summaries responsibly. They also clarify where audio, AI assistance, and monthly maintenance fit into the methodology.
Yes. Each record links to an official whitepaper or substantive documentation source, and the source is checked against the project's own official site before the record is approved.
No. Some projects now maintain living documentation that explains the current system more accurately than an older PDF. In those cases, the library links to the official documentation page instead.
The current approved collection contains 200 active project records. The library can continue growing whenever another project meets the same source-quality and learner-value standard.
Each approved record includes the project name and symbol, a plain-language description, the official website, the verified whitepaper or documentation link, and a deeper critical summary of the source.
Not yet. The Summary-to-audio pipeline is active, but audio is added progressively and only after the approved text has passed technical validation, listening review, approval, attachment, and record-level verification.
The collection follows a monthly maintenance cycle, with additional reviews triggered by broken links, moved documents, project lifecycle changes, rebrands, migrations, or other material developments.
No. Market rank is only one ordinary entry gate for token-bearing candidates. A project must also be live, well documented, supported by current evidence, and educationally distinct enough to earn a place.
No. Start with the description and critical summary, then open the original source for the sections, diagrams, assumptions, or claims that matter to your specific research question.
No. The summary is a triage and interpretation layer. It helps you understand the main model and limitations, but the original source remains the place to verify definitions, diagrams, formulas, and exact claims.
The same underlying records can be presented through multiple views for structured comparison, visual scanning, grouped exploration, or recent additions. Additional views may be introduced as the collection develops.
AI supports source discovery, document analysis, drafting, recurring checks, and approved Summary-to-audio generation. Editors verify the evidence and retain approval authority over every inclusion, change, summary, and published audio file.
No. Inclusion means the project and its source are educationally worth understanding. It is not an endorsement, investment recommendation, security assessment, compliance opinion, or proof of future viability.
Get started today before this once in a lifetime opportunity expires.
