Composite

Part:BBa_K3037009

Designed by: Arnau Pérez Roig   Group: iGEM19_TU_Dresden   (2019-10-15)
Revision as of 23:17, 21 October 2019 by Psantos (Talk | contribs)

HRP+Strep-tag

HRP+Strep-tag
Function Expression
Use in Escherichia coli
RFC standard Freiburg RFC25 standard
Backbone pSB1C3
Experimental Backbone pOCC97
Submitted by Team: TU_Dresden 2019


Overview

The TU Dresden 2019 team designed this biobrick using the BBa_K823038 (more information).

HRP+Strep-tag was inserted into the pSB1C3 vector for transformation and expressed in Escherichia coli.

The HRP was made from BBa_K1800002 but adapted to the Freiburg RFC25 standard

Biology

The metalloenzyme horse radish peroxide is widely used in many biochemical and immunological applications. This enzyme on its own does not give any visual readout but however upon addition of a suitable substrate, HRP oxidizes it and yields a colour change that can be spectrophotometrically analysed. One such common example for chromogenic substrate is TMB (3,3',5,5'-Tetramethylbenzidine) that HRP oxidizes. Additionally, an advantage of using HRP includes its stability and small size, hence reducing the interference during conjugation reactions such as for secondary antibody detection. Furthermore, it is economical in comparison with other alternative enzymes like Alkaline Phosphatase.

Characterization

The Strep-tag BBa_K823038 was supposed to be used for purification.

The protocol used was “Expression and purification of proteins using Strep-Tactin†of IBA Lifescience preparing the same buffers described in this protocols without EDTA to not harm the activity of HRP. From the results of the purifications we concluded that the Strep-tag is not working properly for column purification and should therefore only be used for Western Blots. See more information regarding this in the original registry of this BioBrick (BBa_K823038).

T--TU Dresden--Strep-tag purification BBa 3037009.png

Sequence

NOTE: Please be aware, that by combining all the basic parts used for this composite part, the registry automatically inserted a RFC23 scar. However, the design and our cloning strategy is based on RFC25.


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    INCOMPATIBLE WITH RFC[12]
    Illegal NheI site found at 151
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BglII site found at 393
    Illegal XhoI site found at 477
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]


[edit]
Categories
Parameters
None