Difference between revisions of "Part:BBa K3037009"

Revision as of 23:36, 21 October 2019

HRP+Strep-tag

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

HRP

Since the HRP-Strep part is a composite part, the correct functioning of the HRP activity was already characterized individually. Please check for that the characterization of this BioBrick BBa_K1800007.

Strep-tag

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).

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.