gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
340 Commits 81 Branches 357 Tags
v0.4.0
Commit Graph

225 Commits

Author SHA1 Message Date
Greg Fitzgerald
c998fbe2ae Sign the owner's public key 
Without this, the accountant will reject transfers from different
entities if they are for the same amount and to the same entity.
 2018-03-02 11:56:42 -07:00
Greg Fitzgerald
9f12cd0c09 Purge the Claim event type 
It's now represented as a Transaction from an unknown party.
 2018-03-02 11:48:58 -07:00
Greg Fitzgerald
0d0fee1ca1 Sign Claim's 'to' field 
Otherwise, the accountant will treat deposits of the same amount as
duplicates.
 2018-03-02 11:46:22 -07:00
Greg Fitzgerald
a0410c4677 Pipe all Claim constructors through a function 2018-03-02 10:58:43 -07:00
Greg Fitzgerald
8fe464cfa3 Rename Claim's key field to match same field in Transaction 2018-03-02 10:47:21 -07:00
Greg Fitzgerald
3e2d6d9e8b Generalize Transaction to express a Claim 
If a Transaction doesn't have an existing address, it's being used
to create new funds.
 2018-03-02 10:41:15 -07:00
Greg Fitzgerald
32d677787b Reduce transactions sent by demo 
We don't do retries yet, so keep tx count to something that won't
trigger any packet loss.
 2018-03-02 10:35:38 -07:00
Greg Fitzgerald
dfd1c4eab3 Don't process transaction if channel.send() fails. 
Do all input validation first, then log (which can fail). If all
goes swimmingly, process the transaction.
 2018-03-02 10:17:52 -07:00
Greg Fitzgerald
36bb1f989d More defense against a double-spend attack 
Before this change, a client could spend funds before the accountant
processed a previous spend. With this change in place, the accountant
updates balances immediately, but that comes at an architectural cost.
The accountant now verifies signatures on behalf of the historian, so
that it can ensure logging will not fail.
 2018-03-02 09:55:44 -07:00
Greg Fitzgerald
684f4c59e0 Delete commented out code 
accountant crate shouldn't verify the log. Instead, it should
only add valid entries and leave verification to network nodes.
 2018-03-02 08:51:29 -07:00
Greg Fitzgerald
1b77e8a69a 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:57 -07:00
Greg Fitzgerald
c935fdb12f Move signature duplicate detection into the historian 2018-03-01 17:44:10 -07:00
Greg Fitzgerald
9e16937914 Delete the Discovery event 
Not useful to the accountant.
 2018-03-01 17:02:41 -07:00
Greg Fitzgerald
f705202381 No need to hash data that's already hashed to create the signature 2018-03-01 16:39:09 -07:00
Greg Fitzgerald
570e71f050 Check for duplicate signatures 
TODO: have client add recent hash to each message
 2018-03-01 14:07:39 -07:00
Greg Fitzgerald
c9cc4b4369 Switch to UDP from TCP 
And remove all the sleep()'ing around.
 2018-03-01 13:47:53 -07:00
Greg Fitzgerald
4610de8fdd Switch to sync_channel to preserve order 2018-02-28 19:33:28 -07:00
Greg Fitzgerald
3fcc2dd944 Add testnode 
Fixes #20
 2018-02-28 18:05:20 -07:00
Greg Fitzgerald
8299bae2d4 Add accountant stub 2018-02-28 16:01:12 -07:00
Greg Fitzgerald
604ccf7552 Add network interface for accountant 2018-02-28 14:00:04 -07:00
Greg Fitzgerald
c3bb207488 Verify event signatures before adding log entries 2018-02-28 10:23:01 -07:00
Greg Fitzgerald
fa4d9e8bcb Add more tests 2018-02-27 11:28:10 -07:00
Greg Fitzgerald
34b77efc87 Sleep longer for TravisCI 2018-02-27 11:08:28 -07:00
Greg Fitzgerald
5ca0ccbcd2 Add accountant 2018-02-27 10:54:06 -07:00
Greg Fitzgerald
f98e9a2ad7 Fix overuse of search-and-replace 2018-02-26 17:03:50 -07:00
Greg Fitzgerald
c6134cc25b Allow the historian to track ownership of any type of data 2018-02-26 17:01:22 -07:00
Greg Fitzgerald
0443b39264 Allow event log to hold events of any serializable (hashable) type 2018-02-26 16:42:31 -07:00
Greg Fitzgerald
8b0b8efbcb Allow Entry to hold events of any kind of data 2018-02-26 15:37:33 -07:00
Greg Fitzgerald
97449cee43 Allow events to hold any kind of data 2018-02-26 15:31:01 -07:00
Greg Fitzgerald
ab5252c750 Move entry verification out of Entry impl 2018-02-26 14:39:01 -07:00
Greg Fitzgerald
b02eab57d2 Extend the event log with a Transaction event to transfer possession 
This implementation assumes 'from' is the current owner of 'data'.
Once that's verified, the signature ensures that nobody modified
'data' (the asset being transferred) or 'to' the entity taking
ownership.

Fixes #14
 2018-02-26 11:09:11 -07:00
Greg Fitzgerald
b8d52cc3e4 Make the Discovery event into a struct instead of a tuple 2018-02-24 11:15:03 -07:00
Greg Fitzgerald
d78082f5e4 Test bad signature 2018-02-24 10:27:51 -07:00
Greg Fitzgerald
08e501e57b 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 10:09:49 -07:00
Greg Fitzgerald
29a607427d Rename UserDataKey to Discovery 
From the perspective of the log, when some data's hash is added,
that data is "discovered" by the historian.  Another event
might be a "claim" that some signed data belongs to the owner of a
public key.
 2018-02-24 05:25:19 -07:00
Greg Fitzgerald
c1326ac3d5 Up the time to sleep so that ticks are generated 2018-02-21 12:22:23 -07:00
Greg Fitzgerald
7871b38c80 Update demo to use self-ticking logger 2018-02-21 11:52:03 -07:00
Greg Fitzgerald
b34d2d7dee Allow the logger to inject Tick events on its own 2018-02-21 11:33:42 -07:00
Greg Fitzgerald
fa4e232d73 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:13 -07:00
Greg Fitzgerald
6e37f70d55 Test reorder attack 2018-02-20 14:46:36 -07:00
Greg Fitzgerald
d97112d7f0 Explain proof-of-history in the readme 
Also:
* Hash userdata so that verification works as the readme describes.
* Drop itertools package. Found a way to use std::iter instead.

Fixes #8
 2018-02-20 14:04:49 -07:00
Greg Fitzgerald
ba90e43f72 Update benchmark 
* Add asm, though it doesn't make it faster. TODO: use avx instructions.
* Do 10x less hashes, since sha256 is more expensive.
 2018-02-19 16:51:35 -07:00
Greg Fitzgerald
0297edaf1f 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:23:53 -07:00
Greg Fitzgerald
bb22522e45 Remove assertions that fail in the kcov docker container 2018-02-19 12:54:01 -07:00
Greg Fitzgerald
bd3fe5fac9 Sleep a little longer to ensure Travis context switches 2018-02-19 12:33:33 -07:00
Greg Fitzgerald
10a70a238b Cleanup demo 2018-02-19 12:25:57 -07:00
Greg Fitzgerald
4a7156de43 Move hash generation into stateless function 2018-02-19 12:09:58 -07:00
Greg Fitzgerald
d88d1b2a09 Reset historian's hasher between events 
Hasher will generate different hashes for the same input if it
had already generated a hash.

Also add a binary to ensure the example in the README works.
 2018-02-19 12:03:06 -07:00
Greg Fitzgerald
5e3c7816bd Ensure verify_slice succeeds 2018-02-19 09:09:24 -07:00
Greg Fitzgerald
ceb65c2669 Better function names 2018-02-18 10:05:54 -07:00