Difference between revisions of "Part:BBa K2653001:Design"
(→Design Notes) |
|||
| Line 7: | Line 7: | ||
===Design Notes=== | ===Design Notes=== | ||
| − | The GFP-nano works as a core in our system to degrade the proof of concept target GFP as the tool to bind with it. In the design we link GFP-nano with hIgG1-Fc, so that it can work as the bridge between target GFP and Trim21, and finally help form a ternary complex of GFP, GFP-nano and Trim21. Only after this the degradation could successfully be processed. | + | The GFP-nano works as a core in our system to degrade the proof of concept target GFP as the tool to bind with it. In the design we link GFP-nano with hIgG1-Fc, so that it can work as the bridge between target GFP and Trim21, and finally help form a ternary complex of GFP, GFP-nano and Trim21. Only after this the degradation could successfully be processed. |
| − | + | ||
| − | + | ||
===Source=== | ===Source=== | ||
Latest revision as of 01:30, 8 October 2018
GFP-nano
Assembly Compatibility:
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21COMPATIBLE WITH RFC[21]
- 23COMPATIBLE WITH RFC[23]
- 25COMPATIBLE WITH RFC[25]
- 1000INCOMPATIBLE WITH RFC[1000]Illegal BsaI site found at 35
Design Notes
The GFP-nano works as a core in our system to degrade the proof of concept target GFP as the tool to bind with it. In the design we link GFP-nano with hIgG1-Fc, so that it can work as the bridge between target GFP and Trim21, and finally help form a ternary complex of GFP, GFP-nano and Trim21. Only after this the degradation could successfully be processed.
Source
The sequence of GFP-nano we use came from a patent.