Physical Transformation AtlasPTA
Phenomenon · phenomenon:galvanic-reaction

Galvanic (redox) reaction

A spontaneous redox reaction split between two electrodes forces its electrons through the external circuit. Reaction free energy becomes electrical work at up to the Nernst potential.

Electrochemistryfirst reported 1800also: electrochemical cell reaction, battery discharge

Atlas record: 6 claims reference this phenomenon — 6 established.

Explorerelations · matrix context · routes · sources · cite

conditions: aqueous medium required
6claims1enumerated routes1routes with complete-composition evidence0candidate routes not searched1cited sources

Relations

drives · 1
Chemical potential difference—drives→Galvanic (redox) reactionestablished
  • a spontaneous redox couple split between two electrodes with an ion-conducting electrolyte between them
E_cell = −ΔG / nF · 1/(nF) [mol/C]
produces · 1
Galvanic (redox) reaction—produces→Ionic currentestablished
member of · 1
Galvanic (redox) reaction—member of→Electrochemicalestablished
implemented by · 1
Galvanic (redox) reaction—implemented by→Galvanic cell (battery)established
bounded by · 1
Galvanic (redox) reaction—bounded by→Nernst / Gibbs free-energy boundestablished
governed by · 1
Galvanic (redox) reaction—governed by→Electromagnetic interactionestablished

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

D.05 × C.21 · Chemical potential difference × Electrochemical · Established
family: Electrochemical (C.21)

Enumerated routes through this · 1

Cited sources · 1

  1. [1]
    A. J. Bard, L. R. Faulkner. Electrochemical Methods: Fundamentals and Applications (2nd ed.) (2001)
    Wiley · book, no DOI · record

Cite this entity

Physical Transformation Atlas (2026). entity phenomenon:galvanic-reaction: Galvanic (redox) reaction. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/phenomenon/galvanic-reaction

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.