The sequence at Spike S1/S2 site enables cleavage by furin and phospho-regulation in SARS-CoV2 but not in SARS-CoV1 or MERS-CoV
This article has been Reviewed by the following groups
Listed in
- Evaluated articles (ScreenIT)
Abstract
The Spike protein of the novel coronavirus SARS-CoV2 contains an insertion 680 S PRRA R↓SV 687 forming a cleavage motif RxxR for furin-like enzymes at the boundary of S1/S2 subunits. Cleavage at S1/S2 is important for efficient viral entry into target cells. The insertion is absent in other CoV-s of the same clade, including SARS-CoV1 that caused the 2003 outbreak. However, an analogous cleavage motif was present at S1/S2 of the Spike protein of the more distant Middle East Respiratory Syndrome coronavirus MERS-CoV. We show that a crucial third arginine at the left middle position, comprising a motif R R xR is required for furin recognition in vitro, while the general motif RxxR in common with MERS-CoV is not sufficient for cleavage. Further, we describe a surprising finding that the two serines at the edges of the insert S PRRAR↓ S V can be efficiently phosphorylated by proline-directed and basophilic protein kinases. Both phosphorylations switch off furin’s ability to cleave the site. Although phospho-regulation of secreted proteins is still poorly understood, further studies, supported by a recent report of ten in vivo phosphorylated sites in the Spike protein of SARS-CoV2, could potentially uncover important novel regulatory mechanisms for SARS-CoV2.
Article activity feed
-
SciScore for 10.1101/2020.06.23.166900: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
Institutional Review Board Statement not detected. Randomization not detected. Blinding not detected. Power Analysis not detected. Sex as a biological variable not detected. Table 2: Resources
No key resources detected.
Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section about the limitations of the techniques employed in this study was not found. We encourage authors to address study limitations.Results from TrialIdentifier: No clinical trial numbers were referenced.
Results from Barzooka: We did not find any issues relating to the usage of bar …
SciScore for 10.1101/2020.06.23.166900: (What is this?)
Please note, not all rigor criteria are appropriate for all manuscripts.
Table 1: Rigor
Institutional Review Board Statement not detected. Randomization not detected. Blinding not detected. Power Analysis not detected. Sex as a biological variable not detected. Table 2: Resources
No key resources detected.
Results from OddPub: We did not detect open data. We also did not detect open code. Researchers are encouraged to share open data when possible (see Nature blog).
Results from LimitationRecognizer: An explicit section about the limitations of the techniques employed in this study was not found. We encourage authors to address study limitations.Results from TrialIdentifier: No clinical trial numbers were referenced.
Results from Barzooka: We did not find any issues relating to the usage of bar graphs.
Results from JetFighter: We did not find any issues relating to colormaps.
Results from rtransparent:- Thank you for including a conflict of interest statement. Authors are encouraged to include this statement when submitting to a journal.
- Thank you for including a funding statement. Authors are encouraged to include this statement when submitting to a journal.
- No protocol registration statement was detected.
-
-