Team:Buenos Aires/Results/Bb2


Revision as of 02:51, 27 September 2012 by Abush84 (Talk | contribs)


Why this biobrick?

We were having some custom related issues with the synthesized dna we ordered (see aa-rich export devices), so we started designing a biobrick that could be used for the same purpose, but that uses just parts included in the 2012 kit. Yes, you are correct: a PlanB!

Although we did not work in the lab with this planB biobrick - because fortunately the synthesized dna made it through customs (although very late) - we are including it in the registry and the wiki for documentary purposes only. Just follow this link BBa_K792014 to access its entry in the registry.

Bacteria Exportable His-rich peptide Generator

As mentioned before, for this biobrick we had to use solely parts that came in the iGEM Kit 2012 Spring distribution, and that could work for the same purposes that our main biobrick, which is mainly the export of aminoacids.

We designed a plausible construct that could work for the export of His using 5 parts of the registry, but we didnt find enough parts in order to design a simmilar one for the export of Trp.

Furthermore, the binding and preparation of this device is much more complex and has many more steps than what our main biobrick would require to work. Therefore, we conclude that our main biobrick is an important contribution to the registry part, given that it allows the export of aminoacids His and Trp to be enhanced with the use of only one part, without the need of the many steps that we describe in this section and consequently reducing the risk of failure and errors.

Device final structure

Our device is composed by:

  • Promoter (BBa_J04500)
  • Ribosome binding site (BBa_B0034)
  • Peptide signal or secretion tag so that the aminoacid is exported out of the cell (BBa_K125310)
  • Payload, a histidine tag repeated several times in order to have a long peptide enriched in this aa (BBa_K133035)
  • Terminator (BBa_B0024)
Structure of the device

This construct should be able to export Histidine, for sure in Cyanobacterium and to be tested in E.Coli and S. cereviciae. More details about the design process (and choices made) can be found in the following sections.

Design process


We found many usable parts to use as promoters. We found Promoters + RBS ideal for our purposes, in order to economize ligation steps. We considered using two parts:

  1. Promoter + RBS (BBa_K206015), a strongest constitutive promoter in J23100 family (J23100) + mid-strength RBS from the community collection (B0030, 0.6. It looks like a reliable sequence but it has not been tested according to the registry.
  2. Inducible Promoter (IPTG) + RBS (Strong) (BBa_J04500). This part has been tested and according to the registry it works well.

We finally decided to use the second opton (BBa_J04500) in order to make our system plausible of regulation through IPTG. This kind of regulation could also have been implemented in our main biobricks, for the same purposes or making the system more flexible.

Signal Peptide

Unfortunately, we found very few signal peptide biobrick options, solely two and tested in Cyanobacterium. Our two options were:

  1. pilA1 signal sequence from cyanobacterium Synechocystis; secretes protein: BBa_K125300
  2. slr2016 signal sequence from cyanobacterium Synechocystis; secretes protein: BBa_K125310

These parts are only partically confirmed and optimized for working in Cyanobacterium, not E. coli or Yeast. We could use any of them in order to test them but not having any E.coli or yeast optimized signal peptide available at the registry is a critical obstacle in the project.

We would use the second one: BBa_K125310.


The only option available in iGEM Kit Spring distribution 2012 was Methionine + His Affinity Tag x 6: BBa_K133035. This part is only partially confirmed. We would put this part 3 times in a row in order to have a larger peptide - so it would take 3 ligation steps to obtain a larger peptide enriched Histidine, whereas in our main biobrick 1 and 3, it already comes in the same construct.


There are several options for terminators, but we would use a double terminator in order to be sure that it works. We choose the double terminator BBa_B0024. This sequence has a double terminator in several of reading frames, which could be very useful.

Different Reading Frames of BBa_B0024. Frames 1 and 3 are useful as double terminators.

Assembly method

All the chosen parts are compatible with RFC 21 Standard, which is an in frame assembly method and would be our choice for assembling these parts.

Picture: Final sequence with prefix, suffix and scars assembled with RFC 21 Standard method.