From ad9ea4e2cd6b37df358491b7997bcbcff0aeb534 Mon Sep 17 00:00:00 2001 From: "J. Paul Daigle" Date: Tue, 7 Jul 2015 13:43:45 -0400 Subject: [PATCH] Update GUIDE.md There is always a formatting problem. --- GUIDE.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/GUIDE.md b/GUIDE.md index 4c9b240..94453f5 100644 --- a/GUIDE.md +++ b/GUIDE.md @@ -38,10 +38,11 @@ The BitPay client gem includes the BitPay KeyUtilities gem, which can be used to ### BitPay authentication BitPay authentication depends on four parts: + 1. An account on our servers. -2. A token shared between the client and the server. -3. A public key, shared between the client and the server. -4. A private key, held exclusively by the client. +1. A token shared between the client and the server. +1. A public key, shared between the client and the server. +1. A private key, held exclusively by the client. In order to complete authentication, you have to associate your private key with a token, and associate that token with an account. Once this authentication is complete, as long as you have the private key, you never have to authenticate again. The token you created will always be associated with that private key, so any time you create a new bitpay client object with that key, it is authenticated with BitPay. This is true whether you use the ruby-client, python client, or no client at all, the key is the important thing.