From f1d35d9b041ce6fc2e49aa6ff944b31b524398cf Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 4 Aug 2020 14:46:23 -1000 Subject: [PATCH] Update 04_4__Interlude_Using_Curl.md --- 04_4__Interlude_Using_Curl.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/04_4__Interlude_Using_Curl.md b/04_4__Interlude_Using_Curl.md index fb89940..0e7c644 100644 --- a/04_4__Interlude_Using_Curl.md +++ b/04_4__Interlude_Using_Curl.md @@ -308,3 +308,7 @@ Having finished this section, you may feel that accessing `bitcoind` via `curl` But there are still reasons you'd use `curl` instead of `bitcoin-cli`: _What is the power of curl?_ Most obviously, `curl` takes out one level of indirection. Instead of working with `bitcoin-cli` which sends RPC commands to `bitcoind`, you're sending those RPC commands directly. This allows for more robust programming, because you don't have to worry about what unexpected things that `bitcoin-cli` might do or how it might change over time. However, you're also taking your first steps toward using a more comprehensive programming language than the poor options offered by a shell script. As you'll see in the last few chapters of this, you might actually see curl libraries are other functions to access the RPC commands in a variety of programming languages: but that's still a long ways away. + +## What's Next? + +Learn one more way to "Send Bitcoin Transactions" with [ยง4.5 Sending Coins with Automated Raw Transactions](04_5_Sending_Coins_with_Automated_Raw_Transactions.md).