Difference between revisions of "Part:BBa K1930003"

 
 
Line 3: Line 3:
 
<partinfo>BBa_K1930003 short</partinfo>
 
<partinfo>BBa_K1930003 short</partinfo>
  
The iGEM team Groningen 2016 worked on bioencryption in order to safely store data in DNA. In our project we were mainly working with two sequences of DNA which were the encrypted message sequence and the encryption key sequence. The message sequence was created by our software. It is therefore artificial DNA. We ordered the encrypted message sequence as gBlock from IDT (Integrated DNA technologies). This part was created in the interest of having a genomic integration plasmid with our message sequence. We used an available BioBrick BBa_K823023 from igem Munich 2012. It is an integration plasmid for <em>Bacillus subtilis</em>, which can be used for cloning in <em>E. coli</em> as well. An RFP is inserted in BBa_K823023 for more efficient screening after transformation.
+
The iGEM team Groningen 2016 worked on bioencryption in order to safely store data in DNA. In our project we were mainly working with two sequences of DNA which were the encrypted message sequence and the encryption key sequence. The message sequence was created by our software. It is therefore artificial DNA. We ordered the encrypted message sequence as gBlock from IDT (Integrated DNA technologies). This part was created in the interest of having a genomic integration plasmid with our message sequence. We used an available BioBrick BBa_K823023 from igem Munich 2012. It is an integration plasmid for <em>Bacillus subtilis</em>, which can be used for cloning in <em>E. coli</em> as well.  
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Latest revision as of 10:55, 17 October 2016


Encrypted message sequence in integration plasmid (BBa_K823023)

The iGEM team Groningen 2016 worked on bioencryption in order to safely store data in DNA. In our project we were mainly working with two sequences of DNA which were the encrypted message sequence and the encryption key sequence. The message sequence was created by our software. It is therefore artificial DNA. We ordered the encrypted message sequence as gBlock from IDT (Integrated DNA technologies). This part was created in the interest of having a genomic integration plasmid with our message sequence. We used an available BioBrick BBa_K823023 from igem Munich 2012. It is an integration plasmid for Bacillus subtilis, which can be used for cloning in E. coli as well.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BamHI site found at 6601
    Illegal XhoI site found at 4109
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal NgoMIV site found at 1663
    Illegal NgoMIV site found at 4073
    Illegal NgoMIV site found at 5212
  • 1000
    INCOMPATIBLE WITH RFC[1000]
    Illegal BsaI.rc site found at 5036