Team:ESBS-Strasbourg/proteolux/scientific/proteoluxbasic

{{ESBS-Strasbourg/Temp2}} {|
<html>


<div style="position: absolute; width: 965px; height: 20px; z-index: 1; top: -40px; background-color:#222222" id="layer1">

<font color="#FFFFFF">
<img border="0" src="https://static.igem.org/mediawiki/2010/3/33/ESBS-Strasbourg-Proteolux-logo-back.png" width="120" height="28" align="right" hspace="10"></font>
<a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/contact" style="text-decoration: none">
<font color="#FFFFFF">Contact</font></a>&nbsp;&nbsp;&nbsp;
<a style="text-decoration: none">
<font color="#FFFFFF">|</font></a>&nbsp;&nbsp;&nbsp;
<a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/sitemap" style="text-decoration: none">
<font color="#FFFFFF">Sitemap</font></a>

<p>&nbsp;</div>


<p>
<head>
    <meta http-equiv="content-type" content="text/html;charset=utf-8" />
    <title>ESBS-Strasbourg</title>
 
 
<script type="text/javascript"><!-- 
var delay=7000
var ie4=document.all
var curindex=0
var totalcontent=0
function get_total(){
if (ie4){
while (eval("document.all.content"+totalcontent))
totalcontent++
}
else{
while (document.getElementById("content"+totalcontent))
totalcontent++
}
}
function contract_all(){
for (y=0;y<totalcontent;y++){
if (ie4)
eval("document.all.content"+y).style.display="none"
else
document.getElementById("content"+y).style.display="none"
}
}
function expand_one(which){
contract_all()
if (ie4)
eval("document.all.content"+which).style.display=""
else
document.getElementById("content"+which).style.display=""
}
function rotate_content(){
get_total()
contract_all()
expand_one(curindex)
curindex=(curindex<totalcontent-1)? curindex+1: 0
setTimeout("rotate_content()",delay)
}
window.onload=rotate_content
//--></script>
</head>
 
<style> 
body{
background-color: red;
font: 11px Arial;
color: #888888;
padding: 5px 5px 5px 5px;
     }
 
b{
color: #ffffff;
}
 
.heading{
color: #FFF;
font: 14px century gothic;
padding: 5px 5px 2px 5px;
font-weight: bold;
}
 
.titlebg{
position: absolute;
top: 0px;
background-color: #000000;
width: 965px;
height: 50px;
  /* for IE */
  filter:alpha(opacity=60);
  /* CSS3 standard */
  opacity:0.6;
 z-index:3;
      }
 
.title{
position: absolute;
top: 243px;
float: left;
font: 35px Trebuchet MS;
color: #FFF;
padding-top: 5px;
padding-left: 10px;
z-index: 4;
       }
 
.header{
z-index: 1;
position: absolute;
top: 0px;
height: 293px;
     }
 
.menu{
z-index: 5;
position: absolute;
top: -20px;
font: 17px Trebuchet MS;
text-align: center;

           }
 
.menubg{
position: absolute;
top: 243px;
background-color: #000000;
width: 965px;
height: 50px;
  /* for IE */
  filter:alpha(opacity=60);
  /* CSS3 standard */
  opacity:0.6;
z-index:2;
      }
a:link{color:#fff;}
a:visited{color:#fff;}
a:active{color:#fff;}
</style>
 
<body bgcolor="#414141" style="background-color: #800000">
<body style="background-color: #800000">
 
 
<div class="header">
<div class="titlebg">
</div>
<div class="title">
</>
</div>

<div id="content0" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/5/52/ESBS-Strasbourg-Ab6.png" width="965px" height="293px" border="0">
</div>
<div id="content1" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/b/be/ESBS-Strasbourg-Ab1.png" width="965px" height="293px" border="0">
</div>
<div id="content2" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/2/29/ESBS-Strasbourg-Ab2.png" width="965px" height="293px" border="0">
</div>
<div id="content3" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/6/67/ESBS-Strasbourg-Ab3.png" width="965px" height="293px" border="0">
</div>
<div id="content4" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/2/2e/ESBS-Strasbourg-Ab4.png" width="965px" height="293px" border="0">
</div>
<div id="content5" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/9/9f/ESBS-Strasbourg-Ab5.png" width="965px" height="293px" border="0">
</div>
<div id="content6" style="display:none">
<img src="https://static.igem.org/mediawiki/2010/5/52/ESBS-Strasbourg-Ab6.png" width="965px" height="293px" border="0">
</div>



<div class="menubg">
</div>
 
<div class="menu">
 
<!--[if lt IE 7]>
<script type="text/javascript">
 
sfHover = function() {
	var sfEls = document.getElementById("nav").getElementsByTagName("LI");
	for (var i=0; i<sfEls.length; i++) {
		sfEls[i].onmouseover=function() {
			this.className+=" over";
		}
		sfEls[i].onmouseout=function() {
			this.className=this.className.replace(new RegExp(" over\\b"), "");
		}
	}
}
if (window.attachEvent) window.attachEvent("onload", sfHover);
 
</script>
<![endif]-->
<style type="text/css"> 
/* general styling */
*{margin:0;padding:0}
body {
	font: x-small Verdana, Arial, Helvetica, sans-serif;
	text-align:left;
	padding:20px;
	}
.outer{
	padding:0px 0 0 0;
	width:965px;
	margin:auto;
	position:relative;
	text-align:center;
}
 
/* drop up */
ul#nav,ul#nav ul {
	margin: 0;
	padding: 0;
	list-style: none;
}
ul#nav {
	width:1100px;
	height:25px;
	
}
 
ul#nav li {
	position: relative;
	float: left;
	width:240px;
	height:75px;
	color:#fff;
	text-align:left;

}
ul#nav li a {
	text-decoration: none;
	color:#fff;
       
}
#nav li ul {
	position: absolute;
	left: 0; 
	top:70px;
	margin-left:-999em;
	border:none;
	height:193px;
	width:153px;
	background:#000;
 /*opacity for IE5+*/
  filter: alpha(opacity=60);
  /*opacity for older Mozilla browsers*/
  -moz-opacity: 0.6;
  /*opacity for mozilla/safari*/
  opacity: 0.6;
}
ul#nav li li{height:auto;border:none;}
ul#nav li li a{
	color:red;
	padding:2px 5px 2px 5px;
	display:block;
}
ul#nav li:hover ul, 
ul#nav li.over ul {
	margin-left:0;
}
ul#nav li:hover,
ul#nav li.over,
ul#nav li:hover a,
ul#nav li.over a {color:#800000}
 
ul#nav li:hover li a,ul#nav li.over li a{color:#fff;}
ul#nav li li a:hover{color:#800000; background-color: #fff;}
ul#nav li p {padding:0px;}
ul#nav li.last,ul#nav li.last ul{border:none;width:193px;}
 
</style>
 
<div class="outer">
	
	<ul id="nav">
		<li>
			<p><br/><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HOME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</a></p>
			
			
		</li>




		<li>
			<p><br/><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/overview">Overview&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</a></p>
			<ul>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/overview/proteoluxbasic">
				ProteOlux Basic</a></li>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/overview/proteoluxplus">
				ProteOlux Plus</a></li>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/overview/proteoluxpro">
				ProteOlux Pro</a></li>

                               
			</ul>
		</li>


		<li>
			<p><br />
				<a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/scientific">
			Scientific Background&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</a></p>
			<ul>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/scientific/proteoluxbasic">
				ProteOlux Basic</a></li>
                                <li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/scientific/proteoluxplus">
								ProteOlux Plus</a></li>
                                <li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/scientific/proteoluxpro">
								ProteOlux Pro</a></li>

				
			</ul>
		</li>


		<li>
			<p><br/><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/application">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Application</a></p>                 
                        <ul>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/application/cancer">
				Cancer</a></li>
				<li><a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/application/neuro">
				<font size="3">Neurodegenerative Diseases</font></a></li>

				
			</ul>

</div>
 


</div>
 
</div>
</p><p>
<body style="background-color: #800000">
<style> 
 
p{
padding: 5px;
}
 
.heading{
font: century gothic;
color: #ffffff;
}
 
table {
left:0px;
background-color: #414141;
cell-padding: 5px;
border-collapse:collapse;
border-width: 0px;
}
 
#content{
background-color:#222222;
border:0px;
font: 12px Arial;
color: #cccccc;
}
 
#leftmenu{
position: relative;
top: 900px;
border-right:10px transparent;

}
 
td{
color: #cccccc;
border-collapse:collapse;
}
 
#logo
{
background-color: #ffffff;
width: 180px;
height: 180px;
 
}
 
.desc
{
padding: 5px 10px 5px 5px;
text-align: justify;
}
</style>
 
<img src="http://i1001.photobucket.com/albums/af132/igemcalgary/blankspace.gif" height="205px">
<br>

<table cellspacing=0>
<tr>
<td width="210" rowspan=20 bgcolor="#414141" valign="top">
<br>
<div class="heading">ProteOlux Basic</div>
<div class="desc">

<ul>
<li><a href="#degradation">Degradation System</a></li>
<li><a href="#light">Light detection system</a></li>
<li><a href="#system">Final construction</a></li>
<li><a href="#chassis">Introduction to various chassis</a></li>

</ul>

</div>
</p></div>
</td>
<td width="10" rowspan=20 bgcolor="#222222">
</div>

<td width="750" bgcolor="#414141" valign="top">
<div class="desc">
<div class="heading">
<a name="overview"></a>
 Overview
</div>
<br>

Proteolux is a light-controllable specific protein degradation system. The system contains several parts: the bacterial ClpXP protease from E. Coli and the specific recognition sequence (DAS-tag) for ClpX for the degradation part as the photoreceptor protein phytochrome B (PhyB) and the phytochrome interacting factor 6(PIF6) from A. thaliana for the light-dependent part of the system.
<br><br>

The ClpXP proteases consist of three main parts: the ClpX unit and two units of ClpP. The ClpX forms a hexametric ring and binds to a double heptamer of ClpP. The ClpX is responsible for recognizing proteins bearing a specific degradation tag, unfolding and leading them into the catalytic core of the enzyme, where two ClpP subunits break down the peptides bonds. 
<br><br>

PhyB is characterized by a red/far-red photochromicity. Through red-light absorption (650–670 nm) PhyB undergoes a rapid conformational change from its ground state Pr to its active state Pfr. The structural change allows the binding of different interacting factors (PIF).The process is completely reversible through absorption in the near infra-red spectrum (705-740nm). PhyB is fused to the N terminus of a trimeric form of ClpX that lacks the N-terminus in which the subunits were connected with a flexible linker to stabilize the enzyme. 

<br><br>

Target proteins are fused to the PIF and tagged with the specific degradation sequence which, through light activation, brings the degradation sequence in proximity to ClpX and guides them to the catalytic core of the protease. Therefore a specific degradation of proteins containing the degradation sequence can be induced by a light signal.


<br>
</div>
<br>
</td>
</tr>

<tr>
<td width="750" height="10" bgcolor="#222222">
</td>
</tr>



<td width="750" bgcolor="#414141" valign="top">
<div class="desc">
<div class="heading">
<a name="degradation"></a>
 Degradation system
</div>
<br>
<p><b>Description</b></p>
ClpXP is an AAA protease present in bacteria, consisting of two main components, ClpX and ClpP. The ClpX is a hexamer consisting of six identical subunits. It recognizes specific degradation tags of target substrate proteins, unfolds them in an ATP-consuming hydrolysis reaction, and uses additional cycles of ATP hydrolysis to translocate the unfolded polypeptide into an interior chamber of ClpP, where proteolysis takes place. ClpP is a multi-subunit serine peptidase, in which the proteolytic active sites reside within a barrel-shaped structure. 
<br><br>

<center>
<img src="https://static.igem.org/mediawiki/2010/d/d7/ESBS-Strasbourg-Clpp.png" width="220px" height="316px">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img src="https://static.igem.org/mediawiki/2010/e/e7/ESBS-Strasbourg-clpx.png" width="217px" height="316px">
</center>
<br><br>
In E. coli, the adaptor SspB tethers ssrA-tagged substrates to the ClpXP protease, causing a modest increase in their rate of degradation. 

<br><br>
<p><b>The recognition sequence</b></p>
In the native organism, the SsrA tag is added to incomplete proteins whose translation has been aborted. Thus, misfunctionnal proteins do not accumulate inside the cell. The ssrA tag is a natural well-characterized recognition for ClpXP-degradation sequence in E. Coli. It is composed of the 11 amino acid sequence AANDENYALAA, localized at the C-terminal of the target protein. ClpX recognizes the last three residues LAA(Leu9, Ala10 and Ala11). Proteins with C-terminal LAA- tags are degraded rapidly in the cell, even without presence of SspB.
<br><br>
To engineer controlled degradation, Baker and Sauer (2006) designed a series of modified SsrA tags that have weakened interactions with ClpXP. The DAS-tag presents one of these artificial sequence; its Kd value is significantly higher than the one of wild type SsrA, thus degradation of DAS-tagged proteins is not significant within the range of physiological concentrations. There is an N-terminal equivalent to the DAS-tag, the λO- tag. In the absence of SspB, substrates bearing the artificially altered tags are stable; however, through the action of the adaptor protein SspB, DAS- or λO –tagged proteins are significantly degraded.
<br><br>
<p><b>Substitution of the adaptor</b></p>
The role of the adaptor-protein SspB has been assumed by Pif6 in our system, only light-induced activation can lead to binding and efficient degradation of DAS bearing constructs. 
<br><br>
<img src="https://static.igem.org/mediawiki/2010/8/82/ESBS-Strasbourg-ImageProteinfinal%2B.png" width="239px" height="168px" align="left">

<br>
<p><span>The target protein will be fused to Pif6 and to the specific degradation tag.<br>
<br>To avoid problems with the accessibility or an increased activity of the target protein we provide two different variants: the C-terminal degradation tags, with the target protein construct [PIF6-linker-Protein-DAS] and the N-terminally fused λO-tag resulting in the construct [λO-Protein-linker-PIF6]. </span></p>



<br><br>
Most bacterial proteins tolerate C-terminal fusions and the C-termini of most proteins are solvent accessible. The C-terminal fusion of PIF6 using the N-terminal degradation tag λO is consequently more promising to succeed, as the specific degradation sequence consists of very few amino acids (3 for the DAS-tag and 11 for the λO –tag) which do not perturb protein activity in most of the cases.<br><br>
Nevertheless, if possible, we recommend to test the activity of the target protein within the two constructs before the implementation of Proteolux.


<br>
</div>
<br>
</td>
</tr>



<tr>
<td width="750" height="10" bgcolor="#222222">
</td>
</tr>


<tr>
<td width="750" bgcolor="#414141" valign="top">
<div class="heading">
<a name="light"></a>
 Light detection system
</div>
<div class="desc">
<br>
As previously mentioned, the Phytochrome/PIF system has been chosen as light detection system. There are several advantages of this system: it offers a second timescale control which is significantly faster than chemically induced translocation systems, further it is perfectly reversible as it has been proven to be robust being cycled over a hundred times by alternating red and infrared illumination with no measurable decrease in recruitment ratios over time [41]. 
<br><br>

<p><b>Description</b></p>
Phytochromes are photoreceptive signaling proteins responsible for mediating many light-sensitive processes in plants. They detect red and near-infrared light through the photoisomerization of a covalently bound tetrapyrrole chromophore such as phycocyanobilin (PCB) for plant phytochromes. This photoisomerization event is coupled to an allosteric transition in the phytochrome between two conformational states called Pr (red-absorbing) and Pfr (far-red-absorbing). <br><br>
Upon stimulation with red light (650 nm), the phytochrome B (PhyB) protein binds directly to a downstream transcription factor, the phytochrome interaction factor (PIF). PIF is a nuclear-localized, basic helix–loop–helix (bHLH) factor initially isolated as interacting with the non-photoactive, C-terminal domain of Arabidopsis PhyB. The process is completely reversible through absorption in the near infra-red spectrum (705-740nm).
<br><br>
All plant phytochromes can be divided into an N-terminal photo sensory domain and a C-terminal dimerization domain. The N-terminal photo sensory domain comprises four consecutive subdomains called P1, P2/PAS, P3/GAF, and P4/PHY (named sequentially from the N terminus), the C-terminal domain consists of two subdomains, the PAS-A and PAS-B domains and the histidine kinase–related domain (HKRD) [45].
<br><br>


<img src="https://static.igem.org/mediawiki/2010/c/c3/ESBS-Strasbourg-Phybdomain.png" width="148px" height="270px" align="left">
<br>
<p><span>The P1 domain is not essential for the function of PHYB. Deletion of amino acids 1–57 of Arabidopsis PHYB yields a protein with full activity [30]. In contrast, the P2/PAS and P3/GAF domains form the essential photo sensory core domain. These domains contain a bilin lyase activity, which is responsible for the binding of the chromophore to a cysteine residue in the P3/GAF domain. The P2/PAS and P3/GAF domains play critical roles in photo sensing, whereas the P4/PHY domain is necessary for fine tuning phytochrome activity. The autophosphorylation and phytochrome-directed phosphorylation of other proteins, such as PIF3 is attributed to a serine/threonine kinase domain located in the N-terminal [1]. Deletion of the P4/PHY domain increases the dark reversion rate (i.e., the instability of the Pfr conformation) and causes a blue shift in absorption by both Pr and Pfr. The PAS-A and PAS-B domains of PHYB are necessary for dimerization and nuclear localization, whereas PAS-A, PAS-B, and the HKRD domains are necessary for nuclear speckle formation [1]. Dimerization is required for PhyB full activity.  </span></p>
<br><br><br><br>

<p><b>Construction Choice</b></p>
To avoid potential sterical hindrance for ClpX activity we attempted to reduce its size as much as possible.
<br><br>
The light-sensitive interaction between PHYB and PIF3 has been mapped to the 650-residue amino- terminal photosensory core of PHYB [30]. The improved understanding of these mechanisms has been helpful for the design of the first engineered photoreceptors that utilized the interaction between PhyB and PIF3 to achieve light regulation of target proteins.
<br><br>


<img src="https://static.igem.org/mediawiki/2010/5/59/ESBS-Strasbourg-PhyB.png" width="192px" height="316px" align="left">

<br>
<p><span>Leung et al. put the association of the GTPase Cdc42 with its effector protein WASP under red-light control. When in complex with PhyB-Cdc42, PIF3-WASP promoted actin polymerization in vitro; use in vivo was not demonstrated. Lastly, Voigt and colleges employed the light-dependent interaction between PhyB and PIF6 to activate target proteins in vivo. Thereby they have shown that the PIF-interaction with the PhyB photo sensory core (residues 1–642) is irreversible in infrared light. By assaying PIF6, which has the strongest interactions of all previously reported PIF domains, against different variants of PhyB they demonstrated that the tandem C-terminal PAS domains (residues 1-908) of PhyB are necessary to confer rapid photo reversibility under infrared light. </span></p>
<br>
We have tested different variants for the implementation of our system: the residues 1-908 and the photo sensory core domain residues 1-642 for the phytochrome B constructs in combination with PIF3 (residues 1-100) and PIF6 (residues 1-100).<br><br><br><br><br>
Our tests confirmed the findings of Voigt et al. that the tandem C-terminal PAS domains of PhyB are necessary to maintain the reversibility of the system. The Proteolux system therefore uses the PhyB residues 1-908 in combination with PIF6. The restriction of enzyme activity due to sterical hindrances could be reduced to less than 5% for the optimized final system. <br><br>

<p><b>The chromophore</b></p>

Since the plant phytochromes PhyA and PhyB employ the modified tetrapyrroles PCB or PΦB which are not available in most tissues and cell types, these chromophores must be supplied either exogenously or endogenously. It is possible to produce the holophytochrome in E. coli by co-expressing two genes from Synechocystis for chromophore biosynthesis together withcyanobacterial chromophore 1(Cph1) from the same organism [15],[35]. Heme oxygenase converts host heme to biliverdin IXK which is then reduced to phycocyanobilin via phycocyanobilin:ferredoxin oxidoreductase. The Cph1 apophytochrome is able to autoassemble with the phycocyanobilin in vivo to form the fully photoreversible holophytochrome.<br><br>
Nevertheless, we decided to use the exogenous way by adding exogenous PCB as the endogenous way to produce the holoenzyme can lead to the production of toxic side-products. 



</div>
<br>
</td>
</tr>



<tr>
<td width="750" height="10" bgcolor="#222222">
</td>
</tr>


<td width="750" bgcolor="#414141">
<div class="desc">
<div class="heading">
<a name="system"></a>
 Final construction: Light controllable protease 
</div>
<br><br>
PhyB is fused to the N terminus of a trimeric form of ClpX-N in which the subunits were connected with a flexible linker to stabilize the enzyme. So the ClpX-hexamer is composed of two trimers fused to PhyB at its N-terminal.
<br><br>
The reason for this particular design is that N-domain dimerization is needed to stabilize the active hexameric form of ClpX [14]. So replacing this domain, as in our construction, would result in weaker hexamerization. <br><br>




<img src="https://static.igem.org/mediawiki/2010/8/87/ESBS-Strasbourg-System.png" width="192px" height="317px" align="left">
<p>&nbsp;</p>
<br><br>
<p><span>In our system the adaptor-role is assumed by PIF, which will bind to PhyB following light-induction. Target proteins are fused to PIF and tagged with the specific degradation sequence which, through light activation, brings the degradation sequence in proximity to ClpX and guides them to the catalytic core of the protease. Therefore a specific degradation of proteins containing the degradation sequence can be induced by a light signal.<br><br> 
The system can be constitutively expressed in the chassis but it remains inactive until light-induction. However, it is expected to stay active for the background of naturally SsrA-tagged proteins, creating no interference with the natural occurring proteins.
</span></p>
<p>&nbsp;</p>
<br><br>




</div>
<br>
</td>
</tr>



<tr>
<td width="750" height="10" bgcolor="#222222">
</td>
</tr>


<td width="750" bgcolor="#414141">
<div class="desc">
<div class="heading">
<a name="chassis"></a>
 Introduction to various chassis 
</div>
<br><br>
The ProteoLux® system can be applied to various chassis. To optimize the expression we developed different versions of ProteoLux® based on an improved codon usage especially adapted to the target host system : 
<br><br>
<center>
<ul>
<li>Proteolux bacteria </li>
<li>Proteolux eucaria </li>
<li>Proteolux mammalia </li>
</ul>
</center>
<br><br>


<b>ProteoLux® bacteria</b> has been designed for an optimized expression in bacteria, the codon usage is primarily adapted to the class of proteobacteria. Proteobacteria are a major group of bacteria. They include a wide variety of pathogens, such as Escherichia, Salmonella, Vibrio, Helicobacter and many other notable genera. Others are free-living, and include many of the bacteria responsible for nitrogen fixation or involved in the carbon cycle.   <br><br>


<b>ProteoLux® bacteria</b> has been successfully implemented in various representatives of proteobacteria, including Caulobacter crescentus, Escherichia Coli, Pseudomonas fluorescens , Salmonella enterica and Vibrio fischeri.
<br><br>

<b>ProteoLux® eucaria</b> has been designed for the use in eukaryotic microorganism like Saccharomyces cerevisiae that represents one of the most intensively studied unicellular eukaryotic model organism in molecular and cellular biology. Many proteins important in human biology were first discovered by studying their homologs in S. cerevisiae; these proteins include cell cycle proteins, signaling proteins, and protein-processing enzymes.  
<br><br>

<b>ProteoLux® eucaria</b> has further been tested in Schizosaccharomyces pombe, another yeast species and Ashbya gossypi, a model organism for filamentous fungi.  
<br><br>

<b>ProteoLux® mammalia</b> aims at the use in the medical research field, its codon usage has been adapted to the human species.  
<br><br>
The system can be implemented in different mammalian cell lines in vitro, including the human cell lines HEK293, K562 and HeLa, embryonic mouse fibroblast cells 3T3 as the baby hamster kidney cell line BHK-21.  
<br><br>

For in vivo implementations you should consider the use ProteoLux® Pro, which presents a special variant of ProteoLux® mammalia.  
<br><br>


The introduction of ProteoLux® can be realized with common transformation, transfection or transduction methods. It requires the introduction of the light inducible degradation complex ClpX-PhyB as the ClpP-gene for non-bacterial systems.  <br><br>

In proteobacteria species encode the ClpXP protease in their proper genome. The naturally present ClpP-subunit assembles auto-catalytically with ClpX, therefore the ClpP-gene has not to be added in proteobacteria. 
<br><br>
Mammalian species also have a ClpXP but it is expressed in mitochondria. Thus, the natural protease will not interfere with the ProteoLux® protease. Besides, it has be shown that the human ClpXP does not recognize SsrA tag and lambda Otag (Functional Proteolytic Complexes of the Human Mitochondrial ATP-dependent Protease, hClpXP (2002) J. Biol. Chem. Vol. 277, No. 23, pp. 21095–21102).
<br><br>

The target gene needs to be fused with Pif6 and the specific degradation sequence. We provide two different variants to avoid problems with the accessibility or an increased activity of the target protein: The N-terminally fused λO-tag, resulting in the target protein construct [λO-protein-linker-PIF6], and the C-terminal degradation tag DAS, resulting in the target protein construct  [PIF6-linker-Protein-DAS].  
<br><br>

Most bacterial proteins tolerate C-terminal fusions and the C-termini of most proteins are solvent accessible. Consequently, the C-terminal fusion of Pif6 using the N-terminal degradation tag λO is more promising to succeed, as the specific degradation sequence consists of very few amino acids (3 for the DAS-tag and 11 for the λO–tag) which do not perturb protein activity in most of the cases. <br><br>

If possible, we recommend to test the activity of the target protein within the two constructs before the implementation of ProteoLux®, as the integration of the Pif6- and degradation tag-flanked target protein cassette presents a more time-consuming step for analytical purposes.  <br><br>

The analysis of a specific target protein requires its fusion to the adaptor Pif6 and the specific degradation tag λO/DAS. To simplify the addition of these two sequences to your target gene we provide a special plasmid containing standard restriction sides for the integration of the target gene. Thus the integration requires no more that the amplification of your target gene with the standard restriction sites and its ligation into the plasmid. 
<br><br>
To avoid interferences with the original protein it is necessary to silence the native gene. Therefore it is necessary to a gene-knock-out using the common gene targeting approaches based on homologous recombination. We recommend to integrate the Pif6- and degradation tag-flanked target protein cassette directly into the native gene or to substitute it with per gene-knock-in. 
<br><br>
This requires a further amplification step adding the specific “homology arms” which must match which must match the genomic DNA of the cell line being targeted, so in our case the native target gene sequence. These arms drive the homologous recombination event that results in insertion of the construct into the desired locus.
<br><br>
It is the client’s responsibility to design and engineer the targeting construct. See our tips on <a href="https://2010.igem.org/Team:ESBS-Strasbourg/proteolux/scientific/proteoluxbasic/constructdesign" style="text-decoration: none"> <font color="#FF9900">targeting construct design.</font></a>



</div>
<br>
</td>
</tr>



<tr>
<td width="750" height="10" bgcolor="#222222">
</td>
</tr>


<td width="750" bgcolor="#414141">
<div class="desc">
<div class="heading">
<a name="scheme"></a>
 SCHEME 
</div>
<br><br>
To avoid this time consuming step you can resort to the ProteoLux® Pro system which further has lots of potential for in vivo studies.  The details of this promising approach are explained in the following chapter. 






</div>
<br>
</td>
</tr>






</div>
<br>
</td>
</tr>





</table>
</body>
</html>