Key result
A 1:1 Lis1-dynein complex promotes an open state, whereas 2:1 complexes resemble nucleotide-regulated autoinhibition.
Why the study?
Evidence for the mechanism by which Lis1 relieves dynein's autoinhibited state was lacking.
Key points are not available for this paper at this time.
Comparison
Different nucleotide-bound states of dynein motor domain affecting Lis1 binding affinity and stoichiometry
Design
Structural and biochemical analysis including electron microscopy and cryo-EM
No immediate clinical implications; leaves open Lis1-dynein roles in cardiovascular cytoskeletal research.
Dynein-1 is a microtubule motor responsible for the transport of cytoplasmic cargoes. Activation of motility requires it first overcome an autoinhibited state prior to its assembly with dynactin and a cargo adaptor. Studies suggest that Lis1 may relieve dynein's autoinhibited state. However, evidence for this mechanism is lacking. We first set out to determine the rules governing dynein-Lis1 binding, which reveals that their binding affinity is regulated by the nucleotide-bound states of each of three nucleotide-binding pockets within the dynein motor domain. We also find that distinct nucleotide 'codes' coordinate dynein-Lis1 binding stoichiometry by impacting binding affinity at two different sites within the dynein motor domain. Electron microscopy reveals that a 1 Lis1:1 dynein complex directly promotes an open, uninhibited conformational state of dynein, whereas a 2:1 complex resembles the autoinhibited state. Cryo-EM analysis reveals the structural basis for Lis1 opening dynein relies on interactions with the linker domain.
No takes yet. Share an insight, caveat, or question.
Geohring et al. (2024) studied this question. A 1 Lis1:1 dynein complex directly promotes an open, uninhibited conformational state of dynein, whereas a 2:1 complex resembles the autoinhibited state, regulated by nucleotide-bound states.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: