z-logo
Premium
Solution structure of ribosomal protein L40E, a unique C4 zinc finger protein encoded by archaeon Sulfolobus solfataricus
Author(s) -
Wu Bin,
Lukin Jonathan,
Yee Adelinda,
Lemak Alexander,
Semesi Anthony,
Ramelot Theresa A.,
Kennedy Michael A.,
Arrowsmith Cheryl H.
Publication year - 2008
Publication title -
protein science
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 3.353
H-Index - 175
eISSN - 1469-896X
pISSN - 0961-8368
DOI - 10.1110/ps.073273008
Subject(s) - sulfolobus solfataricus , ribosomal protein , sulfolobus , 50s , archaea , protein subunit , crystallography , zinc finger , eukaryotic large ribosomal subunit , biology , ribosomal rna , protein structure , biochemistry , chemistry , ribosome , rna , gene , transcription factor
The ribosomal protein L40E from archaeon Sulfolobus solfataricus is a component of the 50S ribosomal subunit. L40E is a 56‐residue, highly basic protein that contains a C4 zinc finger motif, CRKC_X 10 _CRRC. Homologs are found in both archaea and eukaryotes but are not present in bacteria. Eukaryotic genomes encode L40E as a ubiquitin‐fusion protein. L40E was absent from the crystal structure of euryarchaeota 50S ribosomal subunit. Here we report the three‐dimensional solution structure of L40E by NMR spectroscopy. The structure of L40E is a three‐stranded β‐sheet with a simple β2β1β3 topology. There are two unique characteristics revealed by the structure. First, a large and ordered β2–β3 loop twists to pack across the one side of the protein. L40E contains a buried polar cluster comprising Lys19, Lys20, Cys22, Asn29, and Cys36. Second, the surface of L40E is almost entirely positively charged. Ten conserved basic residues are positioned on the two sides of the surface. It is likely that binding of zinc is essential in stabilizing the tertiary structure of L40E to act as a scaffold to create a broad positively charged surface for RNA and/or protein recognition.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here