From 7d5328d51e163f8b916125d218119f8b807128bc Mon Sep 17 00:00:00 2001 From: "judymcconville@roadrunner.com" Date: Fri, 28 Apr 2017 09:13:49 -0700 Subject: [PATCH] Edited ch03.asciidoc with Atlas code editor --- ch03.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch03.asciidoc b/ch03.asciidoc index ad5878d2..6ff5b127 100644 --- a/ch03.asciidoc +++ b/ch03.asciidoc @@ -679,7 +679,7 @@ The block contains 419 transactions and the 64th transaction listed (+0627052b.. ==== Using Bitcoin Core's Programmatic Interface -((("Bitcoin Core", "Bitcoin Core API", "using programmatic interface")))The +bitcoin-cli+ helper is very useful for exploring the Bitcoin Core API and testing functions. But the whole point of an application programming interface is to access functions programmatically. In this section we will demonstrate accessing Bitcoin Core from another program. +((("Bitcoin Core", "Bitcoin Core API", "using programmatic interface")))((("programmatic interface")))The +bitcoin-cli+ helper is very useful for exploring the Bitcoin Core API and testing functions. But the whole point of an application programming interface is to access functions programmatically. In this section we will demonstrate accessing Bitcoin Core from another program. Bitcoin Core's API is a JSON-RPC interface. JSON stands for JavaScript Object Notation and it is a very convenient way to present data that both humans and programs can easily read. RPC stands for Remote Procedure Call, which means that we are calling procedures (functions) that are remote (on the Bitcoin Core node) via a network protocol. In this case, the network protocol is HTTP, or HTTPS (for encrypted connections).