Биткоин installer что это в 2019 году

Недавняя ошибка и workchain раскол меня на 32-разрядной ОС Windows исполняемый файл.

  • Operating System: — Debian 9 Stretch
  • Software: — Bitcoin 0.14.1
  • # — requires given linux commands to be executed with root privileges either directly as a root user or by use of sudo command
  • $ — requires given linux commands to be executed as a regular non-privileged user

/.bitcoin directory so you can expect this directory to grow drastically. To stop bitcoin node run:

Subscribe to Linux Career Newsletter to receive latest news, jobs, career advice and featured configuration tutorials.

LinuxConfig is looking for a technical writer(s) geared towards GNU/Linux and FLOSS technologies. Your articles will feature various GNU/Linux configuration tutorials and FLOSS technologies used in combination with GNU/Linux operating system.

When writing your articles you will be expected to be able to keep up with a technological advancement regarding the above mentioned technical area of expertise. You will work independently and be able to produce at minimum 2 technical articles a month.


Some notes on how to build Bitcoin Core in Unix.

(For BSD specific instructions, see build-*bsd.md in this directory.)

Always use absolute paths to configure and compile Bitcoin Core and the dependencies. For example, when specifying the path of the dependency:

Here BDB_PREFIX must be an absolute path — it is defined using $(pwd) which ensures the usage of the absolute path.

This will build bitcoin-qt as well, if the dependencies are met.

These dependencies are required:

Library Purpose Description libssl Crypto Random Number Generation, Elliptic Curve Cryptography libboost Utility Library for threading, data structures, etc libevent Networking OS independent asynchronous networking
Library Purpose Description
miniupnpc UPnP Support Firewall-jumping support
libdb4.8 Berkeley DB Wallet storage (only needed when wallet enabled)
qt GUI GUI toolkit (only needed when GUI enabled)
protobuf Payments in GUI Data interchange format used for payment protocol (only needed when GUI enabled)
libqrencode QR codes in GUI Optional for generating QR codes (only needed when GUI enabled)
univalue Utility JSON parsing and encoding (bundled version will be used unless —with-system-univalue passed to configure)
libzmq3 ZMQ notification Optional, allows generating ZMQ notifications (requires ZMQ version >= 4.0.0)

For the versions used, see dependencies.md

C++ compilers are memory-hungry. It is recommended to have at least 1.5 GB of memory available when compiling Bitcoin Core. On systems with less, gcc can be tuned to conserve memory with additional CXXFLAGS:

Linux Distribution Specific Instructions

Dependency Build Instructions

Now, you can either build from self-compiled depends or install the required dependencies:

BerkeleyDB is required for the wallet.

Ubuntu and Debian have their own libdb-dev and libdb++-dev packages, but these will install BerkeleyDB 5.1 or later. This will break binary wallet compatibility with the distributed executables, which are based on BerkeleyDB 4.8. If you do not care about wallet compatibility, pass —with-incompatible-bdb to configure.

Otherwise, you can build from self-compiled depends (see above).

To build Bitcoin Core without wallet, see Disable-wallet mode

Optional (see —with-miniupnpc and —enable-upnp-default):

ZMQ dependencies (provides ZMQ API):

If you want to build bitcoin-qt, make sure that the required packages for Qt development are installed. Qt 5 is necessary to build the GUI. To build without GUI pass —without-gui .

To build with Qt 5 you need the following:

libqrencode (optional) can be installed with:

Once these are installed, they will be found by configure and a bitcoin-qt executable will be built by default.

Dependency Build Instructions

To build with Qt 5 you need the following:

libqrencode (optional) can be installed with:

The release is built with GCC and then «strip bitcoind» to strip the debug symbols, which reduces the executable size by about 90%.

miniupnpc may be used for UPnP port mapping. It can be downloaded from here. UPnP support is compiled in and turned off by default. See the configure options for upnp behavior desired:

It is recommended to use Berkeley DB 4.8. If you have to build it yourself, you can use the installation script included in contrib/ like so:

from the root of the repository.

Note: You only need Berkeley DB if the wallet is enabled (see Disable-wallet mode).

If you need to build Boost yourself:

To help make your Bitcoin Core installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default. This can be disabled with:

Hardening enables the following features:

Position Independent Executable: Build position independent code to take advantage of Address Space Layout Randomization offered by some kernels. Attackers who can cause execution of code at an arbitrary memory location are thwarted if they don’t know where anything useful is located. The stack and heap are randomly located by default, but this allows the code section to be randomly located as well.

On an AMD64 processor where a library was not compiled with -fPIC, this will cause an error such as: «relocation R_X86_64_32 against `. ‘ can not be used when making a shared object;»

To test that you have built PIE executable, install scanelf, part of paxutils, and use:

The output should contain:

Non-executable Stack: If the stack is executable then trivial stack-based buffer overflow exploits are possible if vulnerable buffers are found. By default, Bitcoin Core should be built with a non-executable stack, but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection.

To verify that the stack is non-executable after compiling use: scanelf -e ./bitcoin

The output should contain: STK/REL/PTL RW- R— RW-

The STK RW- means that the stack is readable and writeable but not executable.

When the intention is to run only a P2P node without a wallet, Bitcoin Core may be compiled in disable-wallet mode with:

In this case there is no dependency on Berkeley DB 4.8.

Mining is also possible in disable-wallet mode using the getblocktemplate RPC call.

Additional Configure Flags

A list of additional configure flags can be displayed with:

Setup and Build Example: Arch Linux

This example lists the steps necessary to setup and build a command line only, non-wallet distribution of the latest changes on Arch Linux:

Note: Enabling wallet support requires either compiling against a Berkeley DB newer than 4.8 (package db ) using —with-incompatible-bdb , or building and depending on a local version of Berkeley DB 4.8. The readily available Arch Linux packages are currently built using —with-incompatible-bdb according to the PKGBUILD. As mentioned above, when maintaining portability of the wallet between the standard Bitcoin Core distributions and independently built node software is desired, Berkeley DB 4.8 must be used.

These steps can be performed on, for example, an Ubuntu VM. The depends system will also work on other Linux distributions, however the commands for installing the toolchain will be different.

Make sure you install the build requirements mentioned above. Then, install the toolchain and curl:

Оцените статью
Биткоин Блог / и всё о Биткоине