mirror of
				https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git
				synced 2025-10-31 10:27:29 +00:00 
			
		
		
		
	Update 04_4__Interlude_Using_Curl.md
This commit is contained in:
		
							parent
							
								
									b31f033328
								
							
						
					
					
						commit
						8b6ebc0966
					
				| @ -220,7 +220,7 @@ This is almost exactly the same output that you receive when you type `bitcoin-c | |||||||
| 
 | 
 | ||||||
| After you know where your funds are, the next step in crafting a transaction is to get a change address. By now you've probably got the hang of this, and you know that for simple RPC commands, all you need to do is adjust the `method` is the `curl` command: | After you know where your funds are, the next step in crafting a transaction is to get a change address. By now you've probably got the hang of this, and you know that for simple RPC commands, all you need to do is adjust the `method` is the `curl` command: | ||||||
| ``` | ``` | ||||||
| $ curl --user StandUp:8eaf562eaf45c33c3328bc66008f2dd1 --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnewaddress", "params": ["", "legacy"] }' -H 'content-type: text/plain;' http://127.0.0.1:18332/ | jq -r '.' | $ curl --user StandUp:8eaf562eaf45c33c3328bc66008f2dd1 --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getrawchangeaddress", "params": ["legacy"] }' -H 'content-type: text/plain;' http://127.0.0.1:18332/ | jq -r '.' | ||||||
| { | { | ||||||
|   "result": "mrSqN37TPs89GcidSZTvXmMzjxoJZ6RKoz", |   "result": "mrSqN37TPs89GcidSZTvXmMzjxoJZ6RKoz", | ||||||
|   "error": null, |   "error": null, | ||||||
| @ -228,11 +228,11 @@ $ curl --user StandUp:8eaf562eaf45c33c3328bc66008f2dd1 --data-binary '{"jsonrpc" | |||||||
| } | } | ||||||
| ``` | ``` | ||||||
| 
 | 
 | ||||||
| > **WARNING:** The parameters order is important when you are sending RPC commands using curl. For example here, if we had sent `"params": ["legacy"]` instead of `"params": ["", "legacy"]`, we would get a `bech32` address with a label of `"legacy"` instead of a `legacy` address, so pay attention to the order. | > **WARNING:** The parameters order is important when you are sending RPC commands using curl. There's only one argument for `getrawchangeaddress`, but consider its close cousin `getnewaddress`. That takes two arguments: first label, then type. If we sent that same `"params": ["legacy"]` instead of `"params": ["", "legacy"]`, we would get a `bech32` address with a label of `"legacy"` instead of a `legacy` address, so pay attention to the order! | ||||||
| 
 | 
 | ||||||
| At this point, we can even revert to our standard practice of saving results to variables with additional help from `jq`: | At this point, we can even revert to our standard practice of saving results to variables with additional help from `jq`: | ||||||
| ``` | ``` | ||||||
| $ newaddress=$(curl --user StandUp:8eaf562eaf45c33c3328bc66008f2dd1 --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnewaddress", "params": ["", "legacy"] }' -H 'content-type: text/plain;' http://127.0.0.1:18332/ | jq -r '.result') | $ newaddress=$(curl --user StandUp:8eaf562eaf45c33c3328bc66008f2dd1 --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getrawchangeaddress", "params": ["legacy"] }' -H 'content-type: text/plain;' http://127.0.0.1:18332/ | jq -r '.result') | ||||||
| $ echo $newaddress | $ echo $newaddress | ||||||
| mqdfnjgWr2r3sCCeuTDfe8fJ1CnycF2e6R | mqdfnjgWr2r3sCCeuTDfe8fJ1CnycF2e6R | ||||||
| ``` | ``` | ||||||
| @ -240,7 +240,7 @@ No need to worry about the downloading info. It'll go to `STDERR` and be display | |||||||
| 
 | 
 | ||||||
| ## Create a Transaction | ## Create a Transaction | ||||||
| 
 | 
 | ||||||
| You're now ready to create a transaction with `curl`, except using `getrawchangeaddress` instead of `getnewaddress`. | You're now ready to create a transaction with `curl`. | ||||||
| 
 | 
 | ||||||
| ### Ready Your Variables | ### Ready Your Variables | ||||||
| 
 | 
 | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user