Response to “Unexpected mutations after CRISPR-Cas9 editing in vivo”

Re:Response to “Unexpected mutations after CRISPR-Cas9 editi... by jacquesm on Thursday July 06, 2017 @06:05AM (#14709228)

> (You would need cryptographic signing, though, to see if the record mirrored by B has not been tampered with.)

Yes, hence the blockchain, which provides all that in a fairly convenient package.

You could even piggyback on any existing public blockchain, for a few fractions of a penny.

[ Parent | on HN ]

Re:Response to “Unexpected mutations after CRISPR-Cas9 editi... by Dylan16807 on Thursday July 06, 2017 @06:43AM (#14709376)

If you're making a notary system, the part you can get from a blockchain is a very minor percent of your code, and comes with a lot of complicated baggage. It's not convenient at all.

[ Parent | on HN ]

Re:Response to “Unexpected mutations after CRISPR-Cas9 editi... by mikeash on Thursday July 06, 2017 @08:28AM (#14709827)

Or you could publish an announcement in a newspaper or similar. This problem has been solved for a long time and doesn't really need fancy crypto.

[ Parent | on HN ]

Re:Response to “Unexpected mutations after CRISPR-Cas9 editi... by ClassyJacket on Thursday July 06, 2017 @07:22AM (#14709530)

You could also just distribute a hash of, or the entire original text of, the original text. No need for a blockchain and all that processing.

[ Parent | on HN ]