Difference between revisions of "Part:BBa K1930001:Design"
Barawaclawik (Talk | contribs) |
Barawaclawik (Talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 16: | Line 16: | ||
===Source=== | ===Source=== | ||
− | Created by our CryptoGErM software | + | <html> |
+ | <p>Created by our CryptoGErM software (see <a href="http://2016.igem.org/Team:Groningen/Encoding">Encoder</a>).</p> | ||
+ | </html> | ||
===References=== | ===References=== |
Latest revision as of 12:40, 19 October 2016
Encrypted message sequence
Assembly Compatibility:
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000COMPATIBLE 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 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).
For more information of how this part was designed see BBa_K1930001 on our wiki page.
Source
Created by our CryptoGErM software (see Encoder).