Abstract

It is well known that vital enzymes in the replication process of the coronavirus are the SARS-CoV-2 PLpro and SARS-CoV-2 3CLpro, both of which are important targets in the search for anti-coronavirus agents. These two enzymes are responsible for cleavage at various polyprotein sites in the SARS-CoV-2 lifecycle. Herein, the dynamics of the polyprotein cleavage sequences for the boundary between non-structural proteins Nsp1 and Nsp2 (CS1) and between Nsp2 and Nsp3 (CS2) in complex with both the papain-like protein PLpro and the main protease 3CLpro were explored using computational methods. The post dynamics analysis reveals that CS1 and CS2 both have greater stability when complexed with PLpro. Of these two, greater stability is observed for the CS1-PLpro complex, while destabilization resulting in loss of CS2 from the PLpro active site is observed for CS2-PLpro, suggesting the rate of exchange by the papain-like protease is faster for CS2 compared to CS1. On the other hand, the 3CLpro main protease also reveals stability for CS1 suggesting that the main protease could also play a potential role in the cleavage at point CS1. However, destabilization occurs early in the simulation for the complex CLpro-CS2 suggesting a poor interaction and non-plausible protease cleavage of the polyprotein at CS2 by the main protease. These findings could be used as a guide in the development and design of potent COVID-19 antiviral inhibitors that mimic the CS1 cleavage site.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.