Reporter

Part:BBa_K1071014

Designed by: Team Marburg 2013   Group: iGEM13_Marburg   (2013-09-19)
Revision as of 18:10, 12 October 2013 by Lucas (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

RFP-MTS

RFP (BBa_E1010) with a C-terminal membrane translocation sequence (MTS). The origin is the protein YlxH from the bacterium Geobacillus thermodenitrificans. The MTS has a hydrophobic site and an affinity for membranes.

Usage and Biology

An important aspect in synthetic biology is the cellular compartmentalization of complex enzyme reactions. Therefore, it would be great to establish simple and autonomous parts that allow the recruitment of synthetic components to cellular membranes – eventually with specificity to certain lipid environments (e.g. anionic phospholipid clusters).

Therefore, we decided to establish membrane scaffolds, which are known as membrane targeting sequences (MTS). These sequences form amphipathic helices, which autonomously bind to membranes often with specificity to anionic phosphor lipids (compare to: Parlitz et al., 2007, JBC and Szeto et al., 2003, JBC). To challenge that idea, we fused the reporter RFP (red fluorescent protein) with a C-terminal membrane targeting sequence (MTS). The origin is the protein YlxH from the bacterium Geobacillus thermodenitrificans. To show the functionality of the MTS, we fused the targeting sequence to the C-terminus of reporter RFP to gain RFP-MTS. The construct was transformed into Escherichia coli and an IPTG inducible promoter controlled expression of the RFP-MTS fusion protein (Figure).

RFP-MTS localized at the membrane with a slight preference for the poles, which in E. coli are enriched in anionic phospholipids. Taken together, we were able to create an additional BioBrick for our toolbox and to improve the in the registry existing RFP.

[1] MTS

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BamHI site found at 676
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal AgeI site found at 555
    Illegal AgeI site found at 667
  • 1000
    COMPATIBLE WITH RFC[1000]


[edit]
Categories
Parameters
None