Part:BBa_K2842690
Intein Monomer 2: GFP reporter flanked with orthogonal inteins
Intein Monomer 2 | |
---|---|
Function | Create intein-spliced polymers |
Use in | E. coli cells |
Chassis Tested | DH5α cells |
Abstraction Hierarchy | Composite Device |
Related Device | BBa_K2842680 |
RFC standard | RFC10,RFC12,RFC21,RFC23 & RFC25 compatible |
Backbone | pSB1C3 |
Submitted by | [http://2018.igem.org/Team:UCL UCL iGEM 2018] |
This construct is designed to work with Intein Monomer 1, it is flanked with the corresponding split intein fragments for protein trans-splicing. An GFP reporter is flanked by the AcelTerL-C intein and the Npu-N intein allowing for polymerisation by protein trans splicing with other proteins flanked by 2 compatible split inteins. Like Intein Monomer 1 it has SapI cassettes to facilitate the exchange of the sequences that are flanked by inteins. This enables the polymerisation of any protein that can be synthesised.
Characterisation by Team UCL 2019
Team UCL 2019 was planning to use intein as part of their modular drug delivery system to join binding peptides to our delivery vesicles (encapsulins) post-expression since one of our main concerns about our engineered encapsulin vehicle was that the targeting peptides loaded onto the encapsulin monomers’ surface may hinder proper encapsulin assembly. We thought rather than fusing the targeting peptide directly to the monomers, we could fuse the relatively small intein unit to the monomers (not hindering assembly), then subsequently add the targeting peptide with a matching intein and have it splice onto the surface of the already assembled encapsulin shells. As a result, we sought to characterise the 2018 UCL iGEM team’s intein part further. We investigated the burden of high levels of intein production in E.coli by monitoring cell growth with and without the recombinant protein and observed the solubility of intein hybrid proteins.
In Vivo Expression
Growth curves of BL21 (DE3) bacteria carrying an empty plasmid (pSB1C3), uninduced bacteria carrying BBa_K2842690 and induced bacteria carrying BBa_K2842690 were evaluated. Induction was done following the protocol listed in the protocols section, briefly: BL21 (DE3) competent cells were transformed with empty pSB1C3 plasmids and pSB1C3 plasmids containing the inserted sequence of the part BBa_K2842690. Following successful transformation, starter cultures were grown overnight, re-inoculated into 50ml scale-up cultures and incubated at 37 °C until they reached an OD600 of 0.6. They were then induced with IPTG and grown at 25 °C or 37 °C. Figures below show the measurements that were obtained at each time after inoculation and induction.
Next, we ran the soluble and insoluble fractions of cell lysate on an SDS PAGE and a Western Blot using a Strep-Tactin antibody because the part has a Strep-tag. From Figures 4 and 5 we can see that the protein (highlighted by the red rectangle) expressed at 37 °C is completely insoluble, while expressed at 25 °C it is only barely soluble.
Our results suggest that lower temperature of culture growth will result in higher yield of functional GFP/intein protein (Figure 6), even though the bacterial rate of growth would drop (Figures 2 and 3). This is likely the result of the protein being more soluble after expression at 25 °C.
In Vitro Expression
Finally, attempting to solve the issue of solubility we decided to BBa_K2842690 using cell-free protein synthesis (CFPS) with bacterial cell lysate. By measuring the fluorescence of the reaction over time, we estimate to have produced 0.58±0.27 mg/L of soluble GFP/intein hybrid protein, which is incredibly low for a CFPS reaction. As seen in Figure 8, majority of the protein is still insoluble (band at ~55 kDa).
Conclusion
As it was not possible to express enough soluble intein protein, we decided not to use inteins in creation of our encapsulin-based drug delivery system.
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000INCOMPATIBLE WITH RFC[1000]Illegal BsaI site found at 1536
Illegal BsaI.rc site found at 28
Illegal SapI site found at 1151
Illegal SapI.rc site found at 422
None |