feat(lnd): update lnd to v0.5-beta-6-g48d016bc

app/reducers/invoice.js

@@ -40,7 +40,7 @@ export const UPDATE_INVOICE = 'UPDATE_INVOICE'
 
 // Decorate invoice object with custom/computed properties.
 const decorateInvoice = invoice => {
-  invoice.finalAmount = invoice.amt_paid ? invoice.amt_paid : invoice.value
+  invoice.finalAmount = invoice.amt_paid_sat ? invoice.amt_paid_sat : invoice.value
   return invoice
 }
 

package.json

@@ -42,7 +42,7 @@
   "config": {
     "style_paths": "app/styles/*.scss app/components/**/*.scss",
     "lnd-binary": {
-      "binaryVersion": "0.5-beta-rc2-41-g4dd4f7cf",
+      "binaryVersion": "0.5-beta-6-g48d016bc",
       "binarySite": "https://github.com/LN-Zap/lnd/releases/download"
     }
   },

resources/lnd.conf

@@ -42,15 +42,23 @@
 
 ; Path to write the admin macaroon for lnd's RPC and REST services if it
 ; doesn't exist. This can be set if one wishes to store the admin macaroon in a
-; distinct location. By default, it is stored within lnd's main home directory.
-; Applications that are able to read this file, gains admin macaroon access
-; adminmacaroonpath=~/.lnd/admin.macaroon
+; distinct location. By default, it is stored within lnd's network directory.
+; Applications that are able to read this file, gain admin macaroon access.
+; adminmacaroonpath=~/.lnd/data/chain/bitcoin/simnet/admin.macaroon
 
 ; Path to write the read-only macaroon for lnd's RPC and REST services if it
 ; doesn't exist. This can be set if one wishes to store the read-only macaroon
 ; in a distinct location. The read only macaroon allows users which can read
-; the file to access RPCs which don't modify the state of the daemon.
-; readonlymacaroonpath=~/.lnd/readonly.macaroon
+; the file to access RPCs which don't modify the state of the daemon. By
+; default, it is stored within lnd's network directory.
+; readonlymacaroonpath=~/.lnd/data/chain/bitcoin/simnet/readonly.macaroon
+
+; Path to write the invoice macaroon for lnd's RPC and REST services if it
+; doesn't exist. This can be set if one wishes to store the invoice macaroon in
+; a distinct location. By default, it is stored within lnd's network directory.
+; The invoice macaroon allows users which can read the file to gain read and
+; write access to all invoice related RPCs.
+; invoicemacaroonpath=~/.lnd/data/chain/bitcoin/simnet/invoice.macaroon
 
 
 ; Specify the interfaces to listen on for p2p connections.  One listen
@@ -128,11 +136,6 @@ debuglevel=debug
 ; network.
 ; nobootstrap=1
 
-; If set, your wallet will be encrypted with the default passphrase. This isn't
-; recommend, as if an attacker gains access to your wallet file, they'll be able
-; to decrypt it. This value is ONLY to be used in testing environments.
-; noencryptwallet=1
-
 ; The alias your node will use, which can be up to 32 UTF-8 characters in
 ; length.
 ; alias=My Lightning ☇

resources/rpc.proto

@@ -1,4 +1,4 @@
-// Imported from https://github.com/lightningnetwork/lnd/blob/baee07ef480c15a731e0c87dc98d27269c5a80fa/lnrpc/rpc.proto
+// Imported from https://github.com/lightningnetwork/lnd/blob/48d016bc78e9f338742b10d936e52e7655fd8770/lnrpc/rpc.proto
 syntax = "proto3";
 
 // import "google/api/annotations.proto";
@@ -1670,15 +1670,28 @@ message Invoice {
     */
     uint64 settle_index = 17 [json_name = "settle_index"];
 
+    /// Deprecated, use amt_paid_sat or amt_paid_msat.
+    int64 amt_paid = 18 [json_name = "amt_paid", deprecated = true];
+
+    /**
+    The amount that was accepted for this invoice, in satoshis. This will ONLY
+    be set if this invoice has been settled. We provide this field as if the
+    invoice was created with a zero value, then we need to record what amount
+    was ultimately accepted. Additionally, it's possible that the sender paid
+    MORE that was specified in the original invoice. So we'll record that here
+    as well.
+    */
+    int64 amt_paid_sat = 19 [json_name = "amt_paid_sat"];
+
     /**
-    The amount that was accepted for this invoice. This will ONLY be set if
-    this invoice has been settled. We provide this field as if the invoice was
-    created with a zero value, then we need to record what amount was
-    ultimately accepted. Additionally, it's possible that the sender paid MORE
-    that was specified in the original invoice. So we'll record that here as
-    well.
+    The amount that was accepted for this invoice, in millisatoshis. This will
+    ONLY be set if this invoice has been settled. We provide this field as if
+    the invoice was created with a zero value, then we need to record what
+    amount was ultimately accepted. Additionally, it's possible that the sender
+    paid MORE that was specified in the original invoice. So we'll record that
+    here as well.
     */
-    int64 amt_paid = 18 [json_name = "amt_paid"];
+    int64 amt_paid_msat = 20 [json_name = "amt_paid_msat"];
 }
 message AddInvoiceResponse {
     bytes r_hash = 1 [json_name = "r_hash"];