eLife Assessment: #GotGlycans: Role of N343 Glycosylation on the SARS-CoV-2 S RBD Structure and Co-Receptor Binding Across Variants of Concern
Bibliographic record
Abstract
Glycosylation of the SARS-CoV-2 spike (S) protein represents a key target for viral evolution because it affects both viral evasion and fitness. Successful variations in the glycan shield are difficult to achieve though, as protein glycosylation is also critical to folding and to structural stability. Within this framework, the identification of glycosylation sites that are structurally dispensable can provide insight into the evolutionary mechanisms of the shield and inform immune surveillance. In this work we show through over 45 μs of cumulative sampling from conventional and enhanced molecular dynamics (MD) simulations, how the structure of the immunodominant S receptor binding domain (RBD) is regulated by N-glycosylation at N343 and how this glycan’s structural role changes from WHu-1, alpha (B.1.1.7), and beta (B.1.351), to the delta (B.1.617.2) and omicron (BA.1 and BA.2.86) variants. More specifically, we find that the amphipathic nature of the N-glycan is instrumental to preserve the structural integrity of the RBD hydrophobic core and that loss of glycosylation at N343 triggers a specific and consistent conformational change. We show how this change allosterically regulates the conformation of the receptor binding motif (RBM) in the WHu-1, alpha and beta RBDs, but not in the delta and omicron variants, due to mutations that reinforce the RBD architecture. In support of these findings, we show that the binding of the RBD to monosialylated ganglioside co-receptors is highly dependent on N343 glycosylation in the WHu-1, but not in the delta RBD, and that affinity changes significantly across VoCs. Ultimately, the molecular and functional insight we provide in this work reinforces our understanding of the role of glycosylation in protein structure and function and it also allows us to identify the structural constraints within which the glycosylation site at N343 can become a hotspot for mutations in the SARS-CoV-2 S glycan shield.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.008 | 0.003 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.492 | 0.216 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".