2
getblockstats
"txs" : n, (numeric) The number of transactions (including coinbase)
Example
C:\Program Files\Bitcoin\daemon> bitcoin-cli getblockcount
627251
C:\Program Files\Bitcoin\daemon> bitcoin-cli getblockstats 627251 | findstr /C:"\"txs\":"
"txs": 2103,
The full output contains ...
2
If you are trying to load a wallet, then you do not need to be using a wallet specific endpoint. loadwallet is not actually a wallet RPC so it does not need the wallet specific endpoint.
If you are trying to access a wallet that has already been loaded, then you have the wrong endpoint. The endpoint does not include the wallet.dat file. Bitcoin Core gives ...
2
regtest is the test network best suited for this kind of testing. While it does still have a PoW requirement, the work required is basically negligible. It also does not do retargeting so the difficulty does not change. This allows you to create blocks at will. So you can use the regtest network option in order to test that your code is creating blocks ...
2
You can use the rpcallowip feature in your bitcoin.conf to whitelist IP addresses.
https://bitcoin.org/en/release/v0.10.0#rpc-access-control-changes
1
Even I am getting weird errors using python-OP_RETURN, last commit in this repository was in 2017 so maybe we need to make few changes in the code.
If you want to experiment with OP_RETURN, it can be done using Bitcoin Core. Example:
Convert string to hex: https://codebeautify.org/string-hex-converter
createrawtransaction '[]' '{"data":"...
1
Not every transaction output has an address. In this case, the output you are looking at, while it is a standard output type, it does not have an associated address. It is a Pay to Public Key script for which there is no address. Thus gettxout does not provide an address.
1
There is no way for a block explorer to know which addresses belong to the same wallets, in fact no block explorer shows the balance of wallets but only by addresses.
The only way to know which addresses are from the same wallet is having generated that wallet or having it's seed.
Wallets are a client structure that collects all the addresses for which you ...
1
Big disclaimer: you really shouldn't do this. Transaction prioritization works based on fee per size, so that's what you should be configuring.
As for an explanation of what you're seeing: the block explorer you're using is showing the wrong size. For fee computations what you need is the vsize, not the serialized size. This is the size that takes the ...
1
Tons of red flags here.
I've been around for a while and have never heard of this client.
Browsing the site, all the pages dedicated to code or developer documentation are non-existent or lead to placeholders.
I reached out to Will Binns whose name is given as the maintainer of
the ostensible "Bitcoin client" Bitly Core on the "developer
...
Only top voted, non community-wiki answers of a minimum length are eligible
