Difference between revisions of "Part:BBa K1355003"

Line 2: Line 2:
  
  
The Bioaccumulative Biobrick is composed of our “Essential biobrick”  (BBa_K1355001) + a Metal Binding Peptide - MBP (BBa_K346004) available in the database of the iGEM since 2010, as represented below:
+
We designed a biobrick device to bind and inactivate Hg. It is composed by two parts: Essential biobrick (BBa_K1355001) attached to the MBP biobrick (BBa_K346004) that was synthesized by iGEM Peking 2010. As described by the team, this MBP design was based on the tandem of two metal binding domains to make a high performance and less energy consuming metal binding peptide. The idea came from the high similarity of the C-terminal metal binding domain with MerR family TFs, which indicates a similar metal recognition mechanism and metal-protein complex structure.
 +
The Mercury ions accumulator device biobrick (BBa_K1355003) has dual function: A) In reverse: transcription of MerR regulator protein; and B) In forward: transcription of MerP - MerT - Metal Binding Peptide proteins, as represented below:
  
 
[[File:L5.jpg]]
 
[[File:L5.jpg]]
  
In mercury’s presence, MerR protein will bind to it so MerT, MerP and Metal Binding Protein (MBP) proteins are synthesized and bioaccumulation will start! MerP and MerT protein are responsible for mercury’s transport of mercury from the periplasm to cytoplasm, leading it to MBP! The MBP binds to the mercury in the cytoplasm, inactivating it.
+
 
 +
In absence of mercury, MerR forms a MerR-promoter-operator complex, preventing RNA polymerase to recognize the promoter, consequently, messengers RNA for MerPT and MBP will not be transcript. In presence of Hg2+, MerR protein binds to this element and dissociates from the promoter-operator complex, allowing MerPT and MBP expression, as represented below:
 +
 
 +
[[File:bc7.png]]
 +
 
 +
When MerT, MerP and Metal Binding Protein (MBP) proteins are synthesized the bioaccumulation will start! MerP and MerT protein are responsible for mercury’s transport of mercury from the periplasm to cytoplasm, leading it to MBP! The MBP binds to the mercury in the cytoplasm, inactivating it.
  
 
[[File:MercuryBacterBIOACC.jpg]]
 
[[File:MercuryBacterBIOACC.jpg]]
  
Figure 1:  Mercury Bacter Hg bioaccumulator (DH5-alpha transformed with BBa_K1355003)
+
Mercury Bacter Hg bioaccumulator (DH5-alpha transformed with BBa_K1355003)
 
   
 
   
 
<!-- -->
 
<!-- -->

Revision as of 03:39, 17 October 2014

Mercury ions accumulator device


We designed a biobrick device to bind and inactivate Hg. It is composed by two parts: Essential biobrick (BBa_K1355001) attached to the MBP biobrick (BBa_K346004) that was synthesized by iGEM Peking 2010. As described by the team, this MBP design was based on the tandem of two metal binding domains to make a high performance and less energy consuming metal binding peptide. The idea came from the high similarity of the C-terminal metal binding domain with MerR family TFs, which indicates a similar metal recognition mechanism and metal-protein complex structure. The Mercury ions accumulator device biobrick (BBa_K1355003) has dual function: A) In reverse: transcription of MerR regulator protein; and B) In forward: transcription of MerP - MerT - Metal Binding Peptide proteins, as represented below:

L5.jpg


In absence of mercury, MerR forms a MerR-promoter-operator complex, preventing RNA polymerase to recognize the promoter, consequently, messengers RNA for MerPT and MBP will not be transcript. In presence of Hg2+, MerR protein binds to this element and dissociates from the promoter-operator complex, allowing MerPT and MBP expression, as represented below:

Bc7.png

When MerT, MerP and Metal Binding Protein (MBP) proteins are synthesized the bioaccumulation will start! MerP and MerT protein are responsible for mercury’s transport of mercury from the periplasm to cytoplasm, leading it to MBP! The MBP binds to the mercury in the cytoplasm, inactivating it.

MercuryBacterBIOACC.jpg

Mercury Bacter Hg bioaccumulator (DH5-alpha transformed with BBa_K1355003)

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    INCOMPATIBLE WITH RFC[12]
    Illegal NheI site found at 988
  • 21
    COMPATIBLE WITH RFC[21]
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal NgoMIV site found at 586
    Illegal NgoMIV site found at 1160
  • 1000
    INCOMPATIBLE WITH RFC[1000]
    Illegal SapI site found at 579