CryptoCoinsInfoClub.com

Bitcoin-cli Examples

Learning-bitcoin-from-the-command-line/12_1_accessing_bitcoind_with_curl.md At Master Christophera/learning-bitcoin-from-the-command-line Github

Learning-bitcoin-from-the-command-line/12_1_accessing_bitcoind_with_curl.md At Master Christophera/learning-bitcoin-from-the-command-line Github

NOTE: This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. bitcoin-cli, the heart of chapters 3-6, is ultimately just a wrapper. It's a way to interface with bitcoind from the command line, providing simplified access to its many RPC commands. But RPC can, of course, be accessed directly. That's what this chapter is about: directly connecting to RPC with the curl command. curl, short for "see URL", is a command-line tool that allows you to directly access URLs in a programmatic way. It's an easy way to interact with servers like bitcoind that listen to ports on the internet and that speak a variety of protocols. Curl is also available as a library for many programming languages, such as C, Java, PHP, and Python. So, once you know how to work with Curl, you'll have a strong foundation for using a lot of different APIs as we'll touch on in the next few chapters. In order to use curl with bitcoind, you must know three things: the standard format, the user name and password, and the correct port. The bitcoin-cli commands are all linked to RPC commands in bitcoind. That makes the transition from using bitcoin-cli to using curl very simple. In fact, if you look at any of the help pages for bitcoin-cli, you'll see that they list not only the bitcoin-cli commands, but also parallel curl commands. For example, here is bitcoin-cli getinfo help: $ bitcoin-cli help getmininginfogetmininginfoReturns a json object containing mining-related information.Result:{ "blocks": nnn, (numeric) The current block "currentblocksize": nnn, (numeric) The last block size "currentblockweight": nnn, (numeric) The last block weight "currentblocktx": nnn, (numeric) The last block transaction "difficulty": xxx.xxxxx (numeric) The current d Continue reading >>

Chain Query: Bitcoin Api: Sendtoaddress

Chain Query: Bitcoin Api: Sendtoaddress

sendtoaddress "address" amount ( "comment" "comment_to" subtractfeefromamount replaceable conf_target "estimate_mode")Send an amount to a given address.Requires wallet passphrase to be set with walletpassphrase call.Arguments:1. "address" (string, required) The bitcoin address to send to.2. "amount" (numeric or string, required) The amount in BTC to send. eg 0.13. "comment" (string, optional) A comment used to store what the transaction is for. This is not part of the transaction, just kept in your wallet.4. "comment_to" (string, optional) A comment to store the name of the person or organization to which you're sending the transaction. This is not part of the transaction, just kept in your wallet.5. subtractfeefromamount (boolean, optional, default=false) The fee will be deducted from the amount being sent. The recipient will receive less bitcoins than you enter in the amount field.6. replaceable (boolean, optional) Allow this transaction to be replaced by a transaction with higher fees via BIP 1257. conf_target (numeric, optional) Confirmation target (in blocks)8. "estimate_mode" (string, optional, default=UNSET) The fee estimate mode, must be one of: "UNSET" "ECONOMICAL" "CONSERVATIVE"Result:"txid" (string) The transaction id.Examples:> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1 "donation" "seans outpost"> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1 "" "" true> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "sendtoaddress", "params": ["1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd", 0.1, "donation", "seans outpost"] }' -H 'content-type: text/plain;' Continue reading >>

Original Bitcoin Client/api Calls List

Original Bitcoin Client/api Calls List

Bitcoin API call list (as of version 0.8.0) Note: up-to-date API reference can be found here . Listing the bitcoin addresses in your wallet is easily done via listreceivedbyaddress. It normally lists only addresses which already have received transactions, however you can list all the addresses by setting the first argument to 0, and the second one to true. Required arguments are denoted inside < and > Optional arguments are inside [ and ]. Add a nrequired-to-sign multisignature address to the wallet. Each key is a bitcoin address or hex-encoded public key. If [account] is specified, assign address to [account]. Returns a string containing the address. version 0.8 Attempts add or remove from the addnode list or try a connection to once. Safely copies wallet.dat to destination, which can be a directory or a path with filename. Creates a multi-signature address and returns a json object version 0.7 Creates a raw transaction spending given inputs. version 0.7 Produces a human-readable JSON object for a raw transaction . Reveals the private key corresponding to version 0.13.0 Exports all wallet private keys to file Returns the account associated with the given address. Returns the current bitcoin address for receiving payments to this account. If does not exist, it will be created along with an associated new address that will be returned. version 0.8 Returns information about the given added node, or all added nodes (note that onetry addnodes are not listed here)If dns is false, only a list of added nodes will be provided,otherwise connected information will also be available. Returns the list of addresses for the given account. If [account] is not specified, returns the server's total available balance. If [account] is specified, returns the balance in the Continue reading >>

Generating Segwit Change Addresses In Bitcoin 0.15

Generating Segwit Change Addresses In Bitcoin 0.15

Generating Segwit Change Addresses in Bitcoin 0.15 Segwit was activated on the Bitcoin network in August 2017. Unfortunately, thereare still not many segwit transactions on mainnet, and most blocks are stillabout 1 MB in size. One of the obstacles here is that the current version ofBitcoin Core, 0.15.1, does not include native segwit support. Bitcoin Core canactually generate segwit addresses relatively easily, with a single RPC call toaddwitnessaddress. But at least at the moment, theres no way to easy receivechange output at a segwit change when using sendtoaddress. Actually Bitcoin Core 0.15 does support this, you just have to use the rawtransaction API. This might sound scary, but its actually not that hard. Inthis post Ill show how to create and use segwit change addresses using the rawtransaction API available in Bitcoin Core 0.15. Bitcoin Core comes with a regression test mode called regtest. In regtest modeyou start with a completely empty blockchain, and there is a special RPC methodthat can be used to generate new blocks (as if you were mining, but without thewait!). This mode is extremely useful for testing Bitcoin features, because youdont need to wait for real blocks to be mined on mainnet or testnet. The first step here will be to run a bitcoind instance in regtest mode andgenerate some blocks: # Launch an instance of bitcoind in regtest mode.$ bitcoind -daemon -regtest# Generate some new blocks. You must generate at least 432 to enable segwit.$ bitcoin-cli -regtest generate 432# # Verify that segwit is enabled.$ bitcoin-cli -regtest getblockchaininfo | jq .bip9_softforks.segwit.status -"active"# Check our balance.$ bitcoin-cli -regtest getbalance14949.69482000 You may get a slightly different balance than what is shown here. The impo Continue reading >>

Bitcoind - Here's How To Send Raw Transaction Btc Using Bitcoin-cli Command - Stack Overflow

Bitcoind - Here's How To Send Raw Transaction Btc Using Bitcoin-cli Command - Stack Overflow

Here's how to send raw transaction BTC using Bitcoin-cli command Michael receives 0.05000000 BTC from Pablo and another 0.01000000 BTC from Kuradang. Michael also wants to send 0.02500000 BTC to Berteng. Each amount that Michael receives has the corresponding txid and other details. Lets check that out using listunspent command then create a raw transaction using createrawtransaction after that sign it using signrawtransaction and send that raw transaction using sendrawtransaction. $ bitcoin-cli listunspent [misconf=1] [max_number_confirmation=99999999] '''[""]''' Lets check Michael's list of unspent using with his address. $ bitcoin-cli listunspent 1 99999999 '''["mkrzDhhZtzQm8zgckSs4fMNrvtNJ66zaFe"]''' [{ "txid": "12b8e7ede4992f4d30f93idj3085746951d945e39f40becebd7c290af8c2e7ad", "vout": 1, "address": "mkrzDhhZtzQm8zgckSs4fMNrvtNJ66zaFe", "account": "micz", "scriptPubKey": "76a9143aa28e1740a6a5a2190975b6e7f1ad67aaec9a3988ac", "amount": 0.05000000, "confirmations": 94, "spendable": true}, { "txid": "8443bc63b65d569ff9ekwm37sy3b67b9c7c6f8f386c3cdf372b260961b64ec9fc", "vout": 1, "address": "mkrzDhhZtzQm8zgckSs4fMNrvtNJ66zaFe", "account": "micz", "scriptPubKey": "76a9143aa28e1740a6a5a2190975b6e7f1ad67aaec9a3988ac", "amount": 0.01000000, "confirmations": 93, "spendable": true}] What we see here is the results that assigned 50 and 10 mBTC to our address mkrz. To spend this output we will create a new transaction. We need to choose some blocks with sufficient amount from the result of listunspent. Since we only need to send 0.02500000 mBTC I think the first block has the enough amount to make the transaction. $ bitcoin-cli createrawtransaction '[{ "txid" : "", "vout" : }]' '{"": , "": }' To pa Continue reading >>

Api Reference (json-rpc)

Api Reference (json-rpc)

Run bitcoind or bitcoin-qt -server. You can control it via the command-line bitcoin-cli utility or by HTTP JSON-RPC commands. You must create a bitcoin.conf configuration file setting an rpcuser and rpcpassword; see Running Bitcoin for details. If you are learning the API, it is a very good idea to use the test network (run bitcoind -testnet and bitcoin-cli -testnet). Running Bitcoin with the -server argument (or running bitcoind) tells it to function as a HTTP JSON-RPC server, but Basic access authentication must be used when communicating with it, and, for security, by default, the server only accepts connections from other processes on the same machine. If your HTTP or JSON library requires you to specify which 'realm' is authenticated, use 'jsonrpc'. Bitcoin supports SSL (https) JSON-RPC connections beginning with version 0.3.14. See the rpcssl wiki page for setup instructions and a list of all bitcoin.conf configuration options. Allowing arbitrary machines to access the JSON-RPC port (using the rpcallowip configuration option ) is dangerous and strongly discouraged-- access should be strictly limited to trusted machines. To access the server you should find a suitable library for your language. See the proper money handling page for notes on avoiding rounding errors when handling bitcoin values. python-jsonrpc is the official JSON-RPC implementation for Python.It automatically generates Python methods for RPC calls.However, due to its design for supporting old versions of Python, it is also rather inefficient. jgarzik has forked it as Python-BitcoinRPC and optimized it for current versions.Generally, this version is recommended. While BitcoinRPC lacks a few obscure features from jsonrpc, software using only the ServiceProxy class can be written the same to work wi Continue reading >>

Glossary | Txid

Glossary | Txid

(Transaction ID) is basically an identification number for a bitcoin transaction. f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 - First ever Bitcoin transaction to Hal Finney in 2010. a1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d - Pizza transaction for 10,000 BTC in 2010. 4ce18f49ba153a51bcda9bb80d7f978e3de6e81b5fc326f00465464530c052f4 - The transaction containing the first donation I received for making this website. A TXID is always 32 bytes (64 characters) and hexadecimal . You get a TXID by hashing transaction data through SHA256 twice. 0100000001c997a5e56e104102fa209c6a852dd90660a20b2d9c352423edce25857fcd3704000000004847304402204e45e16932b8af514961a1d3a1a25fdf3f4f7732e9d624c6c61548ab5fb8cd410220181522ec8eca07de4860a4acdd12909d831cc56cbbac4622082221a8768d1d0901ffffffff0200ca9a3b00000000434104ae1a62fe09c5f51b13905f07f06b99a2f7159b2225f374cd378d71302fa28414e7aab37397f554a7df5f142c21c1b7303b8a0626f1baded5c72a704f7e6cd84cac00286bee0000000043410411db93e1dcdb8a016b49840f8c53bc1eb68a382e97b1482ecad7b148a6909a5cb2e0eaddfb84ccf9744464f82e160bfa9b8b64f9d4c03f999b8643f656b412a3ac00000000 169e1e83e930853391bc6f35f605c6754cfead57cf8387639d3b4096c54f18f4 (Note: reverse the byte order first if you want to find this transaction in the blockchain...) If you've just hashed some transaction data and want to search for a TXID in the blockchain, you have to search for it in reverse byte order. txid (original): 169e1e83e930853391bc6f35f605c6754cfead57cf8387639d3b4096c54f18f4 txid (searching): f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 Due to historical accident, the tx and block hashes that bitcoin core uses are byte-reversed. I'm not entirely sure why. May be something like using openssl bignum to store hashes or something li Continue reading >>

Whats New In Bitcoin Core V0.15part4

Whats New In Bitcoin Core V0.15part4

I work on open source Bitcoin projects at @Chaincodelabs in NYC. Whats new in Bitcoin Core v0.15 part4 In this series, Ive already covered one performance improvement ( per-output chainstate db ) and a couple of user features ( better fee estimation and bumpfee in the GUI ). Today Ill talk about another user feature, multi-wallet. Multi-wallet is a feature thats long been requested by users, and has now been implemented in Bitcoin Core. Users are now able to load more than one wallet when starting the software. Each wallet is completely separated from all others, with its own keys, addresses, balance and transaction outputs. There are many possible use-cases for multi-wallet, such as: Having separate personal and business wallets, with accounting for those wallets completely separated. One user having multiple wallets for different purposes, for example a savings wallet and a checking wallet. One user having a normal transacting wallet, and an additional wallet for a 2nd layer application such as lightning, tumblebit or joinmarket. Multiple users having a wallet on a shared node. Note that there is no authentication for individual wallets, so the users must trust each other. Future versions may introduce authentication for separate user access to individual wallets. When using multi-wallet, each wallet is available through the bitcoin-cli command line tool and the JSON RPC interface. In v0.15 the GUI will only display and allow transactions to be created and signed on the first wallet. However, additional loaded wallets will continue to remain synced to the node and will continue to keep track of their balances and transaction which involve them. This usage pattern, called wallet warming, is useful if you want your home node to keep track of the wallets transactions an Continue reading >>

Upcoder Coding Blog

Upcoder Coding Blog

UpCoder Up, coder! c++, python, game AI, bitcoin The reference bitcoin client includes a powerful API and RPC interface. In this post I show you how to call into this from Python(which is something that turns out to be almost trivially easy to set up). Python can work well as a kind of (overpowered) scripting language for automatingcomplicated tasks through the bitcoin reference client, but this is also a great way to get started outif you're interested in writing more involved software that works with bitcoin transactions or the bitcoin blockchain. Python has good support for byte sequences and large integers and seems to be quitea good fit for bitcoin operations in general,while the reference client has a great deal of test coverage,and deals with some tricky details very robustly. Using the RPC interface means that you can take advantage of reference client codefor things like network and peer connectivity, wallet management and signing,whilst still retaining the possibility to get down and dirty withsome lower level details such as raw transaction construction. Running the reference client as an RPC server I'm going to assume you have the bitcoin reference client (bitcoind) installed and set upand I'm not going to talk about issues such as 'bootstrapping' the client (to reduce initial block chain synchonisation times),as there should be plenty of other material available for these topics elsewhere on the web.(See this blog post , for example.) We'll need to run bitcoind as a server, which I do with the following command: ~/git/bitcoin/src $ ./bitcoind -printtoconsole This will start bitcoind as both a client (which connects to other nodes in the bitcoin network) and a local server (which you can connect to for RPC calls). If you don't have an rpc username and passw Continue reading >>

Bitcoin Cli Sendtoaddress - Grande Latex Iota

Bitcoin Cli Sendtoaddress - Grande Latex Iota

Bitcoin cli sendtoaddress - Grande latex iota ZCash CLI Help Bitcoin and Altcoins 19 . Bitcoin cli sendtoaddress showing invalid bitcoin address error 5. Sendrawtransactionhex string : Submits raw transactionserialized hex encoded) to local node network. address 2MsXaEmPZ8NSpepkKm9rxnxP6ezdtjxVx9W. minconf bitcoin cliregtest. 0. The limited inflation of the Bitcoin system s money supply is distributed evenlyby CPU power) throughout the network, not monopolized by banks. Build a Bitcoin Node cd bc2 elements src. bitcoin qt bitcoind. 0 also, i am trying bitcoin cliregtest createrawtransaction unconfirmed transaction 4 days. Bitcoin cliregtest sendtoaddress ADDRESS 10. This command will return a transaction ID. Chain Query: Bitcoin API: sendtoaddress Examples: bitcoin cli sendtoaddress1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0. Bitcoin Core: Bitcoin Core 0. Now, if you run bitcoin cliregtest getbalance. Copy these to your local machine add. Bitcoin cli settxfeeFEE. Bitcoin JSON RPC API blockchain. 01my first bitgo transaction. Bitcoin cli sendtoaddress. BTC Bitcoin ClockUpMemo : sendtoaddress listaccounts 1 sendtoaddress 0 koba1 bitcoin cli listaccounts. Hozzszlsok 4 . Bitcoin cli sendtoaddress. API referenceJSON RPC) Bitcoin. Process) You can use go ethereum to send commands to ethereum running on another host using this option rpcconnect 127. Inforpcport 443rpcsslrpcuser YourWalletIdentifierrpcpassword YourPassword getinfo. Shadow Documentation For some reason the Windows client will not start generatingthe Primecoin equivalent to Bitcoin shashing ) until you run a command in the debug window. We ll re use the same Solidity contract but we ll be creating invoking the contract using the Quantum command line tooli. 1 bitcoin cli sendtoaddress. Bitcoin clirpcport 19332 setwalle Continue reading >>

How To Use Bitcoin Rpc In Iguana

How To Use Bitcoin Rpc In Iguana

Bitcoin RPC calls can be issued using an Iguana instance with BTC active . Currently you can send them either 1.- Submitting the corresponding form in the SuperNET API page at The curl syntax for every call is described below, and responses are compared to the original Bitcoin RPC calls. For this document, Bitcoin RPC calls have been tested with Bitcoin Core 0.12.0. For Iguana calls, arguments are highlighted in upper case RED for required arguments and lower case red for optional arguments. The data string with the Iguana API call parameters is sent in JSON format, so every field using " quotes including string arguments requires them to be escaped as \". Returns the header hash of the most recent block on the best block chain. curl --url "--data "{\"coin\":\"BTC\",\"method\":\"getbestblockhash\"}" curl --url "--data "{\"coin\":\"BTC\",\"method\":\"getbestblockhash\"}" 000000000000000005795fb23e17158d23acb4e0312819f297b1b40c909b0d4a Gets a block with a particular header hash from the local database. curl --url "--data "{\"coin\":\"BTC\",\"method\":\"getblock\",\"params\":[HEIGHT, verbose, remoteonly]}" ./bitcoin-cli getblock 000000000000000004ec466ce4732fe6f1ed1cddc2ed4b328fff5224276e3f6f true {"hash": "000000000000000004ec466ce4732fe6f1ed1cddc2ed4b328fff5224276e3f6f", "confirmations":9267, "size":948994, "height":400000, "version":4, "merkleroot":"b0e8f88d4fb7cbc49ab49a3a43c368550e22a8e9e3e04b15e34240306a53aeec", "tx": [TXIDS ARRAY], "time":1456417484, "mediantime":1456415577, "nonce":657220870, "bits":"1806b99f", "difficulty":163491654908.9593, "chainwork":"000000000000000000000000000000000000000000122a24b77c62cd76004cde", "previousblockhash":"0000000000000000030034b661aed920a9bdf6bbfa6d2e7a021f78481882fa39", "nextblockhash":"000000000000000005421b1b2ee6d06d037557d7 Continue reading >>

Bitcoin-core

Bitcoin-core

A modern Bitcoin Core REST and RPC client to execute administrative tasks, wallet operations and queries about network and the blockchain. [agentOptions] (Object): Optional agent options to configure SSL/TLS. [headers=false] (boolean): Whether to return the response headers. [host=localhost] (string): The host to connect to. [logger=debugnyan('bitcoin-core')] (Function): Custom logger (by default, debugnyan). [password] (string): The RPC server user password. [port=[network]] (string): The RPC server port. [ssl] (boolean|Object): Whether to use SSL/TLS with strict checking (boolean) or an expanded config (Object). [ssl.enabled] (boolean): Whether to use SSL/TLS. [ssl.strict] (boolean): Whether to do strict SSL/TLS checking (certificate must match host). [timeout=30000] (number): How long until the request times out (ms). [username] (number): The RPC server user name. [version] (string): Which version to check methods for ( read more ). The network will automatically determine the port to connect to, just like the bitcoind and bitcoin-cli commands. constclient=newClient({network:'regtest'}); constclient=newClient({port:28332}); Connecting to an SSL/TLS server with strict checking enabled By default, when ssl is enabled, strict checking is implicitly enabled. //Awaitstylebasedonpromiseswithheadersenabled: const[body,headers]=awaitclient.getInfo(); Since version v0.14.0, it is possible to send commands via the JSON-RPC interface using named parameters instead of positional ones. This comes with the advantage of making the order of arguments irrelevant. It also helps improving the readability of certain function calls when leaving out arguments for their default value. For instance, take the getBalance() call written using positional arguments: constbalance=awaitnewClient( Continue reading >>

Bitcoin Core :: Bitcoin Core 0.14.0

Bitcoin Core :: Bitcoin Core 0.14.0

Bitcoin Core installation binaries can be downloaded from bitcoincore.org and the source-code is available from the Bitcoin Core source repository. Bitcoin Core version 0.14.0 is now available from: This is a new major version release, including new features, various bugfixesand performance improvements, as well as updated translations. Please report bugs using the issue tracker at github: Bitcoin Core is extensively tested on multiple operating systems usingthe Linux kernel, macOS 10.8+, and Windows Vista and later. Microsoft ended support for Windows XP on April 8th, 2014 ,No attempt is made to prevent installing or running the software on Windows XP, youcan still do so at your own risk but be aware that there are known instabilities and issues.Please do not report issues about Windows XP to the issue tracker. Bitcoin Core should also work on most other Unix-like systems but is notfrequently tested on them. Validation speed and network propagation performance have been greatlyimproved, leading to much shorter sync and initial block download times. The script signature cache has been reimplemented as a cuckoo cache,allowing for more signatures to be cached and faster lookups. Assumed-valid blocks have been introduced which allows script validation tobe skipped for ancestors of known-good blocks, without changing the securitymodel. See below for more details. In some cases, compact blocks are now relayed before being fully validated asper BIP152. P2P networking has been refactored with a focus on concurrency andthroughput. Network operations are no longer bottlenecked by validation. As aresult, block fetching is several times faster than previous releases in manycases. The UTXO cache now claims unused mempool memory. This speeds up initial blockdownload as UTXO lookups Continue reading >>

Does A Full Bitcoin Api Reference Exist With Examples?

Does A Full Bitcoin Api Reference Exist With Examples?

I know that all Bitcoin API methods are listed on the wiki: . However, some of the methods are very poorly documented. F.e. the lockunspent method is only documented as taking the parameters [array-of-objects]. No clue about what type of objects. And there are more examples like this. Is there a good API reference that specifies what parameters are expected and what result they give back? This would so much lower the bar for new developers! I hate to say this, but the source code is probably the ultimate reference. Tom van der Woerdt May 2 '13 at 21:15 Unfortunately more developers lend their time towards making new exchanges or arbitrage bots than actually making Bitcoin more useful. Those who put together Bitcoin.it did a wonderful job but there needs to be an updated spec sheet with examples as you outline in your question. bvpx Oct 22 '13 at 17:52 The 'help' RPC was improved a lot in 0.9.0 (you can currently download rc3). Parameter names, types and examples are now included. wumpus Mar 17 '14 at 16:12 @wumpus see my answer; rpc reference definitely improved Wizard Of Ozzie Sep 28 '14 at 11:34 I've used macros and pulled the full RPC documentation from Bitcoin Core 0.9.2.1 (rough formatting, help appreciated!) Full code won't fit here (80000 chars>30000 limit), but here's the help commands I entered and copied the returned data from: help addmultisigaddresshelp addnode help backupwallet help createmultisig help createrawtransaction help decoderawtransaction help decodescript help dumpprivkey help dumpwallet help getaccount help getaccountaddress help getaddednodeinfo help getaddressesbyaccount help getbalance help getbestblockhashhelp getblock help getblockchaininfohelp getblockcounthelp getblockhash help getblocktemplate help getconnectioncounthelp getdi Continue reading >>

Learning-bitcoin-from-the-command-line/bitcoin-cli-commands-help.md At Master Christophera/learning-bitcoin-from-the-command-line Github

Learning-bitcoin-from-the-command-line/bitcoin-cli-commands-help.md At Master Christophera/learning-bitcoin-from-the-command-line Github

Returns an object containing various state info. { "version": xxxxx, (numeric) the server version "protocolversion": xxxxx, (numeric) the protocol version "walletversion": xxxxx, (numeric) the wallet version "balance": xxxxxxx, (numeric) the total bitcoin balance of the wallet "blocks": xxxxxx, (numeric) the current number of blocks processed in the server "timeoffset": xxxxx, (numeric) the time offset "connections": xxxxx, (numeric) the number of connections "proxy": "host:port", (string, optional) the proxy used by the server "difficulty": xxxxxx, (numeric) the current difficulty "testnet": true|false, (boolean) if the server is using testnet or not "keypoololdest": xxxxxx, (numeric) the timestamp (seconds since Unix epoch) of the oldest pre-generated key in the key pool "keypoolsize": xxxx, (numeric) how many new keys are pre-generated "unlocked_until": ttt, (numeric) the timestamp in seconds since epoch (midnight Jan 1 1970 GMT) that the wallet is unlocked for transfers, or 0 if the wallet is locked "paytxfee": x.xxxx, (numeric) the transaction fee set in BTC/kB "relayfee": x.xxxx, (numeric) minimum relay fee for non-free transactions in BTC/kB "errors": "..." (string) any error messages} > bitcoin-cli getinfo> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' == Generating ==generate numblocks ( maxtries )generatetoaddress numblocks address (maxtries) == Mining ==getblocktemplate ( TemplateRequest )getmininginfogetnetworkhashps ( blocks height )prioritisetransaction submitblock "hexdata" ( "jsonparametersobject" ) == Network ==addnode "node" "add|remove|onetry"clearbanneddisconnectnode "node"getaddednodeinfo dummy ( "node" )getconnectioncountgetnettotalsgetnetworkinfogetpee Continue reading >>

More in cryptocurrency