Difference between revisions of "Part:BBa K1930000:Design"
Line 7: Line 7:
  
 
===Design Notes===
 
===Design Notes===
−
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 key sequence was created by our software. It is therefore artificial DNA. We ordered the encryption key sequence as gBlock from IDT (Integrated DNA technologies).  
+
<html>
 +
<p>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 key sequence was created by our software. It is therefore artificial DNA. We ordered the encryption key sequence as gBlock from IDT (Integrated DNA technologies).</p>
  
−
For more information of how this part was designed click on: [http://2016.igem.org/Team:Groningen/Experiments#Key-in-pSB1C3 ''BBa_K1930000 on wiki'']
+
<p>For more information of how this part was designed see <a href="http://2016.igem.org/Team:Groningen/Experiments#Key-in-pSB1C3">BBa_K1930000</a> on our wiki page.</p>
 +
</html>
  
 
===Source===
 
===Source===
−
Created by our CryptoGErM software. http://2016.igem.org/Team:Groningen/Encoding
+
<html>
 +
<p>Created by our CryptoGErM software. <a href="http://2016.igem.org/Team:Groningen/Encoding">Encoder</a></p>
 +
</html>
  
 
===References===
 
===References===

Revision as of 12:30, 19 October 2016


Encryption key sequence


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    COMPATIBLE WITH RFC[21]
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]


Design Notes

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 key sequence was created by our software. It is therefore artificial DNA. We ordered the encryption key sequence as gBlock from IDT (Integrated DNA technologies).

For more information of how this part was designed see BBa_K1930000 on our wiki page.

Source

Created by our CryptoGErM software. Encoder

References