Key result
Double-headed myosin V performs ATP-free walking by harnessing strain energy from actin binding.
Why the study?
It has long been thought that ATP is the energy source for mechanical work in ATPase protein motors coupled to their ATPase reactions.
This study reveals that the strong binding energy between myosin V and actin is converted into mechanical work, enabling ATP-free walking under external force.
Challenges ATP as sole energy source for myosin motors; leaves open relevance to cardiac myosin function in vivo.
The mechanical processes of ATPase protein motors are coupled to their ATPase reactions. The free energy released at a given step(s) of the ATPase cycle is converted into mechanical work. Therefore, it has long been thought that ATP is the energy source for mechanical work. Here, we show that the double-headed myosin V (M5) motor can perform ATP-free walking. In the presence of ADP, M5 bound to F-actin by both heads makes a forward step when the trailing head is detached by an external force. This forward step harnesses the strain energy in the leading (L) head, provided from the strong binding energy between the L-head and actin. Consequently, strain generation reduces the binding affinity, which manifests as sporadic, brief L-head detachment. Strain generation and brief L-head detachment also occur during ATP-dependent walking to similar extents as during ATP-free walking. These results suggest that the strong binding energy is also converted into mechanical work during ATP-dependent walking.
No takes yet. Share an insight, caveat, or question.
Kodera et al. (2025) studied Myosin V motor mechanics. ATP-free walking vs. ATP-dependent walking was evaluated on Mechanical work and strain generation. Double-headed myosin V motor performs ATP-free walking by harnessing strain energy from strong binding to actin, suggesting this energy is also converted to work during ATP-dependent walking.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: