solana/src/lib.rs

#![cfg_attr(feature = "unstable", feature(test))]
pub mod log;
pub mod logger;
pub mod event;
pub mod genesis;
pub mod historian;
pub mod accountant;
pub mod accountant_skel;
pub mod accountant_stub;
extern crate bincode;
extern crate generic_array;
extern crate rayon;
extern crate ring;
extern crate serde;
#[macro_use]
extern crate serde_derive;
extern crate serde_json;
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;`
Give logger its own crate 2018-03-03 14:24:32 -07:00			`pub mod logger;`
Move Event into its own crate The log crate was starting to be the catch-all for all things related to entries, events, signatures, and hashes. This split shows us that: * Event depends only on signatures, not on hashes [directly] * All event testing was done via log testing (shame on me) * Accounting depends only on events 2018-03-02 08:43:54 -07:00			`pub mod event;`
Add command-line tool for generating a genesis block 2018-03-03 14:41:36 -07:00			`pub mod genesis;`
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 accountant 2018-02-23 14:08:19 -07:00			`pub mod accountant;`
Add network interface for accountant 2018-02-28 10:07:54 -07:00			`pub mod accountant_skel;`
Add accountant stub 2018-02-28 14:16:50 -07:00			`pub mod accountant_stub;`
Allow event log to hold events of any serializable (hashable) type 2018-02-26 16:42:31 -07:00			`extern crate bincode;`
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;`
Initialize the testnode from a log $ cargo run --bin silk-genesis-file-demo > demo-genesis.json $ cat demo-genesis.json \| cargo run --bin silk-genesis-block > demo-genesis.log $ cat demo-genesis.log \| cargo run --bin silk-testnode 2018-03-05 15:34:15 -07:00			`extern crate serde_json;`
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;`