Multiplex using Cas9 direct repeat

I saw this comment on Pubpeer and found it very interesting:

https://pubpeer.com/publications/1C98A3008E68E2C8661C21268E373F#1

"SpRNase III was not necessary for cleavage of the protospacer (Fig. 1D), and the 89-nt tracrRNA is processed in its absence (fig. S2C). Similarly, maturation of pre-crRNA does not require RNase III (Fig. 1D and fig. S4), suggesting that there may be endogenous mammalian RNases that assist in pre-crRNA maturation (24–26)"

Screen Shot 2019-01-03 at 4.38.32 PM.png

This paper was the very first paper demonstrating the effectiveness of Cas9 in mammalian cells. If this is true, wouldn't it be easier to clone the 2 guides in the direct repeat rather than to clone the 2 U6 system when multiplex is needed?


Login or Signup to leave a comment
Pink Pixiealmost 4 years ago

That's a really interesting idea, and it's further supported by the fact that in that paper (Cong and Ran et al 2013), crRNAs also look like they're more efficient than sgRNAs in some cases. However, in a paper later that year (Hsu and Scott et al 2013-- https://www.ncbi.nlm.nih.gov/pubmed/23873081), they showed that if you extend the tracrRNA element to nearly full-length in the sgRNA (+85 rather than +48), then sgRNAs are more efficient than crRNAs/tracrRNAs expressed separately.

Screenshot 2019-01-05 23.38.46.png

So you could definitely multiplex the crRNAs and have the tracrRNA expressed separately, but it might be less efficient than just using two sgRNAs driven by separate promoters.

Mint Lichalmost 4 years ago

This is a great point. Explained my confusion. In this paper (Hsu and Scott et al 2013), they also showed that longer sgRNA lead to greater transcription efficiency. Wonder why crRNA doesn't have similar KO efficiency ( crRNA~102nt, so transcription should not be a problem). Probably mammalian cells have less efficiency in processing the guide array.

Find your community. Ask questions. Science is better when we troubleshoot together.
Find your community. Ask questions. Science is better when we troubleshoot together.

Have a question?

Contact support@scifind.net or check out our support page.