Bitcoin core reindex
At this point, if you just want to sync the blockchain and run the Insight Block Explorer, then you are done! If you would like to create additional nodes that are not in your global npm installation directory, or run the Bitcore Wallet Service, please do the following:. This will create the directory "mynode" in your current working and install all of the necessary dependencies and configuration files for your node.
Note that you'll need to have txindex enabled in your bitcoin configuration file. For installation instructions regarding the Bitcore Wallet Service, please see wallet service. Your node can run on "livenet" or "testnet". If you wish to configure the network, you can do so by opening the bitcore-node. Then change the network value to "testnet" or "livenet". Here is an example configuration file:.
This configuration includes an exec path to a locally compiled bitcoind and shares the datadir with standard. As mentioned previously, this process can take several hours to complete, so you can start the script and come back later to check on the status.
This will start up all of the services that have been enabled in your configuration file. The first service that will most likely be started is Bitcoin itself, followed by others that depend on it, such as the Database and Address Service. The syncing process will connect to other Bitcoin peers in the network and start downloading the blockchain, verifying proof-of-work, and creating indexes for querying the blockchain.
Both Bitcoin and the Database Service will log the status of the initial synchronization process. If you created your node by running bitcored instead of bitcore create mynode , your node will already have these services installed and you can skip this command.
While running individual CLI commands is a useful way to interact with your node, being able to view it in a GUI is even be better. Let's get started by installing the blockchain explorer Insight! This will run an npm command to download the packages insight-api and insight-ui and add them to your node's package. For more information about the implementation, see https: This release seeks to consensus enforce the rule.
Bitcoin transactions currently may specify a locktime indicating when they may be added to a valid block. Current consensus rules require that blocks have a block header time greater than the locktime specified in any transaction in that block.
Miners get to choose what time they use for their header time, with the consensus rule being that no node will accept a block whose time is more than two hours in the future. The consensus rules also specify that valid blocks may have a header time greater than that of the median of the 11 previous blocks. This GetMedianTimePast time has a key feature we generally associate with time: Mempool inclusion rules currently require transactions to be valid for immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP rule to received transactions, so transaction whose time is greater than the GetMedianTimePast will no longer be accepted into the mempool. Any transactions which are valid under the current rules but not yet valid under the BIP rules will either be mined by other miners or delayed until they are valid under BIP Note, however, that time-based locktime transactions are more or less unseen on the network currently.
GetMedianTimePast always trails behind the current time, so a transaction locktime set to the present time will be rejected by nodes running this release until the median time moves forward. To compensate, subtract one hour 3, seconds from your locktimes to allow those transactions to be included in mempools at approximately the expected time.
The p2p alert system is off by default.