92635a475e
Ticket voting selection and validation require fast access to a lexicographically sorted list of all available tickets. The current implementation stores these tickets in bucketized maps which are unordered. This means the data has to be sorted every time it is needed in order to select a ticket and validate a block. On my hardware, the process of removing tickets that have been voted and adding new tickets takes ~27ms with the current implementation. In order to speed this up, this introduces a new internal package named tickettreap that provides a tailored treap data structure that is intended to be used for the in-memory live ticket pool when the new database and blockchain enhancements have been synced from upstream. Since it maintains the data in sorted order, it provides a significant speedup over the current map-based implementation. On my hardware, this implementation is able to remove the tickets that have voted and add the new tickets in ~0.083ms and iterate the entire structure for selecting the tickets in ~1.88ms for a total of ~1.96ms. That equates to roughly 14x faster access. In addition, it would also be possible for the stake code to keep a map for height-based lookups (while still relying on this new data structure for keeping the lexicographic sort ordering requirements) for an even greater speedup since it would eliminate the need to iterate the structure to remove tickets at a given height. Finally, when evaluating forks, the current code is quite inefficient because it needs to make a copy of all of the live ticket maps. This new structure provides O(1) snapshot/copy capabilities so it is much more efficient in that regard as well. Benchmarks: ImmutableCopy 30000000 40.7 ns/op 0 B/op 0 allocs/op ImmutableIterate 1000 1881738 ns/op 0 B/op 0 allocs/op |
||
|---|---|---|
| addrmgr | ||
| blockchain | ||
| chaincfg | ||
| cmd | ||
| database | ||
| database2 | ||
| dcrec | ||
| dcrjson | ||
| docs | ||
| limits | ||
| mining | ||
| peer | ||
| release | ||
| txscript | ||
| wire | ||
| .gitignore | ||
| .travis.yml | ||
| blocklogger.go | ||
| blockmanager.go | ||
| chainindexer.go | ||
| CHANGES | ||
| config.go | ||
| cpuminer.go | ||
| dcrd.go | ||
| deps.txt | ||
| discovery.go | ||
| doc.go | ||
| dynamicbanscore_test.go | ||
| dynamicbanscore.go | ||
| goclean.sh | ||
| LICENSE | ||
| log.go | ||
| mempool.go | ||
| mempoolerror.go | ||
| mining_test.go | ||
| mining.go | ||
| miningerror.go | ||
| mrunoncemap_test.go | ||
| mrunoncemap.go | ||
| params.go | ||
| policy_test.go | ||
| policy.go | ||
| README.md | ||
| rpcserver.go | ||
| rpcserverhelp_test.go | ||
| rpcserverhelp.go | ||
| rpcwebsocket.go | ||
| sample-dcrd.conf | ||
| server.go | ||
| service_windows.go | ||
| signal.go | ||
| signalsigterm.go | ||
| upgrade.go | ||
| upnp.go | ||
| version.go | ||
dcrd
[
]
(https://travis-ci.org/decred/dcrd) ![ISC License]
(http://img.shields.io/badge/license-ISC-blue.svg)
dcrd is a Decred full node implementation written in Go (golang).
This project is currently under active development and is in a Beta state. It is extremely stable and has been in production use since October 2013.
It properly downloads, validates, and serves the block chain using the exact rules (including bugs) for block acceptance as Bitcoin Core. We have taken great care to avoid dcrd causing a fork to the block chain. It passes all of the 'official' block acceptance tests (https://github.com/TheBlueMatt/test-scripts) as well as all of the JSON test data in the Bitcoin Core code.
It also relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all transactions admitted to the pool follow the rules required by the block chain and also includes the same checks which filter transactions based on miner requirements ("standard" transactions) as Bitcoin Core.
One key difference between dcrd and Bitcoin Core is that dcrd does NOT include wallet functionality and this was a very intentional design decision. See the blog entry here for more details. This means you can't actually make or receive payments directly with dcrd. That functionality is provided by the dcrwallet and Paymetheus (Windows-only) projects which are both under active development.
Requirements
Go 1.5 or newer.
Installation
Windows - MSI Available
https://github.com/decred/dcrd/releases
Linux/BSD/MacOSX/POSIX - Build from Source
-
Install Go according to the installation instructions here: http://golang.org/doc/install
-
Ensure Go was installed properly and is a supported version:
$ go version
$ go env GOROOT GOPATH
NOTE: The GOROOT and GOPATH above must not be the same path. It is
recommended that GOPATH is set to a directory in your home directory such as
~/goprojects to avoid write permission issues.
- Run the following command to obtain dcrd, all dependencies, and install it:
$ go get -u github.com/decred/dcrd/...
- dcrd (and utilities) will now be installed in either
$GOROOT/binor$GOPATH/bindepending on your configuration. If you did not already add the bin directory to your system path during Go installation, we recommend you do so now.
Updating
Windows
Install a newer MSI
Linux/BSD/MacOSX/POSIX - Build from Source
- Run the following command to update dcrd, all dependencies, and install it:
$ go get -u -v github.com/decred/dcrd/...
Getting Started
dcrd has several configuration options avilable to tweak how it runs, but all of the basic operations described in the intro section work with zero configuration.
Windows (Installed from MSI)
Launch dcrd from your Start menu.
Linux/BSD/POSIX/Source
$ ./dcrd
IRC
- irc.freenode.net
- channel #decred
- webchat
Issue Tracker
The integrated github issue tracker is used for this project.
Documentation
The documentation is a work-in-progress. It is located in the docs folder.
License
dcrd is licensed under the copyfree ISC License.