Skip to content
Privacy-preserving auditing for distributed ledgers
Branch: master
Clone or download
Nabeelperson Merge pull request #2 from gertjaap/master
Use ZKSigma in stead of built in crypto.go
Latest commit a7f074c Mar 8, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmd Fixed comments Mar 8, 2019
.gitignore zkLedger as run in NVV18 (zkledger.pdf) Feb 14, 2019
DEVELOPERS.md update readme Feb 14, 2019
README.md update readme Feb 14, 2019
audit.go Fixed comments Mar 8, 2019
audit_test.go Rename package apl to package zkledger Feb 15, 2019
bank.go Fixed comments Mar 8, 2019
bank_test.go Fixed comments Mar 8, 2019
clients.go Rename package apl to package zkledger Feb 15, 2019
debug.go Rename package apl to package zkledger Feb 15, 2019
ledger.go Rename package apl to package zkledger Feb 15, 2019
ledger_test.go Rename package apl to package zkledger Feb 15, 2019
pki.go Small fix and adjustment for moving ECPoint functions to ZKCurveParams Mar 1, 2019
testutil.go Rename package apl to package zkledger Feb 15, 2019
transaction.go Fixed comments Mar 8, 2019
zkcurve.go Improved use of ZKSigma and related bugfixes Feb 15, 2019
zkledger.pdf

README.md

zkLedger

zkLedger is a design for a ledger which has private transactions, but supports provably-correct queries over the ledger.

Maybe you'd like to run the tests:

cd $GOPATH/src/github.com/mit-dci/zkledger
go test

Or, run a local experiment with a few banks, a single-server ledger, and an auditor:

cd cmd/setup
go build
./setup -t simple1

(You can add -debug to get a lot of timing information and other debug output)

You can’t perform that action at this time.