Difference between revisions of "Team:UCL/Design"

 
Line 23: Line 23:
 
<script>
 
<script>
 
$(document).ready(function(){
 
$(document).ready(function(){
  $("a").on('click', function(event) {
+
    $("a").on('click', function(event) {
    if (this.hash !== "") {
+
        if (this.hash !== "") {
      event.preventDefault();
+
            event.preventDefault();
      var hash = this.hash;
+
            var hash = this.hash;
      $('html, body').animate({
+
            $('html, body').animate({
        scrollTop: $(hash).offset().top - 100
+
                scrollTop: $(hash).offset().top - 100
      }, 1500, function(){
+
            }, 1500, function(){
        window.location.hash = hash;
+
                window.location.hash = hash;
      });
+
            });
    }
+
        }
  });
+
    });
 
});
 
});
 
</script>
 
</script>
 
<script src="../resources/js/wow1.js"></script>
 
<script src="../resources/js/wow1.js"></script>
    <script>
+
<script>
        new WOW().init();
+
new WOW().init();
    </script>
+
</script>
  
 
<body>
 
<body>
<div class="background_img_igem">
+
    <div class="background_img_igem">
  <div class="navbarzindex">
+
        <div class="navbarzindex">
  <div class="navbar-brand_igem"><a href="https://2018.igem.org/Team:UCL">
+
            <div class="navbar-brand_igem"><a href="https://2018.igem.org/Team:UCL">
        <img class="img-logo_igem" src="https://static.igem.org/mediawiki/2018/7/73/T--UCL--Logo2.png" ></a>
+
                <img class="img-logo_igem" src="https://static.igem.org/mediawiki/2018/7/73/T--UCL--Logo2.png" ></a>
    </div>
+
            </div>
  
<div class="topnav_igem" id="myTopnav_igem">
+
            <div class="topnav_igem" id="myTopnav_igem">
<div class="floatright_igem">
+
                <div class="floatright_igem">
<a href="javascript:void(0);" style="font-size:21px;" class="icon_igem" onclick="myFunction()">&#9776;</a>
+
                    <a href="javascript:void(0);" style="font-size:21px;" class="icon_igem" onclick="myFunction()">&#9776;</a>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="People()">People
+
                        <button class="dropbtn_igem"onclick="People()">People
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownpeople_igem">
+
                        <div class="dropdown-content_igem"id="dropdownpeople_igem">
        <a href="https://2018.igem.org/Team:UCL/Team">Team</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Team">Team</a>
        <a href="https://2018.igem.org/Team:UCL/Attributions">Attributions</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Attributions">Attributions</a>
        <a href="https://2018.igem.org/Team:UCL/Attributions#Sponsors">Sponsors</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Attributions#Sponsors">Sponsors</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="Project()">Project
+
                        <button class="dropbtn_igem"onclick="Project()">Project
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownproject_igem">
+
                        <div class="dropdown-content_igem"id="dropdownproject_igem">
        <a href="https://2018.igem.org/Team:UCL/Description">Description</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Description">Description</a>
        <a href="https://2018.igem.org/Team:UCL/Results">Results</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Results">Results</a>
        <a href="https://2018.igem.org/Team:UCL/Demonstrate">Demonstrate</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Demonstrate">Demonstrate</a>
        <a href="https://2018.igem.org/Team:UCL/InterLab">InterLab</a>
+
                            <a href="https://2018.igem.org/Team:UCL/InterLab">InterLab</a>
        <a href="https://2018.igem.org/Team:UCL/Safety">Safety</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Safety">Safety</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="Parts()">Parts
+
                        <button class="dropbtn_igem"onclick="Parts()">Parts
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownparts_igem">
+
                        <div class="dropdown-content_igem"id="dropdownparts_igem">
        <a href="https://2018.igem.org/Team:UCL/Design">Part Design</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Design">Part Design</a>
        <a href="https://2018.igem.org/Team:UCL/Parts">Parts</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Parts">Parts</a>
        <a href="https://2018.igem.org/Team:UCL/Improve">Improved Part</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Improve">Improved Part</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="Modelling()">Modelling
+
                        <button class="dropbtn_igem"onclick="Modelling()">Modelling
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownmodelling_igem">
+
                        <div class="dropdown-content_igem"id="dropdownmodelling_igem">
        <a href="https://2018.igem.org/Team:UCL/Model">Modelling</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Model">Modelling</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="Humanpractices()">Human Practices
+
                        <button class="dropbtn_igem"onclick="Humanpractices()">Human Practices
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownhumanpractices_igem">
+
                        <div class="dropdown-content_igem"id="dropdownhumanpractices_igem">
        <a href="https://2018.igem.org/Team:UCL/Human_Practices">Human Practices</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Human_Practices">Human Practices</a>
        <a href="https://2018.igem.org/Team:UCL/Public_Engagement">Public Engagement</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Public_Engagement">Public Engagement</a>
        <a href="https://2018.igem.org/Team:UCL/Collaborations">Collaborations</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Collaborations">Collaborations</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
  <div class="dropdown_igem">
+
                    <div class="dropdown_igem">
    <button class="dropbtn_igem"onclick="Notebook()">Notebook
+
                        <button class="dropbtn_igem"onclick="Notebook()">Notebook
  
    </button>
+
                        </button>
    <div class="dropdown-content_igem"id="dropdownnotebook_igem">
+
                        <div class="dropdown-content_igem"id="dropdownnotebook_igem">
        <a href="https://2018.igem.org/Team:UCL/Notebook">Notebook</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Notebook">Notebook</a>
        <a href="https://2018.igem.org/Team:UCL/Achievements">Achievements</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Achievements">Achievements</a>
        <a href="https://2018.igem.org/Team:UCL/Experiments">Experiments</a>
+
                            <a href="https://2018.igem.org/Team:UCL/Experiments">Experiments</a>
    </div>
+
                        </div>
  </div>
+
                    </div>
 +
                </div>
 +
            </div>
 +
        </div>
  
 
+
        <script>
</div>
+
        $(window).on('scroll',function(){
</div>
+
            if($(window).scrollTop()){
</div>
+
                $('.navbarzindex').addClass('black');
 
+
            }
<script>
+
            else {
  $(window).on('scroll',function(){
+
                $('.navbarzindex').removeClass('black');
    if($(window).scrollTop()){
+
            }
      $('.navbarzindex').addClass('black');
+
        })
    }
+
    </script>
    else {
+
    <script>
      $('.navbarzindex').removeClass('black');
+
    function myFunction() {
    }
+
        var x = document.getElementById("myTopnav_igem");
  })
+
        if (x.className === "topnav_igem") {
</script>
+
            x.className += " responsive";
<script>
+
        } else {
function myFunction() {
+
            x.className = "topnav_igem";
    var x = document.getElementById("myTopnav_igem");
+
        }
    if (x.className === "topnav_igem") {
+
        x.className += " responsive";
+
    } else {
+
        x.className = "topnav_igem";
+
 
     }
 
     }
}
 
 
</script>
 
</script>
  
Line 179: Line 177:
 
<!--BODY==================================================================== -->
 
<!--BODY==================================================================== -->
 
<body>
 
<body>
 +
    <div class="container container_igem">
 
         <div class="container container_igem">
 
         <div class="container container_igem">
             <div class="container container_igem">
+
             <img class="wow fadeInUp subpage_img_igem" src="https://static.igem.org/mediawiki/2018/9/9e/T--UCL--part_design2.svg" data-wow-duration="2s" data-wow-delay="0.1s"/>
                <img class="wow fadeInUp subpage_img_igem" src="https://static.igem.org/mediawiki/2018/9/9e/T--UCL--part_design2.svg" data-wow-duration="2s" data-wow-delay="0.1s"/>
+
            <div class="h1_igem_subpage">Part Design</div>
                <div class="h1_igem_subpage">Part Design</div>
+
        </div>
 +
 
 +
        <div class="container container_igem">
 +
            <div id="sidenav" class="sidenav wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
 +
                <a href="#BB">BioBrick 2.0</a>
 +
                <a href="#IM">Intein Monomers</a>
 +
                <a href="#SC">Spidroin Constructs</a>
 +
                <a href="#IP">Intein Passenger</a>
 +
                <a href="#NIKR">NikR</a>
 +
                <a href="#ER">ER</a>
 
             </div>
 
             </div>
  
            <div class="container container_igem">
 
                <div id="sidenav" class="sidenav wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
 
                    <a href="#BB">BioBrick 2.0</a>
 
                    <a href="#IM">Intein Monomers</a>
 
                    <a href="#SC">Spidroin Constructs</a>
 
                    <a href="#IP">Intein Passenger</a>
 
                    <a href="#NIKR">NikR</a>
 
                    <a href="#ER">ER</a>
 
                  </div>
 
  
 +
            <section id="BB">
 +
                <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
 +
                    <div class="card-title text-center">
 +
                        <h4>BioBrick 2.0</h4>
 +
                    </div>
 +
                    <div class="card-body text-justify">
 +
                        <div class="container">
 +
                            <div class="row">
 +
                                <div class="col-sm-10 mmmm mrfont">
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">Overview</div>
 +
                                    </div>
 +
                                    <p class="card-text card-text_igem text-justify">
 +
                                        While developing our modular platform, we conceived a BioBrick-compatible standard with improved flexibility that enables the integration of conventional cloning methods into iGEM’s workflow. This construct, once inserted into a backbone, allows cloning through Golden Gate assembly and Gibson assembly. At the same time, our construct has a LacZ reporter which can be used to screen plates for successful colonies. We are proposing our BioBrick2.0 as a new standard, which could facilitate an improved cloning process for future iGEM teams.
 +
                                    </p>
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">Reporter</div>
 +
                                    </div>
 +
                                    <p class="card-text card-text_igem text-justify">
 +
                                        The lacZ reporter allows for blue-white screening. It can be displaced by compatible constructs through BioBrick assembly, Golden Gate assembly or Gibson assembly. Blue-white screening is based on the inability of commercial E. coli to metabolise galactose or structurally similar substrates like X-Gal because of a lacZ deletion mutation. Once lacZα is provided through a plasmid, X-Gal can be metabolised to an easily detectable blue compound. This screening can also be used for subsequent cloning where the displacement of lacZ results in white colonies.
 +
                                    </p>
  
                <section id="BB">
+
                                     <div class="card-title text-center">
                    <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
+
                                        <div class="h4_cards">Compatibility</div>
                        <div class="card-title text-center">
+
                                    </div>
                            <h4>BioBrick 2.0</h4>
+
                                    <p class="card-text card-text_igem text-justify">For Golden Gate assembly, BsaI cut sites and defined overhangs were added. The BsaI overhangs are based on Vladimir et al. 2018 [1]. CCAA was chosen for upstream and ACGG for downstream. For Gibson assembly, a defined area of homology was designed. BsaI can be used to open the plasmid, removing the reporter and exposing the Gibson overhangs. </p>
                        </div>
+
                        <div class="card-body text-justify">
+
                            <div class="container">
+
                                <div class="row">
+
                                     <div class="col-sm-10 mmmm mrfont">
+
                                      <br>
+
                                      <div class="card-title text-center">
+
                                          <div class="h4_cards">Overview</div>
+
                                      </div>
+
                                      <br>
+
                                      <p>While developing our modular platform, we conceived a BioBrick-compatible standard with improved flexibility that enables the integration of conventional cloning methods into iGEM’s workflow. This construct, once inserted into a backbone, allows cloning through Golden Gate assembly and Gibson assembly. At the same time, our construct has a LacZ reporter which can be used to screen plates for successful colonies. We are proposing our BioBrick2.0 as a new standard, which could facilitate an improved cloning process for future iGEM teams.</p>
+
                                      <br>
+
                                      <div class="card-title text-center">
+
                                            <div class="h4_cards">Reporter</div>
+
                                      </div>
+
                                        <p class="card-text card-text_igem text-justify">
+
                                          The lacZ reporter allows for blue-white screening. It can be displaced by compatible constructs through BioBrick assembly, Golden Gate assembly or Gibson assembly. Blue-white screening is based on the inability of commercial E. coli to metabolise galactose or structurally similar substrates like X-Gal because of a lacZ deletion mutation. Once lacZα is provided through a plasmid, X-Gal can be metabolised to an easily detectable blue compound. This screening can also be used for subsequent cloning where the displacement of lacZ results in white colonies.
+
                                        </p>
+
<br>
+
<div class="card-title text-center">
+
      <div class="h4_cards">Compatibility</div>
+
</div>
+
<p>For Golden Gate assembly, BsaI cut sites and defined overhangs were added. The BsaI overhangs are based on Vladimir et al. 2018 [1]. CCAA was chosen for upstream and ACGG for downstream. For Gibson assembly, a defined area of homology was designed. BsaI can be used to open the plasmid, removing the reporter and exposing the Gibson overhangs. </p>
+
<br><br>
+
<div class="card-title text-center">
+
      <div class="h4_cards">BioBrick2.0 standardisation</div>
+
</div>
+
<br>
+
<p>One of the oldest problems of biological research which persists nowadays is the lack of standardization in experimental design, which impacts reproducibility and therefore reliability of results. Especially with the advent of DNA cloning, sequencing and omics techniques, there has been a growing need for a connecting thread which would simplify the bundle of data generated by these new experimental techniques. Arkin and Endy from MIT were the first ones who tried to address the issue by publishing a standard registry of biological parts which didn’t have considerable success [1]. However, Tom Knight, one of their colleagues, who at the time was working in an artificial intelligence laboratory, proposed in 2003 a new standard called Biobrick [2]. BioBricks are DNA sequences which conform to a restriction enzyme assembly standard, building blocks which can be assembled in larger synthetic biological circuits from individual parts.</p>
+
<br>
+
<p>Over the years the Biobrick assembly has shown various flaws. First of all, it doesn’t allow for assembly of multiple parts in one reaction and it cannot be used for fusion proteins. Secondly, it produces a scar sequence which can be harmful for E. coli [3]. Even though, some of these issues have been addressed by improved methodologies such as the Silver or the 3A [4], [5], they are unnecessarily laborious as they require additional pre-screenings or, in the case of 3A, three different antibiotics.
+
</p>
+
<br>
+
<p>Our BioBrick2.0 construct integrates different cloning techniques, such as Gibson assembly and Golden Gate assembly, into the iGEM standard. When cloned into a backbone through BioBrick Assembly, it enables the other cloning methods to be used inside the BioBrick2.0 sequence. The Gibson overlapping regions allow for high-fidelity cloning of constructs up to thousands of kilobases, as shown previously [6]. The Golden Gate recognition sites allow for seamless cloning and, applying methods such as MoClo and Golden Braid, this procedure can be carried out with multiple fragments in one single reaction [7] [8].</p>
+
<br>
+
<p>The purpose of the BioBrick is not to create a new standard because, as it happened before in synthetic biology, an excess of attempts at creating new standards can become detrimental [9]. As a consequence, our brick is meant to be a platform to BioBrick standardize constructs cloned using different methods to accommodate different labs’ preferences and boost the iGEM workflow.
+
</p>
+
<br>
+
  
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">BioBrick2.0 standardisation</div>
 +
                                    </div>
  
 +
                                    <p class="card-text card-text_igem text-justify">One of the oldest problems of biological research which persists nowadays is the lack of standardization in experimental design, which impacts reproducibility and therefore reliability of results. Especially with the advent of DNA cloning, sequencing and omics techniques, there has been a growing need for a connecting thread which would simplify the bundle of data generated by these new experimental techniques. Arkin and Endy from MIT were the first ones who tried to address the issue by publishing a standard registry of biological parts which didn’t have considerable success [1]. However, Tom Knight, one of their colleagues, who at the time was working in an artificial intelligence laboratory, proposed in 2003 a new standard called Biobrick [2]. BioBricks are DNA sequences which conform to a restriction enzyme assembly standard, building blocks which can be assembled in larger synthetic biological circuits from individual parts.</p>
  
 +
                                    <p class="card-text card-text_igem text-justify">Over the years the Biobrick assembly has shown various flaws. First of all, it doesn’t allow for assembly of multiple parts in one reaction and it cannot be used for fusion proteins. Secondly, it produces a scar sequence which can be harmful for E. coli [3]. Even though, some of these issues have been addressed by improved methodologies such as the Silver or the 3A [4], [5], they are unnecessarily laborious as they require additional pre-screenings or, in the case of 3A, three different antibiotics.
 +
                                    </p>
  
 +
                                    <p class="card-text card-text_igem text-justify">Our BioBrick2.0 construct integrates different cloning techniques, such as Gibson assembly and Golden Gate assembly, into the iGEM standard. When cloned into a backbone through BioBrick Assembly, it enables the other cloning methods to be used inside the BioBrick2.0 sequence. The Gibson overlapping regions allow for high-fidelity cloning of constructs up to thousands of kilobases, as shown previously [6]. The Golden Gate recognition sites allow for seamless cloning and, applying methods such as MoClo and Golden Braid, this procedure can be carried out with multiple fragments in one single reaction [7] [8].</p>
  
 +
                                    <p class="card-text card-text_igem text-justify">The purpose of the BioBrick is not to create a new standard because, as it happened before in synthetic biology, an excess of attempts at creating new standards can become detrimental [9]. As a consequence, our brick is meant to be a platform to BioBrick standardize constructs cloned using different methods to accommodate different labs’ preferences and boost the iGEM workflow.
 +
                                    </p>
 +
                                </div>
 +
                            </div>
 +
                        </div>
 +
                    </div>
 +
                </div>
 +
            </section>
  
 +
            <section id="IM">
 +
                <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
 +
                    <div class="card-title text-center">
 +
                        <h4>Intein Monomers</h4>
 +
                    </div>
 +
                    <div class="card-body text-justify">
 +
                        <div class="container">
 +
                            <div class="row">
 +
                                <div class="col-sm-10 mmmm mrfont">
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">Intein Monomer 1 and Intein Monomer 2</div>
 +
                                    </div>
 +
                                    <p class="card-text card-text_igem text-justify">
  
  
 +
                                        Initially we planned to clone constructs that would allow us to produce long spider silk proteins which could then be functionalised with proteins of interest using SpyTag/SpyCatcher technology. We later realised that instead of restricting ourselves to just one protein - spider silk protein, we could develop a much broader platform  to polymerise any protein of interest. To achieve this we thought about using split inteins for  polymerisation. We designed two constructs ,Bba_K2842680 and Bba_K2842690 that could work together to polymerise proteins via intein trans-splicing. Each construct is made of an Intein C termini, a fluorescent reporter protein, a StrepTag and an intein N termini.
 +
                                        We introduced Type II restriction sites sites that could be used to introduce any protein of interest into the construct for polymerisation.
 +
                                    </p>
  
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">Design Details</div>
 +
                                    </div>
  
 +
                                    <p class="card-text card-text_igem text-justify"><b>Inteins</b>: Each construct contains orthogonal inteins on each side preventing self reaction and circularisation. The orthogonal inteins mean that polymerisation will only occur when both constructs are expressed together or when the two proteins are combined.</p>
  
 +
                                    <p class="card-text card-text_igem text-justify"><b>Reporters</b>: One construct contains GFP and the other mRFP1. This will enable easy identification of cross polymerisation by fluorescence measurements.</p>
  
 +
                                    <p class="card-text card-text_igem text-justify"><b>Modular design</b>: SapI sites were placed immediately upstream and downstream of the reporter proteins. The codons used were designed to be as innocuous as possible.</p>
  
 +
                                    <p class="card-text card-text_igem text-justify"><b>Other elements</b></p>
  
 +
                                    <p class="card-text card-text_igem text-justify">Promotor: A T7 promoter was used
 +
                                        RBS: We used a RBS based on predictions by sallis lab <sup>[1,2]</sup>
 +
                                        Regulatory elements: We introduced a lac operator to further control gene expression if the T7 promoter was too strong or detrimental to cell health.
 +
                                    </p>
  
 
 
                                    </div>
 
 
                                 </div>
 
                                 </div>
 
                             </div>
 
                             </div>
 
                         </div>
 
                         </div>
 
                     </div>
 
                     </div>
                 </section>
+
                 </div>
 +
            </section>
 +
            <section id="SC">
 +
                <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
 +
                    <div class="card-title text-center">
 +
                        <h4>Spidroin Constructs</h4>
 +
                    </div>
 +
                    <div class="card-body text-justify">
 +
                        <div class="container">
 +
                            <div class="row">
 +
                                <div class="col-sm-10 mmmm mrfont">
 +
                                    <div class="card-title text-center">
 +
                                        <div class="h4_cards">Spidroin Constructs</div>
 +
                                    </div>
 +
                                    <p class="card-text card-text_igem text-justify">
 +
                                        A spidroin is a protein belonging to the family of scleroproteins, which includes collagen and keratin. It is the main building block of spiders’ dragline silk; its tensile properties exceed steel and kevlar and, at the same time, it is more flexible than both of these material as it can be stretched up to 135% of its original length.
 +
                                    </p>
  
                <section id="IM">
+
                                    <p class="card-text card-text_igem text-justify">The amino acid composition is largely dominated by alanine, found in the crystalline regions of the protein, and glycine blocks found in the amorphous matrix. The alternation of the crystalline and amorphous regions, formed by helical structures and beta turns, is what gives spidersilk its incredible properties. However, the protein by itself is a monomer, therefore in order to form a strong fiber, it has to form an oligomer. The C-termini in solution associate by covalent bond and with a change in pH, which in vivo is carried by transport into a different gland The N-termini form hydrogen bonds and complete the oligomerization.
                    <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
+
                                    </p>
                        <div class="card-title text-center">
+
                            <h4>Intein Monomers</h4>
+
                        </div>
+
                        <div class="card-body text-justify">
+
                            <div class="container">
+
                                <div class="row">
+
                                    <div class="col-sm-10 mmmm mrfont">
+
                                      <div class="card-title text-center">
+
                                          <div class="h4_cards">Intein Monomer 1 and Intein Monomer 2</div>
+
                                      </div>
+
                                        <p class="card-text card-text_igem text-justify">
+
  
                                          <br><br>
+
                                    <p class="card-text card-text_igem text-justify">Our construct, which we split into two for simplicity of assembly, is composed by the spidroin core with four total repetitive regions, two in one construct and two in the other, and the C-and N-termini, distinguishing the two constructs. Moreover, to enable characterisation of the fiber, we flanked the C-terminus of the sequence with the N-terminus of the AceL-TerL intein which would splice out when associated with its compatible counterpart.
                                          Initially we planned to clone constructs that would allow us to produce long spider silk proteins which could then be functionalised with proteins of interest using SpyTag/SpyCatcher technology. We later realised that instead of restricting ourselves to just one protein - spider silk protein, we could develop a much broader platform  to polymerise any protein of interest. To achieve this we thought about using split inteins for polymerisation. We designed two constructs ,Bba_K2842680 and Bba_K2842690 that could work together to polymerise proteins via intein trans-splicing. Each construct is made of an Intein C termini, a fluorescent reporter protein, a StrepTag and an intein N termini.
+
                                    </p>
We introduced Type II restriction sites sites that could be used to introduce any protein of interest into the construct for polymerisation.
+
 
</p>
+
                                    <p class="card-text card-text_igem text-justify">The assembly of this construct can be carried out through Gibson assembly or Golden Gate into our BioBrick2.0 construct to standardise it for Bobrick assembly. Finally, the fibre can also be modified to test different properties through assembly of additional repetitive regions into the core of the sequence. This is made possible by our SapI overhangs which are compatible with the ones on our Spidroin Core construct. </p>
                                        <br><br>
+
                                        <div class="card-title text-center">
+
                                            <div class="h4_cards">Design Details</div>
+
                                        </div>
+
                                        <br>
+
                                        <p><b>Inteins</b>: Each construct contains orthogonal inteins on each side preventing self reaction and circularisation. The orthogonal inteins mean that polymerisation will only occur when both constructs are expressed together or when the two proteins are combined.</p>
+
                                        <br>
+
                                      <p><b>Reporters</b>: One construct contains GFP and the other mRFP1. This will enable easy identification of cross polymerisation by fluorescence measurements.</p>
+
                                      <br>
+
                                      <p><b>Modular design</b>: SapI sites were placed immediately upstream and downstream of the reporter proteins. The codons used were designed to be as innocuous as possible.</p>
+
                                      <br>
+
                                      <p><b>Other elements</b></p>
+
  
                                      <p>Promotor: A T7 promoter was used <br>
 
RBS: We used a RBS based on predictions by sallis lab [1,2] <br>
 
Regulatory elements: We introduced a lac operator to further control gene expression if the T7 promoter was too strong or detrimental to cell health.
 
</p>
 
<br><br>
 
                                    </div>
 
 
                                 </div>
 
                                 </div>
 
                             </div>
 
                             </div>
 
                         </div>
 
                         </div>
 
                     </div>
 
                     </div>
                 </section>
+
                 </div>
                <section id="SC">
+
            </section>
                    <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
+
            <section id="IP">
                        <div class="card-title text-center">
+
                <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
                            <h4>Spidroin Constructs</h4>
+
                    <div class="card-title text-center">
                        </div>
+
                        <h4>Intein Passenger</h4>
                        <div class="card-body text-justify">
+
                    </div>
                            <div class="container">
+
                    <div class="card-body text-justify">
                                <div class="row">
+
                        <div class="container">
                                    <div class="col-sm-10 mmmm mrfont">
+
                            <div class="row">
                                      <div class="card-title text-center">
+
                                <div class="col-sm-10 mmmm mrfont">
                                          <div class="h4_cards">Spidroin Constructs</div>
+
                                    <div class="card-title text-center">
                                      </div>
+
                                        <div class="h4_cards">Overview of Intein Passenger</div>
                                        <p class="card-text card-text_igem text-justify">
+
                                          A spidroin is a protein belonging to the family of scleroproteins, which includes collagen and keratin. It is the main building block of spiders’ dragline silk; its tensile properties exceed steel and kevlar and, at the same time, it is more flexible than both of these material as it can be stretched up to 135% of its original length.
+
                                        </p>
+
                                        <br>
+
                                        <p>The amino acid composition is largely dominated by alanine, found in the crystalline regions of the protein, and glycine blocks found in the amorphous matrix. The alternation of the crystalline and amorphous regions, formed by helical structures and beta turns, is what gives spidersilk its incredible properties. However, the protein by itself is a monomer, therefore in order to form a strong fiber, it has to form an oligomer. The C-termini in solution associate by covalent bond and with a change in pH, which in vivo is carried by transport into a different gland The N-termini form hydrogen bonds and complete the oligomerization.
+
</p>
+
<br>
+
<p>Our construct, which we split into two for simplicity of assembly, is composed by the spidroin core with four total repetitive regions, two in one construct and two in the other, and the C-and N-termini, distinguishing the two constructs. Moreover, to enable characterisation of the fiber, we flanked the C-terminus of the sequence with the N-terminus of the AceL-TerL intein which would splice out when associated with its compatible counterpart.
+
</p>
+
<br>
+
<p>The assembly of this construct can be carried out through Gibson assembly or Golden Gate into our BioBrick2.0 construct to standardise it for Bobrick assembly. Finally, the fibre can also be modified to test different properties through assembly of additional repetitive regions into the core of the sequence. This is made possible by our SapI overhangs which are compatible with the ones on our Spidroin Core construct.  </p>
+
<br><br>
+
 
                                     </div>
 
                                     </div>
                                </div>
+
                                     <p class="card-text card-text_igem text-justify">
                            </div>
+
                                        The intein passenger construct is the framework used to insert functional proteins into our highly modular platform. The design of the Biobrick allows it to flank any protein with inteins and, therefore, to functionalise biomaterials with a high degree of freedom. Design notes:
                        </div>
+
 
                    </div>
+
                                    </p>
                </section>
+
                <section id="IP">
+
                    <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s">
+
                        <div class="card-title text-center">
+
                            <h4>Intein Passenger</h4>
+
                        </div>
+
                        <div class="card-body text-justify">
+
                            <div class="container">
+
                                <div class="row">
+
                                     <div class="col-sm-10 mmmm mrfont">
+
                                      <div class="card-title text-center">
+
                                          <div class="h4_cards">Overview of Intein Passenger</div>
+
                                      </div>
+
                                        <p class="card-text card-text_igem text-justify">
+
                                          The intein passenger construct is the framework used to insert functional proteins into our highly modular platform. The design of the Biobrick allows it to flank any protein with inteins and, therefore, to functionalise biomaterials with a high degree of freedom. Design notes:
+
  
                                        </p>
+
                                    <div class="card-title text-center">
                                        <br>
+
                                          <div class="card-title text-center">
+
 
                                         <div class="h4_cards"><b>Intein</b></div>
 
                                         <div class="h4_cards"><b>Intein</b></div>
 
                                     </div>
 
                                     </div>
                                        <br>
+
 
                                        <p>The choice of intein is important because we need to leave as small a fragment as possible at the sister construct.  We picked the AceL-TerL intein (DOI 10.1002/anie.201307969) since its C-terminal section is 125 amino acids long and the N-terminal section only 11. </p>
+
                                    <p class="card-text card-text_igem text-justify">The choice of intein is important because we need to leave as small a fragment as possible at the sister construct.  We picked the AceL-TerL intein (DOI 10.1002/anie.201307969) since its C-terminal section is 125 amino acids long and the N-terminal section only 11. </p>
                                        <br>
+
 
                                        <br>
+
 
                                          <div class="card-title text-center">
+
                                    <div class="card-title text-center">
 
                                         <div class="h4_cards"><b>Reporter</b></div>
 
                                         <div class="h4_cards"><b>Reporter</b></div>
 
                                     </div>
 
                                     </div>
<br>
+
 
<p>mScarlet was chosen as it is one of the brightest RFPs available and it is a fast folder.</p>
+
                                    <p class="card-text card-text_igem text-justify">mScarlet was chosen as it is one of the brightest RFPs available and it is a fast folder.</p>
<br><br>  <div class="card-title text-center">
+
                                      <div class="card-title text-center">
<div class="h4_cards"><b>Golden Gate Set-Up</b></div>
+
                                        <div class="h4_cards"><b>Golden Gate Set-Up</b></div>
</div>
+
                                    </div>
<br>
+
 
<p>To make it compatible with the Golden Gate assembly approach incorporated in the BioBrick2.0, we decided to use SapI. The chosen design allows the lowest impact on the linker sequence. An advantage of using SapI is that any downstream design will be simpler by maintaining the overhang in frame. SapI sites were coded as GRA and SSS. It uses GGC (upstream) and GAG (downstream) overhangs.</p>
+
                                    <p class="card-text card-text_igem text-justify">To make it compatible with the Golden Gate assembly approach incorporated in the BioBrick2.0, we decided to use SapI. The chosen design allows the lowest impact on the linker sequence. An advantage of using SapI is that any downstream design will be simpler by maintaining the overhang in frame. SapI sites were coded as GRA and SSS. It uses GGC (upstream) and GAG (downstream) overhangs.</p>
<br><br>  <div class="card-title text-center">
+
                                      <div class="card-title text-center">
<div class="h4_cards"><b>Promoter
+
                                        <div class="h4_cards"><b>Promoter
</b></div>
+
                                        </b></div>
</div>
+
                                    </div>
<br>
+
 
<p>We needed high-level expression but too much expression would make  the spider silk insoluble, so we used a T7 promote with a middle of the road RBS. This is based on part BBa_K525998 (T7 promoter and RBS).</p>
+
                                    <p class="card-text card-text_igem text-justify">We needed high-level expression but too much expression would make  the spider silk insoluble, so we used a T7 promote with a middle of the road RBS. This is based on part BBa_K525998 (T7 promoter and RBS).</p>
<br><br>  <div class="card-title text-center">
+
                                      <div class="card-title text-center">
<div class="h4_cards"><b>Terminator</b></div>
+
                                        <div class="h4_cards"><b>Terminator</b></div>
</div>
+
                                    </div>
<br>
+
 
<p>The BBa_B1006 terminator was chosen because of its termination probability above 90%  and the many reported cases.
+
                                    <p class="card-text card-text_igem text-justify">The BBa_B1006 terminator was chosen because of its termination probability above 90%  and the many reported cases.
</p>
+
                                    </p>
<br><br>  <div class="card-title text-center">
+
                                      <div class="card-title text-center">
<div class="h4_cards"><b>Additional regulation
+
                                        <div class="h4_cards"><b>Additional regulation
</b></div>
+
                                        </b></div>
</div>
+
                                    </div>
<br>
+
 
<p>We picked a lac operator for improved silencing and reducing leaky expression situated downstream of the T7 promoter.</p>
+
                                    <p class="card-text card-text_igem text-justify">We picked a lac operator for improved silencing and reducing leaky expression situated downstream of the T7 promoter.</p>
<br><br>  <div class="card-title text-center">
+
                                      <div class="card-title text-center">
<div class="h4_cards"><b>Spacers
+
                                        <div class="h4_cards"><b>Spacers
</b></div></div>
+
                                        </b>
<br>
+
                                    </div>
<p>Spacers were added based on estimates of translation calculated on Salis Lab RBS calculator </p>
+
                                    </div>
<br><br>
+
 
 +
                                        <p class="card-text card-text_igem text-justify">Spacers were added based on estimates of translation calculated on Salis Lab RBS calculator.
 +
                                        </p>
 +
 
 
                                     </div>
 
                                     </div>
 
                                 </div>
 
                                 </div>
Line 410: Line 392:
 
                                             Nickel is a naturally occurring substance in ground water; in very low concentrations it is beneficial to the growth of plants. Factory waste and sewage disposal can result in leakage of this substance, which increases the concentration in water making it dangerous to humans. As a solution, we hereby propose a Nickel binding construct integrated with our project.
 
                                             Nickel is a naturally occurring substance in ground water; in very low concentrations it is beneficial to the growth of plants. Factory waste and sewage disposal can result in leakage of this substance, which increases the concentration in water making it dangerous to humans. As a solution, we hereby propose a Nickel binding construct integrated with our project.
 
                                         </p>
 
                                         </p>
                                        <br>
+
 
                                         <p>A hexahistidine tag is the most obvious Nickel binding protein available but it does not have a particularly high affinity. In solution, Ni-NTA has an affinity of 10μM for a single hexahistidine tag. A double histidine tag (6xHis + short spacer + 6xHis) showed an affinity nearly 10 times higher. However, an even higher binding affinity is achieved by the enzyme NikR which is a transcription activator that responds to Nickel. Additionally, E. coli has a NikR enzyme that  is very well characterised (https://www.uniprot.org/uniprot/P0A6Z6).</p>
+
                                         <p class="card-text card-text_igem text-justify">A hexahistidine tag is the most obvious Nickel binding protein available but it does not have a particularly high affinity. In solution, Ni-NTA has an affinity of 10μM for a single hexahistidine tag. A double histidine tag (6xHis + short spacer + 6xHis) showed an affinity nearly 10 times higher. However, an even higher binding affinity is achieved by the enzyme NikR which is a transcription activator that responds to Nickel. Additionally, E. coli has a NikR enzyme that  is very <a href="https://www.uniprot.org/uniprot/P0A6Z6">well characterised</a>.
                                         <br>
+
                                         </p>
                                         <p>NikR is a small 133 amino acid long molecule of known structure [1] with an affinity of 6.8 pM. It has two domains and the C-terminal domain alone, which is made of 86 residues from Gly48 to Asp133, is sufficient to bind nickel tightly at 2.2 pM [2].</p>
+
 
                                        <br>
+
                                         <p class="card-text card-text_igem text-justify">NikR is a small 133 amino acid long molecule of known structure [1] with an affinity of 6.8 pM. It has two domains and the C-terminal domain alone, which is made of 86 residues from Gly48 to Asp133, is sufficient to bind nickel tightly at 2.2 pM [2].
                                         <p>We inserted NikR in our BioBrick2.0 construct to standardise it. This can now be used to modularly characterise biomaterials through our innovative system. Materials functionalised with our NikR construct could be applied as filters to purify water from Nickel which is a very common pollutant. Together with our endocrine disruptor construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications that could affect millions of people.</p>
+
                                        </p>
                                        <br><br>
+
 
 +
                                         <p class="card-text card-text_igem text-justify">We inserted NikR in our BioBrick2.0 construct to standardise it. This can now be used to modularly characterise biomaterials through our innovative system. Materials functionalised with our NikR construct could be applied as filters to purify water from Nickel which is a very common pollutant. Together with our endocrine disruptor construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications that could affect millions of people.
 +
                                        </p>
 +
 
 
                                     </div>
 
                                     </div>
 
                                 </div>
 
                                 </div>
Line 433: Line 418:
 
                                     <div class="col-sm-10 mmmm mrfont">
 
                                     <div class="col-sm-10 mmmm mrfont">
 
                                         <p class="card-text card-text_igem text-justify">
 
                                         <p class="card-text card-text_igem text-justify">
                                          Endocrine disruptors are chemical substances that can interact with parts of the endocrine systems and, at high concentrations, compromise their functions. Dangerous quantities of these chemicals have been registered multiple times in sources of water that are accessible to the public like rivers and springs. The concentration of estradiol 2 (17 β-estradiol) in the river Ahr at Blankenheim is on the order of 4–12 ng/L and 122–631 ng/L in Rio de la Plata, Argentina[1]. A concentration of 15.1 ± 0.3 ng/L of E2 was measured in a sample obtained from a food production process, and 8.8 ± 0.7 ng/L in a sample from the Adriatic Sea[2].
+
                                            Endocrine disruptors are chemical substances that can interact with parts of the endocrine systems and, at high concentrations, compromise their functions. Dangerous quantities of these chemicals have been registered multiple times in sources of water that are accessible to the public like rivers and springs. The concentration of estradiol 2 (17 β-estradiol) in the river Ahr at Blankenheim is on the order of 4–12 ng/L and 122–631 ng/L in Rio de la Plata, Argentina[1]. A concentration of 15.1 ± 0.3 ng/L of E2 was measured in a sample obtained from a food production process, and 8.8 ± 0.7 ng/L in a sample from the Adriatic Sea[2].
 
                                         </p>
 
                                         </p>
                                        <br>
+
 
                                         <p>In order to deal with this health and environmental risk, we developed an endocrine disruptor binder that works with our intein passenger system. The construct is based on the M421F mutated version of the estrogen receptor protein which was shown have higher binding affinities and stability than the normal enzyme[3]. These characteristics make it a well performing potential bionsensor as suggested by Ferrero et al. </p>
+
                                         <p class="card-text card-text_igem text-justify">In order to deal with this health and environmental risk, we developed an endocrine disruptor binder that works with our intein passenger system. The construct is based on the M421F mutated version of the estrogen receptor protein which was shown have higher binding affinities and stability than the normal enzyme[3]. These characteristics make it a well performing potential bionsensor as suggested by Ferrero et al. </p>
                                        <br>
+
 
                                         <p>We inserted ER in our Final Brick to standardise it and this can now be used to modularly characterise biomaterials through our innovative system. Materials characterised with our ER construct could be applied as filters to purify water from dangerous quantities of estrogen which is a very common pollutant. Together with our nickel binding construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications which could affect millions of people.
+
                                         <p class="card-text card-text_igem text-justify">We inserted ER in our Final Brick to standardise it and this can now be used to modularly characterise biomaterials through our innovative system. Materials characterised with our ER construct could be applied as filters to purify water from dangerous quantities of estrogen which is a very common pollutant. Together with our nickel binding construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications which could affect millions of people.
</p>
+
                                        </p>
<br><br>
+
 
 
                                     </div>
 
                                     </div>
 
                                 </div>
 
                                 </div>
Line 449: Line 434:
 
             </div>
 
             </div>
 
         </div>
 
         </div>
        </div>
 
 
 
     </div>
 
     </div>
    <!--FOOTER================================================================== -->
 
  
    <div class="footer">
+
</div>
        <div class="container">
+
<!--FOOTER================================================================== -->
            <div class="row">
+
                <div class="col-lg-4">
+
                    <center>
+
                        <div class="h2_footer_igem">Our Location</div>
+
                        University College London<br />
+
      Gower St, Bloomsbury<br />London <br />WC1E 6BT
+
                        <span></span>
+
  
                    </center>
+
<div class="footer">
                </div>
+
    <div class="container">
                <div class="col-lg-4">
+
        <div class="row">
                    <center>
+
            <div class="col-lg-4">
                        <div class="h2_footer_igem">Contact Us</div>
+
                <center>
                      ucl.igem@ucl.ac.uk
+
                    <div class="h2_footer_igem">Our Location</div>
                        <a class="footer_img_igem" href="https://www.ucl.ac.uk/">
+
                    University College London<br />
                            <img src="https://static.igem.org/mediawiki/2018/f/ff/T--UCL--UCLLogo.jpeg" height="100rem;" />
+
                    Gower St, Bloomsbury<br />London <br />WC1E 6BT
                        </a>
+
                    <span></span>
                    </center>
+
                </div>
+
                <div class="col-lg-4">
+
                    <center>
+
                        <div class="h2_footer_igem">Follow Us</div>
+
                        <a href="https://www.facebook.com/UCLiGEM/"class="contacticons">
+
                            <img src="https://static.igem.org/mediawiki/2018/c/c4/T--UCL--FBLogo.svg" style="padding-top:1em;" height="62rem;"/>
+
                        </a>
+
                        <a href="https://twitter.com/ucligem?lang=en"class="contacticons">
+
                            <img src="https://static.igem.org/mediawiki/2018/e/ed/T--UCL--TwitterLogo.svg" style="padding-top:1em;" height="62rem;"/>
+
                        </a>
+
                        <a href="https://www.instagram.com/ucl.igem/"class="contacticons">
+
                            <img src="https://static.igem.org/mediawiki/2018/3/31/T--UCL--InstaLogo.png" style="padding-top:1em;" height="62rem;"/>
+
  
                        </a>
+
                </center>
                     </center>
+
            </div>
                 </div>
+
            <div class="col-lg-4">
 +
                <center>
 +
                    <div class="h2_footer_igem">Contact Us</div>
 +
                    ucl.igem@ucl.ac.uk
 +
                    <a class="footer_img_igem" href="https://www.ucl.ac.uk/">
 +
                        <img src="https://static.igem.org/mediawiki/2018/f/ff/T--UCL--UCLLogo.jpeg" height="100rem;" />
 +
                     </a>
 +
                </center>
 +
            </div>
 +
            <div class="col-lg-4">
 +
                 <center>
 +
                    <div class="h2_footer_igem">Follow Us</div>
 +
                    <a href="https://www.facebook.com/UCLiGEM/"class="contacticons">
 +
                        <img src="https://static.igem.org/mediawiki/2018/c/c4/T--UCL--FBLogo.svg" style="padding-top:1em;" height="62rem;"/>
 +
                    </a>
 +
                    <a href="https://twitter.com/ucligem?lang=en"class="contacticons">
 +
                        <img src="https://static.igem.org/mediawiki/2018/e/ed/T--UCL--TwitterLogo.svg" style="padding-top:1em;" height="62rem;"/>
 +
                    </a>
 +
                    <a href="https://www.instagram.com/ucl.igem/"class="contacticons">
 +
                        <img src="https://static.igem.org/mediawiki/2018/3/31/T--UCL--InstaLogo.png" style="padding-top:1em;" height="62rem;"/>
 +
 
 +
                    </a>
 +
                </center>
 
             </div>
 
             </div>
 
         </div>
 
         </div>
 
     </div>
 
     </div>
 +
</div>
 
</body>
 
</body>
 
</html>
 
</html>

Latest revision as of 13:26, 8 December 2018


UCL SETA - Part Design

Part Design

BioBrick 2.0

Overview

While developing our modular platform, we conceived a BioBrick-compatible standard with improved flexibility that enables the integration of conventional cloning methods into iGEM’s workflow. This construct, once inserted into a backbone, allows cloning through Golden Gate assembly and Gibson assembly. At the same time, our construct has a LacZ reporter which can be used to screen plates for successful colonies. We are proposing our BioBrick2.0 as a new standard, which could facilitate an improved cloning process for future iGEM teams.

Reporter

The lacZ reporter allows for blue-white screening. It can be displaced by compatible constructs through BioBrick assembly, Golden Gate assembly or Gibson assembly. Blue-white screening is based on the inability of commercial E. coli to metabolise galactose or structurally similar substrates like X-Gal because of a lacZ deletion mutation. Once lacZα is provided through a plasmid, X-Gal can be metabolised to an easily detectable blue compound. This screening can also be used for subsequent cloning where the displacement of lacZ results in white colonies.

Compatibility

For Golden Gate assembly, BsaI cut sites and defined overhangs were added. The BsaI overhangs are based on Vladimir et al. 2018 [1]. CCAA was chosen for upstream and ACGG for downstream. For Gibson assembly, a defined area of homology was designed. BsaI can be used to open the plasmid, removing the reporter and exposing the Gibson overhangs.

BioBrick2.0 standardisation

One of the oldest problems of biological research which persists nowadays is the lack of standardization in experimental design, which impacts reproducibility and therefore reliability of results. Especially with the advent of DNA cloning, sequencing and omics techniques, there has been a growing need for a connecting thread which would simplify the bundle of data generated by these new experimental techniques. Arkin and Endy from MIT were the first ones who tried to address the issue by publishing a standard registry of biological parts which didn’t have considerable success [1]. However, Tom Knight, one of their colleagues, who at the time was working in an artificial intelligence laboratory, proposed in 2003 a new standard called Biobrick [2]. BioBricks are DNA sequences which conform to a restriction enzyme assembly standard, building blocks which can be assembled in larger synthetic biological circuits from individual parts.

Over the years the Biobrick assembly has shown various flaws. First of all, it doesn’t allow for assembly of multiple parts in one reaction and it cannot be used for fusion proteins. Secondly, it produces a scar sequence which can be harmful for E. coli [3]. Even though, some of these issues have been addressed by improved methodologies such as the Silver or the 3A [4], [5], they are unnecessarily laborious as they require additional pre-screenings or, in the case of 3A, three different antibiotics.

Our BioBrick2.0 construct integrates different cloning techniques, such as Gibson assembly and Golden Gate assembly, into the iGEM standard. When cloned into a backbone through BioBrick Assembly, it enables the other cloning methods to be used inside the BioBrick2.0 sequence. The Gibson overlapping regions allow for high-fidelity cloning of constructs up to thousands of kilobases, as shown previously [6]. The Golden Gate recognition sites allow for seamless cloning and, applying methods such as MoClo and Golden Braid, this procedure can be carried out with multiple fragments in one single reaction [7] [8].

The purpose of the BioBrick is not to create a new standard because, as it happened before in synthetic biology, an excess of attempts at creating new standards can become detrimental [9]. As a consequence, our brick is meant to be a platform to BioBrick standardize constructs cloned using different methods to accommodate different labs’ preferences and boost the iGEM workflow.

Intein Monomers

Intein Monomer 1 and Intein Monomer 2

Initially we planned to clone constructs that would allow us to produce long spider silk proteins which could then be functionalised with proteins of interest using SpyTag/SpyCatcher technology. We later realised that instead of restricting ourselves to just one protein - spider silk protein, we could develop a much broader platform to polymerise any protein of interest. To achieve this we thought about using split inteins for polymerisation. We designed two constructs ,Bba_K2842680 and Bba_K2842690 that could work together to polymerise proteins via intein trans-splicing. Each construct is made of an Intein C termini, a fluorescent reporter protein, a StrepTag and an intein N termini. We introduced Type II restriction sites sites that could be used to introduce any protein of interest into the construct for polymerisation.

Design Details

Inteins: Each construct contains orthogonal inteins on each side preventing self reaction and circularisation. The orthogonal inteins mean that polymerisation will only occur when both constructs are expressed together or when the two proteins are combined.

Reporters: One construct contains GFP and the other mRFP1. This will enable easy identification of cross polymerisation by fluorescence measurements.

Modular design: SapI sites were placed immediately upstream and downstream of the reporter proteins. The codons used were designed to be as innocuous as possible.

Other elements

Promotor: A T7 promoter was used RBS: We used a RBS based on predictions by sallis lab [1,2] Regulatory elements: We introduced a lac operator to further control gene expression if the T7 promoter was too strong or detrimental to cell health.

Spidroin Constructs

Spidroin Constructs

A spidroin is a protein belonging to the family of scleroproteins, which includes collagen and keratin. It is the main building block of spiders’ dragline silk; its tensile properties exceed steel and kevlar and, at the same time, it is more flexible than both of these material as it can be stretched up to 135% of its original length.

The amino acid composition is largely dominated by alanine, found in the crystalline regions of the protein, and glycine blocks found in the amorphous matrix. The alternation of the crystalline and amorphous regions, formed by helical structures and beta turns, is what gives spidersilk its incredible properties. However, the protein by itself is a monomer, therefore in order to form a strong fiber, it has to form an oligomer. The C-termini in solution associate by covalent bond and with a change in pH, which in vivo is carried by transport into a different gland The N-termini form hydrogen bonds and complete the oligomerization.

Our construct, which we split into two for simplicity of assembly, is composed by the spidroin core with four total repetitive regions, two in one construct and two in the other, and the C-and N-termini, distinguishing the two constructs. Moreover, to enable characterisation of the fiber, we flanked the C-terminus of the sequence with the N-terminus of the AceL-TerL intein which would splice out when associated with its compatible counterpart.

The assembly of this construct can be carried out through Gibson assembly or Golden Gate into our BioBrick2.0 construct to standardise it for Bobrick assembly. Finally, the fibre can also be modified to test different properties through assembly of additional repetitive regions into the core of the sequence. This is made possible by our SapI overhangs which are compatible with the ones on our Spidroin Core construct.

Intein Passenger

Overview of Intein Passenger

The intein passenger construct is the framework used to insert functional proteins into our highly modular platform. The design of the Biobrick allows it to flank any protein with inteins and, therefore, to functionalise biomaterials with a high degree of freedom. Design notes:

Intein

The choice of intein is important because we need to leave as small a fragment as possible at the sister construct. We picked the AceL-TerL intein (DOI 10.1002/anie.201307969) since its C-terminal section is 125 amino acids long and the N-terminal section only 11.

Reporter

mScarlet was chosen as it is one of the brightest RFPs available and it is a fast folder.

Golden Gate Set-Up

To make it compatible with the Golden Gate assembly approach incorporated in the BioBrick2.0, we decided to use SapI. The chosen design allows the lowest impact on the linker sequence. An advantage of using SapI is that any downstream design will be simpler by maintaining the overhang in frame. SapI sites were coded as GRA and SSS. It uses GGC (upstream) and GAG (downstream) overhangs.

Promoter

We needed high-level expression but too much expression would make the spider silk insoluble, so we used a T7 promote with a middle of the road RBS. This is based on part BBa_K525998 (T7 promoter and RBS).

Terminator

The BBa_B1006 terminator was chosen because of its termination probability above 90% and the many reported cases.

Additional regulation

We picked a lac operator for improved silencing and reducing leaky expression situated downstream of the T7 promoter.

Spacers

Spacers were added based on estimates of translation calculated on Salis Lab RBS calculator.

NikR

Nickel is a naturally occurring substance in ground water; in very low concentrations it is beneficial to the growth of plants. Factory waste and sewage disposal can result in leakage of this substance, which increases the concentration in water making it dangerous to humans. As a solution, we hereby propose a Nickel binding construct integrated with our project.

A hexahistidine tag is the most obvious Nickel binding protein available but it does not have a particularly high affinity. In solution, Ni-NTA has an affinity of 10μM for a single hexahistidine tag. A double histidine tag (6xHis + short spacer + 6xHis) showed an affinity nearly 10 times higher. However, an even higher binding affinity is achieved by the enzyme NikR which is a transcription activator that responds to Nickel. Additionally, E. coli has a NikR enzyme that is very well characterised.

NikR is a small 133 amino acid long molecule of known structure [1] with an affinity of 6.8 pM. It has two domains and the C-terminal domain alone, which is made of 86 residues from Gly48 to Asp133, is sufficient to bind nickel tightly at 2.2 pM [2].

We inserted NikR in our BioBrick2.0 construct to standardise it. This can now be used to modularly characterise biomaterials through our innovative system. Materials functionalised with our NikR construct could be applied as filters to purify water from Nickel which is a very common pollutant. Together with our endocrine disruptor construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications that could affect millions of people.

Estrogen Receptor

Endocrine disruptors are chemical substances that can interact with parts of the endocrine systems and, at high concentrations, compromise their functions. Dangerous quantities of these chemicals have been registered multiple times in sources of water that are accessible to the public like rivers and springs. The concentration of estradiol 2 (17 β-estradiol) in the river Ahr at Blankenheim is on the order of 4–12 ng/L and 122–631 ng/L in Rio de la Plata, Argentina[1]. A concentration of 15.1 ± 0.3 ng/L of E2 was measured in a sample obtained from a food production process, and 8.8 ± 0.7 ng/L in a sample from the Adriatic Sea[2].

In order to deal with this health and environmental risk, we developed an endocrine disruptor binder that works with our intein passenger system. The construct is based on the M421F mutated version of the estrogen receptor protein which was shown have higher binding affinities and stability than the normal enzyme[3]. These characteristics make it a well performing potential bionsensor as suggested by Ferrero et al.

We inserted ER in our Final Brick to standardise it and this can now be used to modularly characterise biomaterials through our innovative system. Materials characterised with our ER construct could be applied as filters to purify water from dangerous quantities of estrogen which is a very common pollutant. Together with our nickel binding construct, these are an example of how our plug and play split inteins system is not only a method that could greatly help in research, but it is also aimed at real world applications which could affect millions of people.