As mentioned in Elliott, M.J., Poelen, J.H. & Fortes, J.A.B. Signing data citations enables data verification and citation persistence. Sci Data 10, 419 (2023). https://doi.org/10.1038/s41597-023-02230-y hash://sha256/f849c870565f608899f183ca261365dce9c9f1c5441b1c779e0db49df9c2a19d , existing (data) publication platforms already support retrieval by content (or hash-based) identifiers. These include, but are not limited to: DataOne https://dataone.org, Zenodo https://zenodo.org, Software Heritage Library https://softwareheritage.org, and Wikimedia Commons https://commons.wikimedia.org/ . For examples on how these existing capacities can be used to create the appearance of a centralized service, please see https://github.com/bio-guoda/preston/issues/181 (DataOne), https://github.com/bio-guoda/preston/issues/149 (Zenodo), https://github.com/bio-guoda/preston/issues/70 (software heritage library), and https://github.com/bio-guoda/preston/issues/239 (wikimedia commons). With this, you can retrieve a picture of a bunny provided by https://commons.wikimedia.org/wiki/File:Oryctolagus_cuniculus_Rcdo.jpg via https://linker.bio/hash://sha1/86fa30f32d9c557ea5d2a768e9c3595d3abb17a2 . Also, you can retrieve a datafile https://zenodo.org/record/7977436/files/triples.nt indirectly mentioned in this publication via their DOI https://doi.org/10.5281/zenodo.7977435 https://linker.bio/hash://md5/c1e6c5410e49eea484a4a873589967d7 . Both examples did not require any special processing other than re-using content retrieval methods already available. This is why I'd like to encourage you to revise your potentially misleading section on content-based identifiers to reflect their widespead use in existing platforms mentioned above and beyond.