My Authors
Read all threads
2006 study inserts furin cleavage site into SARS-CoV spike at the exact residue where SARS-CoV-2's PRRA(R) site is - and demonstrates enhanced cell-to-cell fusion. ncbi.nlm.nih.gov/pmc/articles/P…
Before explaining this 2006 study, it's better to start with the 2020 paper that first described the furin cleavage site unique to SARS-CoV-2: sciencedirect.com/science/articl…
Coutard et al. observed SARS-CoV-2 "has a specific furin-like cleavage site absent in lineage b CoV including SARS-CoV sequences." Figure 2 is great because it aligns SARS-CoV-2 (aka 2019-nCoV) to not only SARS but also MERS and other CoVs with a known FCS marked with *.
Why is the FCS at the S1/S2 junction in the spike so important? A body of studies have shown that such a site can impact cell-to-cell fusion as well as the virus' ability to infect different cell types. This has been recently demonstrated in SARS-CoV-2 as well.
For example, in MERS-CoV, the S1/S2 FCS allows it to infect human lung and intestine (cancer derived) cells; without the FCS, the virus can only infect kidney (cancer derived) cells. pubmed.ncbi.nlm.nih.gov/27791014/ and pubmed.ncbi.nlm.nih.gov/30413791/
In SARS-CoV-2, when its FCS was lost during cell passage in monkey kidney cells, the virus became significantly attenuated in a hamster animal model of SARS2 disease. pubmed.ncbi.nlm.nih.gov/32301390/
This was noticed by 2 groups who both commented that the FCS could be under strong selective pressure in humans or animals. biorxiv.org/content/10.110…
Just to summarize before the next paper (1) S1/S2 FCS has not been seen in any beta CoVs, including all SARS-related CoVs, and (2) the S1/S2 FCS has been shown to confer pathogenic advantages even in SARS-CoV-2.
However, this paper reports a novel beta CoV, closely related to SARS-CoV-2, that has natural insertions (not demonstrated to be a functional FCS) at the S1/S2 junction.
sciencedirect.com/science/articl…
Looking at their Fig 2 alignment of SARS-CoV-2 to the novel CoV RmYN02 and other SARS-related CoVs, others have pointed out that rather than an "insertion" maybe it is a unique alignment that results in a trimer shift, or maybe it's an insertion just downstream of a deletion?
Another way of aligning these sequences would have been to move that -NSPAA back to the left to fill that gap in the alignment. In that version, the novel CoV RmYN02 would look more similar to the other SARSr-CoVs - missing a 4 residue FCS in comparison to SARS-CoV-2.
But what Zhou et al. suggest is that this alignment of RmYN02 vs SARSr-CoVs "indicates that events of this kind are a natural and expected component of coronavirus evolution".
This is supported by their understanding that RmYN02 "is the closest relative of SARSCoV-2 in the long 1ab replicase gene, although the virus itself has a complex history of recombination".
After reading Zhou et al.'s paper I wanted to learn more about furin cleavage sites and coronaviruses so I simply searched for "furin" and "coronaviruses" on pubmed.gov. One of the early papers was the 2006 study by Follis et al. ncbi.nlm.nih.gov/pmc/articles/P…
Follis et al. were focusing on SARS-CoV but ultimately trying to understand why some viruses don't rely on an S1/S2 FCS to infect cells and mediate host cell-to-cell fusion.
Back in 2006, these were the other characterized CoVs (MERS FCS hadn't been studied yet) for comparison (Follis et al. Fig 1A). They noted: "the single arginine at position 667 of the SARS-CoV S glycoprotein, which may signal a protease-sensitive site".
To rule out that wild type (natural) SARS-CoV wasn't already getting cleaved at this site without a notable FCS, Follis et al. mutated that arginine at position 667 (aka R667) and found no impact on Spike expression or glycosylation, confirming no evidence of cleavage.
Then, Follis et al. engineered the BCoV RRSR(R677) FCS into SARS to see what would happen (Fig 1B). They found that for cleavage to occur, you had to insert an extra residue similar to the BCoV alignment, and not perturb the sequence downstream of R677.
"cleavage of the SARS S glycoprotein can be achieved by the introduction of a furin recognition motif, especially at R667. The differences in the degree of cleavage between the two R667 mutants, and in SLLR, suggest specificity in the recognition of the engineered furin sites"
At this point, I want to draw your attention back to Coutard et al.'s figure which shows an updated list of CoVs and their FCS sites: SARS2 SPRRAR, HKU1 SRRKRR, OC43 KNRRSR, MERS TPRSVR. In many naturally found CoVs, this FCS at R667 exists and the sequence can be quite flexible.
Follis et al. showed improved cell-to-cell fusion by the SARS Spike with the inserted FCS. However, they only tested the infectivity of Spike-presenting particles on human 293T kidney cells. We know now the FCS does not affect kidney cell infection, but impacts other cell types.
To summarize, the S1/S2 FCS exists in natural CoVs, but has not been observed in SARS-related-CoVs. Scientists tested introduction of FCS at R667 in SARS. Later discovered in MERS that FCS enables infection of more cell types. Now we know SARS2 FCS confers infection advantages.
Ending of another unsatisfying tweetorial: there is zero evidence that confirms that the SARS-CoV-2 S1/S2 PRRA(R) FCS arose naturally or artificially, but neither scenario can be ruled out.
Sorry, typo - trying to squeeze all these scientific interpretations into tweets - "in any lineage b beta CoVs"
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with Alina Chan

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!