From ed59519fa73c239ced79968c1b08931015a47e4a Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 11 Aug 2020 08:05:39 -1000 Subject: [PATCH] Update 16_0_Programming_with_Libwally.md --- 16_0_Programming_with_Libwally.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16_0_Programming_with_Libwally.md b/16_0_Programming_with_Libwally.md index a02b48a..f608001 100644 --- a/16_0_Programming_with_Libwally.md +++ b/16_0_Programming_with_Libwally.md @@ -2,7 +2,7 @@ The previous chapter presented three C Libraries, for RPC, JSON, and ZMQ, all of which are intended to interact directly with `bitcoind`, just like you've been doing since the start. But, sometimes you might want to code without direct access to a `bitcoind`. This might be due to an offline client, or just because you want to keep some functionality internal to your C program. You also might want to get into deeper wallet functionality, like cryptography or address derivation. That's where Libwally comes in: it's a wallet library for C, C++, Java, NodeJS, or Python, with wrappers also available for other languages, such as Swift. -This chapter touches upon the functionality possible within Libwally, most of which complements the work you've done through RPC access to `bitcoind`, but some of which replicates it. Obviously, this could be used with all three of the libraries from the previous chapter, and together they can create a strong basis for your C programming of Bitcoin. +This chapter touches upon the functionality possible within Libwally, most of which complements the work you've done through RPC access to `bitcoind`, but some of which replicates it. Obviously, this could be used with all three of the libraries from the previous chapter (and generally with a `bitcoind`), and together they can create a strong basis for your C programming of Bitcoin. ## Objectives for This Chapter