Part:BBa_K4229073
BMC-T1_R78TAG
Short Description :
The R78X variant of BMC-T1(BBa_K4229037) was created using site-directed mutagenesis, aiming to insert a non-canonical amino acid at position 8 of the peptide sequence by amber stop codon. The BMC-T1_R78X can only be completely synthesized upon successful amber stop codon suppression. Hence, BMC-T1_R78X can be used to create a ncAA modified shell protein for the assembly of a synthetic carboxysome.
Usage:
Besides the well-known 20 canonical amino acids, there is a variety of non-canonical amino acids which can be used to further modify proteins. One way of incorporating non-canonical amino acids is via the amber stop codon suppression technology. This part BMC-T1_R78X, is a model protein to test non-canonical amino acid incorporation. Without successful incorporation, a non-functional version of BMC-T1 will be translated, and the synthetic carboxysome cannot form. However, after successful incorporation of the non-canonical amino acid, translation will go on as normal and the synthetic carboxysome can form.
Characterization:
The incorporation of non-canonical amino acids into BMC-T1_R78X was characterized using SDS-PAGE, Western blot, and antibody decoration. As an orthogonal translation system, an additional aminoacyl-tRNA synthetase and its corresponding tRNA are used, which in this case correspond to the pBpf synthetase, which incorporates 4-Benzoyl-l-phenylalanine.
The plasmid containing this protein was kindly sent to us by the Kerfeld group.
H. Kirst and C. A. Kerfeld, “Bacterial microcompartments: Catalysis-enhancing metabolic modules for next-generation metabolic and biomedical engineering,” BMC Biol., vol. 17, no. 1, pp. 1–11, 2019, DOI: 10.1186/s12915-019-0691-z.
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12INCOMPATIBLE WITH RFC[12]Illegal NotI site found at 706
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal NgoMIV site found at 36
Illegal AgeI site found at 510
Illegal AgeI site found at 618 - 1000COMPATIBLE WITH RFC[1000]
None |