solana/src/lib.rs

#![cfg_attr(feature = "unstable", feature(test))]
pub mod log;
pub mod historian;
extern crate generic_array;
extern crate rayon;
extern crate ring;
extern crate serde;
#[macro_use]
extern crate serde_derive;
extern crate sha2;
extern crate untrusted;
Parallelize verification 2018-02-14 14:19:30 -07:00			`#![cfg_attr(feature = "unstable", feature(test))]`
Rename event crate to log 2018-02-18 09:59:15 -07:00			`pub mod log;`
Add historian A microservice that continuously generates hashes, only stopping to tag messages with the latest hash. Fixes #8 2018-02-17 20:51:41 -07:00			`pub mod historian;`
Add serialization/deseriation support to event log See bincode and serde_json for usage: https://github.com/TyOverby/bincode Fixes #1 2018-02-20 16:26:11 -07:00			`extern crate generic_array;`
Parallelize verification 2018-02-14 14:19:30 -07:00			`extern crate rayon;`
Extend the event log with a Claim event to claim possession Unlike a Discovery event, a Claim event associates a public key with a hash. It's intended to to be used to claim ownership of some hashable data. For example, a graphic designer could claim copyright by hashing some image they created, signing it with their private key, and publishing the hash-signature pair via the historian. If someone else tries to claim it as their own, the designer can point to the historian's log as cryptographically secure evidence that the designer's copy existed before anyone else's. Note there's nothing here that verifies the first claim is the actual content owner, only that the first claim almost certainly happened before a second. 2018-02-24 06:53:36 -07:00			`extern crate ring;`
Add serialization/deseriation support to event log See bincode and serde_json for usage: https://github.com/TyOverby/bincode Fixes #1 2018-02-20 16:26:11 -07:00			`extern crate serde;`
			`#[macro_use]`
			`extern crate serde_derive;`
Use sha256 hashes instead of Rust's builtin hasher. Causes a 20x performance degradation. Enabling asm did not speed things up. 2018-02-19 16:17:13 -07:00			`extern crate sha2;`
Extend the event log with a Claim event to claim possession Unlike a Discovery event, a Claim event associates a public key with a hash. It's intended to to be used to claim ownership of some hashable data. For example, a graphic designer could claim copyright by hashing some image they created, signing it with their private key, and publishing the hash-signature pair via the historian. If someone else tries to claim it as their own, the designer can point to the historian's log as cryptographically secure evidence that the designer's copy existed before anyone else's. Note there's nothing here that verifies the first claim is the actual content owner, only that the first claim almost certainly happened before a second. 2018-02-24 06:53:36 -07:00			`extern crate untrusted;`