Difference between revisions of "Part:BBa K1930000"

Revision as of 11:20, 19 October 2016

Encryption key sequence

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 on how our encrypted message and encryption key are working together see our [http://2016.igem.org/Team:Groningen/Proof Proof of concept].

Sequence and Features

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]

@@ Line 3: / Line 3: @@
 <partinfo>BBa_K1930000 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 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).
+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 on how our encrypted message and encryption key are working together see our  [http://2016.igem.org/Team:Groningen/Proof ''Proof of concept''].
 <!-- Add more about the biology of this part here