Splitted and engineered N-terminal FbaB for isopeptide bound formation (SpyCatcher) in RFC
|Submitted by||TU Dresden|
This part codes for a protein that recognizes and forms a covalent isopeptide bound to a oligopeptide. That oligopeptide can be found under BBa_K1159201. In contrast to the original SpyCatcher this part only contains the essential part for forming isopeptide bounds and does not contain a N-terminal His-tag and TEV cleavage site. Furthermore two amino acids were exchanged to improve the function, Ile34 was replaced by Glu34 which enhances the reaction rate, also the exposed hydrophobic redidue Met69 was replaced by Tyr69. This part is flanked by RFC pre- and suffix for further protein fusions.
Proper funtion of the construct was verified in a pulldown assay using 10 μM of SpyCatcher with N-terminal HisTag which was incubated with 5 μM of C-terminal spytagged SYFP2 for 1 h in PBS. Afterwards HisTag beads were added to bind the fusion product, resulting in a decrease of spytagged SYFP2 in the supernatant. The results of this assay are shown in Figure 2. The results show that after one hour at room temeperature, a two fold change in relative absorbance was observed. This verifies that the construct is working as intended.
Furthermore the two interaction partners were mixed, incubated and analyzed via SDS Page (reducing conditions) and coomassie staining.
Inspired by the self-catalysis, Peking iGEM 2016 fused three SpyTag spaced by (VPGVG)4 with 6xHistag in N-terminal and other functional protein modules in C-terminal. The network forming capacity is not affected. Moreover, E.coli has successfully secreted our fused protein when a few of specific signal peptides are added.
Fig. 1. Exploration of the polymerization ability of the 3A-SUP/3A-mSA with 3B. Left: the Coomassie Blue staining gel of basic experiment, which illustrates the basic cross-linking ability of 3A-SUP/3A-mSA and 3B. Lane 1, Thermo® Protein Marker; lane 2, 3A-SUP; lane 3, 3A-mSA; lane 4, 3A-SUP+3A-mSA; lane5, 3B; lane 6, 3A-SUP+3B; lane 7, 3A-mSA+3B. (Molecular Weight: 3A-SUP, 21.4kDa; 3A-mSA, 25.4kDa; 3B, 55.4(62) kDa. Right: A, the OD value of the lane 5 of oligomers produced by the mix of 3A-SUP and 3B. Peaks illustrate the monomers and the possible products, ①, 3A-SUP (21.4kDa); ②, 3B (62kDa); ③, 1x 3A-SUP+1x 3B (83.4kDa); ④, 3x 3A-SUP+1x 3B (126.2kDa); ⑤, 2x 3A-SUP+2x 3B (166.8kDa); ⑥, 4x 3A-SUP+4x 3B (333.6kDa). B, the OD value of the lane 6 of oligomers produced by the mix of 3A-mSA and 3B. Peaks illustrate the monomers and the possible products, ①, 3A-mSA (25.4kDa); ②, 3B (62kDa); ③, 1x 3A-mSA+1x 3B (87.4kDa); ④, 1x 3A-mSA+2x 3B (149.4kDa); ⑤, 2x 3A-mSA+2x 3B (174.4kDa); ⑥, 3x 3A-mSA+4x 3B (324.2kDa). (The software lane 1D was used to draw the graph.) (“3A-SUP” stands for “Triple SpyTag-SUP”, “3A-mSA” for “Triple SpyTag-mSA”, and “3B” is the abbreviation of “Triple SpyCatcher”)
We found that some new bands appeared above the band of 3B when it was mixed with monomers containing A, which demonstrated that our idea of forming functional hydrogel was executable. The products were mainly oligomers (Fig. 2 A-F, Table 1), for it is easy to form loops, which hindered the linkage between different monomers at such low concentration. Interestingly, with the restriction that A is equal to B in number, and the content of 3B was constant initially, the crosslinking ability at low concentration of these monomers were different with each other by comparing the surplus content of 3B. What’s more, it was surprising that the position of 3B band (~62kDa) was not accord with its theoretical weight (55.4kDa). Further experiments will be done to understand the differences.
If you want to learn more about Peking’s polymer network and the role of SUP in this network, please click here http://parts.igem.org/Part:BBa_K1989000", http://parts.igem.org/Part:BBa_K1989001" or http://parts.igem.org/Part:BBa_K1989002".
[Zakeri et al., 2012] Zakeri B, Fierer JO, Celik E, Chittock EC, Schwarz-Linek U, Moy VT, Howarth M. (2012). Peptide tag forming a rapid covalent bond to a protein, through engineering a bacterial adhesin. Proc Natl Acad Sci U S A. 20;109(12)
Sequence and Features
- 10COMPATIBLE WITH RFC
- 12COMPATIBLE WITH RFC
- 21COMPATIBLE WITH RFC
- 23COMPATIBLE WITH RFC
- 25COMPATIBLE WITH RFC
- 1000COMPATIBLE WITH RFC
|Protein data table for BioBrick BBa_ automatically created by the BioBrick-AutoAnnotator version 1.0|
|Nucleotide sequence in RFC 25, so ATGGCCGGC and ACCGGT were added (in italics) to the 5' and 3' ends: (underlined part encodes the protein)|
ATGGCCGGCGTTGATACC ... GCTCATATTACCGGT
ORF from nucleotide position -8 to 345 (excluding stop-codon)
|Amino acid sequence: (RFC 25 scars in shown in bold, other sequence features underlined; both given below)|
|Sequence features: (with their position in the amino acid sequence, see the list of supported features)|
|Amino acid composition:|
|Amino acid counting|
|Plot for hydrophobicity, charge, predicted secondary structure, solvent accessability, transmembrane helices and disulfid bridges|
|Alignments (obtained from PredictProtein.org)|
|Predictions (obtained from PredictProtein.org)|
|Subcellular Localization (reliability in brackets)|
|Gene Ontology (reliability in brackets)|
| The BioBrick-AutoAnnotator was created by TU-Munich 2013 iGEM team. For more information please see the documentation.|
If you have any questions, comments or suggestions, please leave us a comment.
This part has been improved:BBa_K2273015