Editorial pass: sharper headline; gain/problem restated as concrete outcomes.
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-1119 version: 2 kind: revised reason: Editorial pass: sharper headline; gain/problem restated as concrete outcomes. timestamp: 2026-11-04T09:50:26.313922Z status: published lens: g_space sector: climate headline: Carbon dioxide hydrogenation on copper and nickel catalysts <i>via</i> a conformal sampling approach dek: We present a computational workflow, the Conformal Sampling of Catalytic Processes (CSCP) approach, and its application to the case of heterogeneous hydrogenation/reduction of carbon dioxide (CO 2 ) on copper and nickel catalysts. CO 2 activation is of critical importance for a sustainable global future and one of the major reactions for which sustainable routes must be found urgently. We use the fcc(100) facet of Cu as a worked-out case, and exhaustively derive at the DFT level its reaction mechanisms. We then… gain_title: In computer benchmarks, AI models of CO2 hydrogenation had maximum errors of 0.05 eV on copper and 0.03 eV on nickel, and the copper work was carried over to nickel rapidly. problem_title: (none) trace_subject: (none) gain_reading: In computer benchmarks, AI models of CO2 hydrogenation had maximum errors of 0.05 eV on copper and 0.03 eV on nickel, and the copper work was carried over to nickel rapidly. gain_evidence: accuracy of the so-derived MLIPs is excellent | maximum discrepancy of 0.05 eV for Cu and 0.03 eV for Ni | predicting both reaction energies and energy barriers for all the mechanistic steps problem_reading: (none) problem_evidence: (none) quick_read: A peer-reviewed study introduced the Conformal Sampling of Catalytic Processes workflow to model heterogeneous CO2 hydrogenation on copper and nickel. Starting from exhaustive DFT on Cu(100), the team trained a Machine Learning Interatomic Potential and transferred it to Ni(100) to test cross-metal portability. The result matters for climate mitigation because accurate, transferable MLIPs could accelerate rational design of catalysts for sustainable CO2 conversion. Uncertainty remains about how the observed pathway divergences in exception cases affect predictions on other facets, alloys, or operating conditions beyond the two monometallic (100) surfaces tested. limitation: In some steps the MLIP deviates from reference DFT because it explores different pathways, indicating mechanism divergence despite maintained absolute accuracy. tag: Evidence-backed gain key_points: Workflow named Conformal Sampling of Catalytic Processes (CSCP) was applied to heterogeneous hydrogenation of CO2 on Cu and Ni. | Initial exhaustive DFT mechanisms were derived on fcc(100) facet of Cu, then knowledge was carried over to Ni(100) to test transferability. | MLIPs maintained uniform accuracy across complex reaction diagram and explored alternative atomistic pathways in exception cases. rundown: Researchers built an exhaustive DFT reaction network for CO2 reduction on Cu(100), then used CSCP to train an MLIP and transferred that knowledge to Ni(100) to rapidly derive a second MLIP. Evaluation showed consistent prediction of energies and barriers across all mechanistic steps, with larger discrepancies explained by the MLIP finding alternative pathways rather than loss of accuracy, supporting use for catalyst rational design. sources: - peer_reviewed | Faraday Discussions | https://doi.org/10.1039/d5fd00132c | 2026-09-17 prev: eb64e1da3165f5471c0614bcfe222ab11f4b911b1cd5c0662f73e7d461fe8ffa
- SHA-256 hash
- 897417096144f8e3cb2452e0a112cd8fa986400231432e5d1a4745d9d19c8e0e
- Previous version’s hash
- eb64e1da3165f5471c0614bcfe222ab11f4b911b1cd5c0662f73e7d461fe8ffa
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1119 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