Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-1205 version: 1 kind: certified reason: Certified into the record timestamp: 2026-09-27T14:19:03.277161Z status: published lens: g_space sector: science headline: AlphaFold Protein Structure Database in 2024: providing structure coverage for over 214 million protein sequences dek: The AlphaFold Database Protein Structure Database (AlphaFold DB, https://alphafold.ebi.ac.uk) has significantly impacted structural biology by amassing over 214 million predicted protein structures, expanding from the initial 300k structures released in 2021. Enabled by the groundbreaking AlphaFold2 artificial intelligence (AI) system, the predictions archived in AlphaFold DB have been integrated into primary data resources such as PDB, UniProt, Ensembl, InterPro and MobiDB. Our manuscript details subsequent enh… gain_title: AlphaFold DB scaled from 300k to over 214 million predicted structures and was integrated into primary resources like PDB and UniProt, expanding structure coverage for research use. problem_title: (none) trace_subject: (none) gain_reading: AlphaFold DB scaled from 300k to over 214 million predicted structures and was integrated into primary resources like PDB and UniProt, expanding structure coverage for research use. gain_evidence: amassing over 214 million predicted protein structures | predictions archived in AlphaFold DB have been integrated into primary data resources such as PDB, UniProt, Ensembl, InterPro and MobiDB problem_reading: (none) problem_evidence: (none) quick_read: By October 2023, the authors reported that the AlphaFold Protein Structure Database had grown from 300,000 structures in 2021 to over 214 million predicted structures, enabled by AlphaFold2. The paper outlines archiving enhancements, coverage of model organisms and other curated sets, and access routes including FTP and Google Cloud Public Datasets. The expansion matters because the predictions have been integrated into primary resources such as PDB, UniProt, Ensembl, InterPro and MobiDB, extending structural information available for biological research workflows. The source does not quantify downstream discovery outcomes or validation rates, leaving uncertainty about coverage quality across all 214 million entries. limitation: tag: Evidence-backed gain key_points: AlphaFold DB grew from initial 300k structures released in 2021 to over 214 million predicted structures by 2024 coverage described in 2023 manuscript. | Predictions are enabled by the AlphaFold2 artificial intelligence system. | Structures have been integrated into PDB, UniProt, Ensembl, InterPro and MobiDB. | Paper details data access via FTP, Google Cloud Public Datasets, and programmatic endpoints, plus improvements to Predicted Aligned Error viewer, 3D viewer customization, and search engine. rundown: The manuscript describes successive releases covering model organisms, global health proteomes, Swiss-Prot integration and curated protein datasets, expanding from the 2021 initial release. Access mechanisms include direct file access via FTP, advanced queries using Google Cloud Public Datasets, and programmatic access endpoints, with added services for viewing Predicted Aligned Error and customizing the 3D viewer. sources: - peer_reviewed | Nucleic Acids Research | https://doi.org/10.1093/nar/gkad1011 | 2023-10-18 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- dc83984f35429bc5bad6c0672bcc9988b46072adc1785133a1edc0f5a71655fe
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1205 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace