[BREAKGLASS] Append-only mirror of github.com/seedhammer/dcrd
Go to file
Dave Collins 93efe6bfe3
mempool: Implement orphan expiration.
This implements orphan expiration in the mempool such that any orphans
that have not had their ancestors materialize within 15 minutes of their
initial arrival time will be evicted which in turn will remove any other
orphans that attempted to redeem it.

In order to perform the evictions with reasonable efficiency, an
opportunistic scan interval of 5 minutes is used.  That is to say that
there is not a hard deadline on the scan interval and instead it runs
when a new orphan is added to the pool if enough time has passed.

The following is an example of running this code against the main
network for around an hour while intentionally generating orphans to
test:

2019-10-28 01:44:36.272 [DBG] TXMP: Expired 2 orphans (remaining: 46)
2019-10-28 01:49:39.915 [DBG] TXMP: Expired 17 orphans (remaining: 49)
2019-10-28 01:54:47.704 [DBG] TXMP: Expired 15 orphans (remaining: 43)
2019-10-28 01:59:53.414 [DBG] TXMP: Expired 16 orphans (remaining: 56)
2019-10-28 02:05:09.858 [DBG] TXMP: Expired 16 orphans (remaining: 68)
2019-10-28 02:10:10.567 [DBG] TXMP: Expired 16 orphans (remaining: 78)
2019-10-28 02:15:11.736 [DBG] TXMP: Expired 26 orphans (remaining: 82)
2019-10-28 02:48:34.352 [DBG] TXMP: Expired 85 orphans (remaining: 0)

As can be seen from the above, without orphan expiration on this data
set, the orphan pool would have grown an additional 193 entries.
2019-10-28 11:37:06 -05:00
.github build: update golangci-lint to v1.21.0 2019-10-17 15:42:53 -05:00
addrmgr server: improve address discovery. 2019-10-27 11:44:15 -05:00
bech32 build: Replace TravisCI with CI via Github actions. 2019-09-20 19:59:04 -05:00
blockchain multi: resolve todos. 2019-10-27 16:34:24 -05:00
certgen build: Replace TravisCI with CI via Github actions. 2019-09-20 19:59:04 -05:00
chaincfg chaincfg: Prepare v2.3.0. 2019-10-14 15:34:49 -05:00
cmd blockchain: Start v3 module dev cycle. 2019-10-24 21:15:06 -05:00
connmgr connmgr: Start v3 module dev cycle. 2019-10-28 11:34:11 -05:00
crypto crypto: import ripemd160 2019-10-07 19:54:15 -05:00
database dcrutil: Start v3 module dev cycle. 2019-10-24 19:13:26 -05:00
dcrec secp256k1: Prepare v2.0.0. 2019-10-07 15:24:46 -05:00
dcrjson dcrjson: Prepare v3.0.1. 2019-10-14 15:54:11 -05:00
dcrutil dcrutil: drop chainec 2019-10-25 21:27:01 -05:00
docs multi: Add tpl update reason to work ntfns. 2019-10-14 14:32:24 -05:00
fees stake: Start v3 module dev cycle. 2019-10-24 22:10:39 -05:00
gcs stake: Start v3 module dev cycle. 2019-10-24 22:10:39 -05:00
hdkeychain dcrutil: Start v3 module dev cycle. 2019-10-24 19:13:26 -05:00
internal rpcserver: Add basic initial package documentation. 2019-10-24 21:37:44 -05:00
lru build: Replace TravisCI with CI via Github actions. 2019-09-20 19:59:04 -05:00
mempool mempool: Implement orphan expiration. 2019-10-28 11:37:06 -05:00
mining mining: Add priority calculation tests. 2019-10-26 01:49:24 -05:00
peer txscript: Start v3 module dev cycle. 2019-10-24 20:48:43 -05:00
release Add example service files. 2017-03-23 02:07:08 -05:00
rpc/jsonrpc/types rpc/jsonrpc/types: Prepare v2.0.0. 2019-10-14 16:19:50 -05:00
rpcclient rpcclient: add automatic pinging. 2019-10-27 17:23:25 -05:00
rpctest txscript: drop chainec 2019-10-25 21:27:01 -05:00
sampleconfig build: Replace TravisCI with CI via Github actions. 2019-09-20 19:59:04 -05:00
txscript txscript: drop chainec 2019-10-25 21:27:01 -05:00
wire wire: Prepare v1.3.0. 2019-10-14 13:19:05 -05:00
.dockerignore docker: Add dockerfiles for running dcrd nodes. 2018-07-07 05:33:53 -05:00
.gitignore main: add address encoding magic constants test 2018-09-26 16:09:11 -05:00
blocklogger.go dcrutil: Start v3 module dev cycle. 2019-10-24 19:13:26 -05:00
blockmanager.go mempool: Start v4 module dev cycle. 2019-10-25 21:27:54 -05:00
cert_test.go main: move cert tests to a separated file 2018-10-18 20:06:53 +02:00
CHANGES multi: Use https links where available. 2019-06-18 14:20:06 -05:00
config_test.go travis: Test go1.13 and drop go1.11. 2019-09-03 15:08:35 -05:00
config.go connmgr: Start v3 module dev cycle. 2019-10-28 11:34:11 -05:00
cpuminer.go blockchain: Start v3 module dev cycle. 2019-10-24 21:15:06 -05:00
dcrd.go multi: resolve todos. 2019-10-27 16:34:24 -05:00
doc.go multi: Correct typos. 2019-08-16 17:37:58 -05:00
Dockerfile docker: update alpine and include notes. 2019-07-20 18:22:23 -05:00
Dockerfile.alpine docker: update alpine and include notes. 2019-07-20 18:22:23 -05:00
go.mod connmgr: Start v3 module dev cycle. 2019-10-28 11:34:11 -05:00
go.sum txscript: Start v3 module dev cycle. 2019-10-24 20:48:43 -05:00
ipc.go multi: Correct typos. 2019-08-16 17:37:58 -05:00
LICENSE multi: Add initial committed filter (CF) support 2018-03-30 13:52:12 -04:00
log.go connmgr: Start v3 module dev cycle. 2019-10-28 11:34:11 -05:00
mining_test.go stake: Start v3 module dev cycle. 2019-10-24 22:10:39 -05:00
mining.go stake: Start v3 module dev cycle. 2019-10-24 22:10:39 -05:00
miningerror.go multi: Implement header commitments and vote. 2019-10-12 12:06:02 -05:00
networkparams_test.go multi: Correct typos. 2019-08-16 17:37:58 -05:00
params.go main: Update to use all new major module versions. 2019-08-13 11:22:37 -05:00
README.md build: Replace TravisCI with CI via Github actions. 2019-09-20 19:59:04 -05:00
require.go multi: Use secp256k1/v2 module. 2019-10-08 10:14:13 -05:00
rpcadaptors.go rpcserver: Move rpc syncmgr iface to internal pkg. 2019-10-24 21:37:24 -05:00
rpcserver_test.go multi: Correct typos. 2019-08-16 17:37:58 -05:00
rpcserver.go rpcserver: Bump to 6.1.1. 2019-10-27 22:18:33 -05:00
rpcserverhelp_test.go blockchain: Rework to use new db interface. 2016-08-18 15:42:18 -04:00
rpcserverhelp.go multi: add notifywork rpc. 2019-10-12 19:45:55 -05:00
rpcwebsocket.go stake: Start v3 module dev cycle. 2019-10-24 22:10:39 -05:00
run_tests.sh build: Setup github actions for CI. 2019-09-20 12:40:49 -05:00
server.go connmgr: Start v3 module dev cycle. 2019-10-28 11:34:11 -05:00
service_windows.go multi: Correct typos. 2019-08-22 10:20:03 -05:00
signal.go main: Convert signal handling to use context. 2019-04-01 14:09:07 -05:00
signalsigterm.go Add pipes for parent process IPC. (#311) 2016-08-31 10:45:16 -04:00
upnp.go multi: Correct typos. 2019-08-22 10:20:03 -05:00

dcrd

Build Status ISC License GoDoc Go Report Card

Decred Overview

Decred is a blockchain-based cryptocurrency with a strong focus on community input, open governance, and sustainable funding for development. It utilizes a hybrid proof-of-work and proof-of-stake mining system to ensure that a small group cannot dominate the flow of transactions or make changes to Decred without the input of the community. A unit of the currency is called a decred (DCR).

https://decred.org

Latest Downloads

https://decred.org/downloads

What is dcrd?

dcrd is a full node implementation of Decred written in Go (golang).

It acts as a fully-validating chain daemon for the Decred cryptocurrency. dcrd maintains the entire past transactional ledger of Decred and allows relaying of transactions to other Decred nodes around the world.

This software is currently under active development. It is extremely stable and has been in production use since February 2016.

The software was originally forked from btcd, which is a bitcoin full node implementation that is still under active development. To gain the benefit of btcd's ongoing upgrades, including improved peer and connection handling, database optimization, and other blockchain related technology improvements, dcrd is continuously synced with the btcd codebase.

What is a full node?

The term 'full node' is short for 'fully-validating node' and refers to software that fully validates all transactions and blocks, as opposed to trusting a 3rd party. In addition to validating transactions and blocks, nearly all full nodes also participate in relaying transactions and blocks to other full nodes around the world, thus forming the peer-to-peer network that is the backbone of the Decred cryptocurrency.

The full node distinction is important, since full nodes are not the only type of software participating in the Decred peer network. For instance, there are 'lightweight nodes' which rely on full nodes to serve the transactions, blocks, and cryptographic proofs they require to function, as well as relay their transactions to the rest of the global network.

Why run dcrd?

As described in the previous section, the Decred cryptocurrency relies on having a peer-to-peer network of nodes that fully validate all transactions and blocks and then relay them to other full nodes.

Running a full node with dcrd contributes to the overall security of the network, increases the available paths for transactions and blocks to relay, and helps ensure there are an adequate number of nodes available to serve lightweight clients, such as Simplified Payment Verification (SPV) wallets.

Without enough full nodes, the network could be unable to expediently serve users of lightweight clients which could force them to have to rely on centralized services that significantly reduce privacy and are vulnerable to censorship.

In terms of individual benefits, since dcrd fully validates every block and transaction, it provides the highest security and privacy possible when used in conjunction with a wallet that also supports directly connecting to it in full validation mode, such as dcrwallet (CLI) and Decrediton (GUI).

  • 10 GB disk space (as of September 2018, increases over time)
  • 1GB memory (RAM)
  • ~150MB/day download, ~1.5GB/day upload
    • Plus one-time initial download of the entire block chain
  • Windows 7/8.x/10 (server preferred), macOS, Linux
  • High uptime

Getting Started

So, you've decided to help the network by running a full node. Great! Running dcrd is simple. All you need to do is install dcrd on a machine that is connected to the internet and meets the minimum recommended specifications, and launch it.

Also, make sure your firewall is configured to allow inbound connections to port 9108.

Installing and updating

Binaries (Windows/Linux/macOS)

Binary releases are provided for common operating systems and architectures:

https://decred.org/downloads

Build from source (all platforms)

Building or updating from source requires the following build dependencies:

  • Go 1.11 or 1.12

    Installation instructions can be found here: https://golang.org/doc/install. It is recommended to add $GOPATH/bin to your PATH at this point.

  • Git

    Installation instructions can be found at https://git-scm.com or https://gitforwindows.org.

To build and install from a checked-out repo, run go install . ./cmd/... in the repo's root directory. Some notes:

  • Set the GO111MODULE=on environment variable if building from within GOPATH.

  • The dcrd executable will be installed to $GOPATH/bin. GOPATH defaults to $HOME/go (or %USERPROFILE%\go on Windows) if unset.

Example of obtaining and building from source on Windows 10:

PS> git clone https://github.com/decred/dcrd $env:USERPROFILE\src\dcrd
PS> cd $env:USERPROFILE\src\dcrd
PS> go install . .\cmd\...
PS> & "$(go env GOPATH)\bin\dcrd" -V

Docker

Running dcrd

You can run a decred node from inside a docker container. To build the image yourself, use the following command:

docker build -t decred/dcrd .

Or you can create an alpine based image (requires Docker 17.05 or higher):

docker build -t decred/dcrd:alpine -f Dockerfile.alpine .

You can then run the image using:

docker run decred/dcrd

You may wish to use an external volume to customise your config and persist the data in an external volume:

docker run --rm -v /home/user/dcrdata:/root/.dcrd/data decred/dcrd

For a minimal image, you can use the decred/dcrd:alpine tag. This is typically a more secure option while also being a much smaller image.

You can run dcrctl from inside the image. For example, run an image (mounting your data from externally) with:

docker run --rm -ti --name=dcrd-1 -v /home/user/.dcrd:/root/.dcrd \
  decred/dcrd:alpine

And then run dcrctl commands against it. For example:

docker exec -ti dcrd-1 dcrctl getbestblock

Running Tests

All tests and linters may be run in a docker (or podman) container using the script run_tests.sh by specifying either docker or podman as the first parameter. This script defaults to using the current latest supported version of Go, but it also respects the GOVERSION environment variable set to the major version of Go to allow testing on a previous version of Go. Generally, Decred only supports the current and previous major versions of Go.

./run_tests.sh docker

To run the tests locally without docker on the latest supported version of Go:

./run_tests.sh

To run the tests locally without docker on Go 1.11:

GOVERSION=1.11 ./run_tests.sh

Contact

If you have any further questions you can find us at:

https://decred.org/community

Issue Tracker

The integrated github issue tracker is used for this project.

Documentation

The documentation for dcrd is a work-in-progress. It is located in the docs folder.

License

dcrd is licensed under the copyfree ISC License.