solana/src/lib.rs

#![cfg_attr(feature = "unstable", feature(test))]
pub mod accountant;
pub mod accounting_stage;
pub mod crdt;
pub mod ecdsa;
pub mod entry;
#[cfg(feature = "erasure")]
pub mod erasure;
pub mod event;
pub mod hash;
pub mod historian;
pub mod ledger;
pub mod logger;
pub mod mint;
pub mod packet;
pub mod plan;
pub mod recorder;
pub mod result;
pub mod signature;
pub mod streamer;
pub mod thin_client;
pub mod thin_client_service;
pub mod timing;
pub mod tpu;
pub mod transaction;
extern crate bincode;
extern crate byteorder;
extern crate chrono;
extern crate generic_array;
extern crate libc;
#[macro_use]
extern crate log;
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;

extern crate futures;

#[cfg(test)]
#[macro_use]
extern crate matches;

extern crate rand;
Parallelize verification 2018-02-14 14:19:30 -07:00			`#![cfg_attr(feature = "unstable", feature(test))]`
Nightly rustfmt Format code with the nightly version of rustfmt, which sorts imports. 2018-03-26 22:03:26 -06:00			`pub mod accountant;`
Extract accounting stage code from tpu 2018-05-09 09:20:56 -06:00			`pub mod accounting_stage;`
initial crdt implementation 2018-04-21 11:02:49 -07:00			`pub mod crdt;`
Fix the nightly build Nightly uses a different (but backward compatible) version of rustfmt. 2018-04-05 22:39:07 -06:00			`pub mod ecdsa;`
Move entry into its own module Hmm, Logger doesn't depend on log. 2018-03-06 17:31:17 -07:00			`pub mod entry;`
improve the error messages 2018-04-21 21:12:57 +08:00			`#[cfg(feature = "erasure")]`
			`pub mod erasure;`
Nightly rustfmt Format code with the nightly version of rustfmt, which sorts imports. 2018-03-26 22:03:26 -06:00			`pub mod event;`
			`pub mod hash;`
Change for cuda verify integration 2018-03-26 21:07:11 -07:00			`pub mod historian;`
log -> ledger Free up namespace for traditional runtime logs. 2018-03-19 10:09:17 -06:00			`pub mod ledger;`
Add broadcast impl 2018-04-28 00:31:20 -07:00			`pub mod logger;`
Rename Genesis to Mint Genesis is a story of creation. We should only use that term to for the event log that bootstraps the system. 2018-03-07 17:08:12 -07:00			`pub mod mint;`
Change for cuda verify integration 2018-03-26 21:07:11 -07:00			`pub mod packet;`
Nightly rustfmt Format code with the nightly version of rustfmt, which sorts imports. 2018-03-26 22:03:26 -06:00			`pub mod plan;`
logger -> recorder Free up namespace for a traditional runtime logger. 2018-03-19 10:16:16 -06:00			`pub mod recorder;`
Fast UdpSocket reader * message needs to fit into 256 bytes * allocator to keep track of blocks of messages * udp socket receiver server that fills up the block as fast as possible * udp socket sender server that sends out the block as fast as possible 2018-03-07 13:47:13 -08:00			`pub mod result;`
Nightly rustfmt Format code with the nightly version of rustfmt, which sorts imports. 2018-03-26 22:03:26 -06:00			`pub mod signature;`
			`pub mod streamer;`
AccountantSkel -> Tpu The terms Stub and Skel come from OMG IDL and only made sense while the Stub was acting as an RPC client for the the Accountant object. Nowadays, the Stub interface looks nothing like the Accountant and meanwhile we've recognized the multithreaded implementation is more reminiscent of a pipelined CPU. Thus, we finally bite the bullet and rename our modules. AccountantSkel -> Tpu AccountantStub -> ThinClient Up next will be moving much of the TPU code into separate modules, each representing a stage of the pipeline. The interface of each will follow the precedent set by the Historian object. 2018-05-08 17:32:50 -06:00			`pub mod thin_client;`
Add thin_client_service 2018-05-09 14:56:34 -06:00			`pub mod thin_client_service;`
Rework sig processing threads and add perf for process/verify 2018-05-07 16:49:15 -07:00			`pub mod timing;`
AccountantSkel -> Tpu The terms Stub and Skel come from OMG IDL and only made sense while the Stub was acting as an RPC client for the the Accountant object. Nowadays, the Stub interface looks nothing like the Accountant and meanwhile we've recognized the multithreaded implementation is more reminiscent of a pipelined CPU. Thus, we finally bite the bullet and rename our modules. AccountantSkel -> Tpu AccountantStub -> ThinClient Up next will be moving much of the TPU code into separate modules, each representing a stage of the pipeline. The interface of each will follow the precedent set by the Historian object. 2018-05-08 17:32:50 -06:00			`pub mod tpu;`
cargo +nightly fmt 2018-05-08 18:59:01 -06:00			`pub mod transaction;`
Allow event log to hold events of any serializable (hashable) type 2018-02-26 16:42:31 -07:00			`extern crate bincode;`
Implement window service Batch out of order blobs until we have a contigious window. 2018-04-02 19:32:58 -07:00			`extern crate byteorder;`
Add DateTime and Cancel conditions Fixes #32, #33 2018-03-07 21:55:49 -07:00			`extern crate chrono;`
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;`
Change for cuda verify integration 2018-03-26 21:07:11 -07:00			`extern crate libc;`
Fast UdpSocket reader * message needs to fit into 256 bytes * allocator to keep track of blocks of messages * udp socket receiver server that fills up the block as fast as possible * udp socket sender server that sends out the block as fast as possible 2018-03-07 13:47:13 -08:00			`#[macro_use]`
No longer rename log crate 2018-03-19 10:18:48 -06:00			`extern crate log;`
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;`
Fast UdpSocket reader * message needs to fit into 256 bytes * allocator to keep track of blocks of messages * udp socket receiver server that fills up the block as fast as possible * udp socket sender server that sends out the block as fast as possible 2018-03-07 13:47:13 -08:00
Add FutureResult to return a Future that immediately resolves 2018-04-24 13:15:08 -04:00			`extern crate futures;`

Fast UdpSocket reader * message needs to fit into 256 bytes * allocator to keep track of blocks of messages * udp socket receiver server that fills up the block as fast as possible * udp socket sender server that sends out the block as fast as possible 2018-03-07 13:47:13 -08:00			`#[cfg(test)]`
			`#[macro_use]`
			`extern crate matches;`
Rework sig processing threads and add perf for process/verify 2018-05-07 16:49:15 -07:00
			`extern crate rand;`