Build Status

acmd is an alternative full node actinium 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 consensus bugs) for block acceptance as Bitcoin Core. We have taken great care to avoid ltcd causing a fork to the block chain. It includes a full block validation testing framework which contains all of the 'official' block acceptance tests (and some additional ones) that is run on every pull request to help ensure it properly follows consensus. Also, it passes all of the JSON test data in the Bitcoin Core code.

It also properly relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all individual transactions admitted to the pool follow the rules required by the block chain and also includes more strict checks which filter transactions based on miner requirements ("standard" transactions).

One key difference between ltcd and Bitcoin Core is that ltcd 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 ltcd. That functionality is provided by the btcwallet and Paymetheus (Windows-only) projects which are both under active development.


Go 1.12 or newer.


Windows - MSI Available

Linux/BSD/MacOSX/POSIX - Build from Source
  • Install Go according to the installation instructions here:

  • Ensure Go was installed properly and is a supported version:

$ go version

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. It is also recommended to add $GOPATH/bin to your PATH at this point.

  • Run the following commands to obtain acmd, all dependencies, and install it:
$ cd $GOPATH/src/
$ GO111MODULE=on go install -v . ./cmd/...
  • acmd (and utilities) will now be installed in $GOPATH/bin. If you did not already add the bin directory to your system path during Go installation, we recommend you do so now.



Install a newer MSI

Linux/BSD/MacOSX/POSIX - Build from Source
  • Run the following commands to update acmd, all dependencies, and install it:
$ cd $GOPATH/src/
$ git pull
$ GO111MODULE=on go install -v . ./cmd/...

Getting Started

acmd has several configuration options available 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 acmd from your Start menu.

$ ./acmd

Issue Tracker

The integrated github issue tracker is used for this project.


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

Release Verification

Please see our documentation on the current build/verification process for all our releases for information on how to verify the integrity of published releases using our reproducible build system.


acmd is licensed under the copyfree ISC License.

Expand ▾ Collapse ▴



acmd is a full-node bitcoin implementation written in Go.

The default options are sane for most users. This means acmd will work 'out of the box' for most users. However, there are also a wide variety of flags that can be used to control it.

The following section provides a usage overview which enumerates the flags. An interesting point to note is that the long form of all of these options (except -C) can be specified in a configuration file that is automatically parsed when acmd starts up. By default, the configuration file is located at ~/.acmd/acmd.conf on POSIX-style operating systems and %LOCALAPPDATA%\acmd\acmd.conf on Windows. The -C (--configfile) flag, as shown below, can be used to override this location.


acmd [OPTIONS]

Application Options:

-V, --version             Display version information and exit
-C, --configfile=         Path to configuration file
-b, --datadir=            Directory to store data
    --logdir=             Directory to log output.
-a, --addpeer=            Add a peer to connect with at startup
    --connect=            Connect only to the specified peers at startup
    --nolisten            Disable listening for incoming connections -- NOTE:
                          Listening is automatically disabled if the --connect
                          or --proxy options are used without also specifying
                          listen interfaces via --listen
    --listen=             Add an interface/port to listen for connections
                          (default all interfaces port: 9333, testnet: 19333)
    --maxpeers=           Max number of inbound and outbound peers (125)
    --nobanning           Disable banning of misbehaving peers
    --banduration=        How long to ban misbehaving peers.  Valid time units
                          are {s, m, h}.  Minimum 1 second (24h0m0s)
    --banthreshold=       Maximum allowed ban score before disconnecting and
                          banning misbehaving peers.
    --whitelist=          Add an IP network or IP that will not be banned.
                          (eg. or ::1)
-u, --rpcuser=            Username for RPC connections
-P, --rpcpass=            Password for RPC connections
    --rpclimituser=       Username for limited RPC connections
    --rpclimitpass=       Password for limited RPC connections
    --rpclisten=          Add an interface/port to listen for RPC connections
                          (default port: 9334, testnet: 19334)
    --rpccert=            File containing the certificate file
    --rpckey=             File containing the certificate key
    --rpcmaxclients=      Max number of RPC clients for standard connections
    --rpcmaxwebsockets=   Max number of RPC websocket connections (25)
    --rpcquirks           Mirror some JSON-RPC quirks of Bitcoin Core -- NOTE:
                          Discouraged unless interoperability issues need to
                          be worked around
    --norpc               Disable built-in RPC server -- NOTE: The RPC server
                          is disabled by default if no rpcuser/rpcpass or
                          rpclimituser/rpclimitpass is specified
    --notls               Disable TLS for the RPC server -- NOTE: This is only
                          allowed if the RPC server is bound to localhost
    --nodnsseed           Disable DNS seeding for peers
    --externalip=         Add an ip to the list of local addresses we claim to
                          listen on to peers
    --proxy=              Connect via SOCKS5 proxy (eg.
    --proxyuser=          Username for proxy server
    --proxypass=          Password for proxy server
    --onion=              Connect to tor hidden services via SOCKS5 proxy
    --onionuser=          Username for onion proxy server
    --onionpass=          Password for onion proxy server
    --noonion             Disable connecting to tor hidden services
    --torisolation        Enable Tor stream isolation by randomizing user
                          credentials for each connection.
    --testnet             Use the test network
    --regtest             Use the regression test network
    --simnet              Use the simulation test network
    --addcheckpoint=      Add a custom checkpoint.  Format: '<height>:<hash>'
    --nocheckpoints       Disable built-in checkpoints.  Don't do this unless
                          you know what you're doing.
    --uacomment=          Comment to add to the user agent --
                          See BIP 14 for more information.
    --dbtype=             Database backend to use for the Block Chain (ffldb)
    --profile=            Enable HTTP profiling on given port -- NOTE port
                          must be between 1024 and 65536
    --cpuprofile=         Write CPU profile to the specified file
-d, --debuglevel=         Logging level for all subsystems {trace, debug,
                          info, warn, error, critical} -- You may also specify
                          <subsystem>=<level>,<subsystem2>=<level>,... to set
                          the log level for individual subsystems -- Use show
                          to list available subsystems (info)
    --upnp                Use UPnP to map our listening port outside of NAT
    --minrelaytxfee=      The minimum transaction fee in ACM/kB to be
                          considered a non-zero fee.
    --limitfreerelay=     Limit relay of transactions with no transaction fee
                          to the given amount in thousands of bytes per
                          minute (15)
    --norelaypriority     Do not require free or low-fee transactions to have
                          high priority for relaying
    --maxorphantx=        Max number of orphan transactions to keep in memory
    --generate            Generate (mine) bitcoins using the CPU
    --miningaddr=         Add the specified payment address to the list of
                          addresses to use for generated blocks -- At least
                          one address is required if the generate option is
    --blockminsize=       Mininum block size in bytes to be used when creating
                          a block
    --blockmaxsize=       Maximum block size in bytes to be used when creating
                          a block (750000)
    --blockprioritysize=  Size in bytes for high-priority/low-fee transactions
                          when creating a block (50000)
    --nopeerbloomfilters  Disable bloom filtering support.
    --nocfilters          Disable committed filtering (CF) support.
    --sigcachemaxsize=    The maximum number of entries in the signature
                          verification cache.
    --blocksonly          Do not accept transactions from remote peers.
    --relaynonstd         Relay non-standard transactions regardless of the
                          default settings for the active network.
    --rejectnonstd        Reject non-standard transactions regardless of the
                          default settings for the active network.

Help Options:

-h, --help           Show this help message


Path Synopsis
acmjson Package acmjson provides primitives for working with the bitcoin JSON-RPC API.
addrmgr Package addrmgr implements concurrency safe Bitcoin address manager.
blockchain Package blockchain implements bitcoin block handling and chain selection rules.
blockchain/fullblocktests Package fullblocktests provides a set of block consensus validation tests.
blockchain/indexers Package indexers implements optional block chain indexes.
btcec Package btcec implements support for the elliptic curves needed for bitcoin.
chaincfg Package chaincfg defines chain configuration parameters.
chaincfg/chainhash Package chainhash provides abstracted hash functionality.
connmgr Package connmgr implements a generic Bitcoin network connection manager.
database Package database provides a block and metadata storage database.
database/ffldb Package ffldb implements a driver for the database package that uses leveldb for the backing metadata and flat files for block storage.
database/internal/treap Package treap implements a treap data structure that is used to hold ordered key/value pairs using a combination of binary search tree and heap semantics.
integration/rpctest Package rpctest provides a acmd-specific RPC testing harness crafting and executing integration tests by driving a `acmd` instance via the `RPC` interface.
mempool Package mempool provides a policy-enforced pool of unmined bitcoin transactions.
netsync Package netsync implements a concurrency safe block syncing protocol.
peer Package peer provides a common base for creating and managing Bitcoin network peers.
rpcclient Package rpcclient implements a websocket-enabled Bitcoin JSON-RPC client.
txscript Package txscript implements the bitcoin transaction script language.
wire Package wire implements the bitcoin wire protocol.