Difference between revisions of "Part:BBa K1930000"
Barawaclawik (Talk | contribs) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
<partinfo>BBa_K1930000 short</partinfo> | <partinfo>BBa_K1930000 short</partinfo> | ||
| − | key | + | <html> |
| + | <style> | ||
| + | .wrap{ | ||
| + | position: relative; | ||
| + | } | ||
| + | img{ | ||
| + | max-width: 99%; | ||
| + | } | ||
| + | .split{ | ||
| + | position: relative; | ||
| + | display: flex; | ||
| + | flex-flow: row nowrap; | ||
| + | justify-content: space-between; | ||
| + | } | ||
| + | .split > .left{ | ||
| + | order: 1; | ||
| + | margin-right: 3px; | ||
| + | } | ||
| + | .split > .right{ | ||
| + | order: 2; | ||
| + | margin-left: 3px; | ||
| + | } | ||
| + | .split > .flone{ | ||
| + | flex: 1 1; | ||
| + | position: relative; | ||
| + | } | ||
| + | .split > .fltwo{ | ||
| + | flex: 2 1; | ||
| + | position: relative; | ||
| + | } | ||
| + | </style> | ||
| + | |||
| + | <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). For more information on how our encrypted message and encryption key are working together see our <a href="http://2016.igem.org/Team:Groningen/Proof">Proof of concept</a>. | ||
| + | |||
| + | <figure> | ||
| + | <img src="https://static.igem.org/mediawiki/parts/9/9a/T-Groningen-pSB1C3-key.png"> | ||
| + | </figure> | ||
| + | </html> | ||
<!-- Add more about the biology of this part here | <!-- Add more about the biology of this part here | ||
Latest revision as of 12:27, 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 Proof of concept.
Sequence and Features
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]