Indeed to use bitcoinrpc, you need to set the username and password in bitcoin.conf by:
rpcauth=user:salt$hash of password
which you can generate using https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py. Simply shutdown bitcoind, add this to bitcoin.conf, restart, and you'll immediately be able to run commands in python like
1: How can it be scanned? how can I see if its exposing any port, or port 8333?
Use getnetworkinfo RPC and results should have one onion address and port number mentioned if onion service is created for Bitcoin Core:
This seems to be more a question about Tor than a Bitcoin specific question, but:
If your bitcoind is set up to use a Tor socks proxy, by default, it will not listen for incoming connections (because by doing so, you'd be listening on your real IP address, which defeats the security you'd gain from Tor). However, if you really want to help the Bitcoin ...
Unfortunately, the information presented on Bitcoin Wiki is misleading. All I had to do is to call getblocktemplate with
JSON object (it happened to be crucial to pass exactly a JSON object, not a string). And for the work completion all I needed to do is to send submitblock request.
Hope it helps someone who's also ...
If you purchased Bitcoin a long time ago, and it's on an exchange, and that exchange still exists, and you can recover your username and password to that exchange, then you should be able to transfer your money off of there.
If you used your own Bitcoin wallet software such as Bitcoin Core, then you will need to have your wallet.dat or other wallet file to ...
Step 1. I backup the wallet and go offline.
To be more secure you should create a wallet with an offline computer.
In general im confused how you use wallet and node. The wallet aims to be a private key, which is computed with a random input, the seed.
The node is a program running, connecting to other programs of its art (p2p).
This program gets ...
In order to set up a multisig transaction, your bitcoind needs to know the public keys that make up that multisig address, and the order that those public keys are listed in. The address itself doesn't contain this information. If you already have 1 bitcoind set up with this information, you can use this script to copy that information to a second bitcoind.
I'm not sure what daemons should be used in this script and ...
You first run two bitcoind daemons locally and then specify their ports as arguments to the command along with other information such as authentication credentials:
# Example usage:
# multisigsync.py \
After a point, there's no reason to increase memory usage further.
dbcache is useful up until the point where you have the entire UTXO in memory (4GB+ in 2021), and then increasing it further does not a lot other than increasing the time to shutdown the node safely (up to many minutes on a slow disk)
maxmempool will increase performance by allowing more ...
You can try my script that can convert raw blockchain database to the simple text format with all blockchain blocks and transactions data in it.
Those text files contain all information you need, but balances need to be calculated through calculation of UTXO set from those data in offine mode. No need RPC calls or any of remote API. All processing goes local ...
If you want to run bitcoin node on an ubuntu machine, it is always recommend to build it from the source code itself. That way you can be almost 100% sure of its authenticity.
sudo apt-get update
sudo apt-get install build-essential software-properties-common
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install ...
You probably need a newer version of gcc.
This helped me fix for Ubuntu: https://askubuntu.com/questions/1140183/install-gcc-9-on-ubuntu-18-04
TL&DR: adds custom PPA repo so you will able to upgrade:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt --fix-broken install
The Bitcoin network doesn't authenticate users. The Bitcoin network doesn't know or need to keep track of people's identities.
Just as a recipient of a $10 bill or €50 banknote don't need to know the identity of the other person, they just need to examine the paper to see if it looks genuine.
Bitcoin is cash, not a bank account.
Bitcoin transactions ...
Here is the protocol: https://electrumx.readthedocs.io/en/latest/protocol.html. If get_mempool serves your use-case then you may use it. You may need to experiment with it to find what is more convenient with Core.
Some apps might be using the Electrum protocol under the hood. Only Electrum allows setting the server manually.
Electrum protocol has blockchain....
Since this question still comes up in search results, it's worth noting that bitcoin-cli now has a getzmqnotifications method. If you get something like this, you've successfully built with ZMQ:
$ bitcoin-cli getzmqnotifications
I think I found a bitcoin private key
So far as I know, a private key is 64 characters long in Hexadecimal (a mix of digits 0-9 and letters A-F only) or 51 characters long in WIF/Base58 (which includes a mix of any uppercase and lowercase letters as well as digits). There's also a mini format that is 22 characters long.
It's 33 letters long
That's likely ...
Are the concerns of my colleague valid or unfounded? Are there valid reasons to believe we will regret self hosting in the long term due to ongoing maintenance costs? If so, what are some issues that we are overlooking with self hosting?
I don't think maintenance of a bitcoin core full node will be a difficult task if the developer is experienced enough and ...
The truth is somewhere in the middle. Your colleague is correct to point out that there is an ongoing cost for maintaining your own full nodes. Beside the employee cost, there is also the cost for the actual server infrastructure, which may be higher than you think if you consider that you will need to maintain high availability, redundancy, testing ...
It appears that btcwire is the Bitcoin p2p module of btcd and neutrino is Lightning Labs's implementation of BIP157/158 (compact client-side block filters (CBF)). I suspect that the agent identifier btcwire 0.5.0/neutrino indicates LND (Lightning Network Daemon) instances which are configured to allow or prefer CBF for synchronization. Given your experience ...
All wallets will calculate and show the same amount as the "balance" for an address. In your example, all wallets would show the balance as 4 BTC. There are exceptions if a wallet is faulty or is not synchronised (not up-to-date, doesn't yet know about latest transactions).
If you import an address into a wallet, it will show the correct balance ...