diff --git a/resources/apps/lnd/0.13.3/hash.bin b/resources/apps/lnd/0.13.3/hash.bin new file mode 100644 index 0000000..222152d --- /dev/null +++ b/resources/apps/lnd/0.13.3/hash.bin @@ -0,0 +1 @@ +PFLZO3TPFC57UTPBE3NKBLOTBRHSZH4DMNYQNX4FEQ54XCC6OB3R3UZEAS62ZLPNVRVNPRE2Z67O6NW4NHV2NEP5NPJ2FTDVHNJZFMY diff --git a/resources/apps/lnd/0.13.3/icon.png b/resources/apps/lnd/0.13.3/icon.png new file mode 100644 index 0000000..ccd8087 Binary files /dev/null and b/resources/apps/lnd/0.13.3/icon.png differ diff --git a/resources/apps/lnd/0.13.3/instructions.md b/resources/apps/lnd/0.13.3/instructions.md new file mode 100644 index 0000000..16c0e75 --- /dev/null +++ b/resources/apps/lnd/0.13.3/instructions.md @@ -0,0 +1,52 @@ +# Lightning Network Daemon (LND) + +## Dependencies + +LND on the Embassy requires a full archival Bitcoin node to function. Since your Embassy Bitcoin node is pruned by default, an additional service, Bitcoin Proxy, is also required. + +## LND Config + +Your LND node is highly configurable. Many settings are considered _advanced_ and should be used with caution. For the vast majority of users and use-cases, we recommend using the defaults. Once configured, you may start your node! + +## Bitcoin Proxy Config + +On the LND page, scroll down to find the Bitcoin Proxy dependency. Click `Configure`. This will automatically configure Bitcoin Proxy to satisfy LND. + +# Lightning Usage Guide + +## Using a Wallet + +Enter your LND-Connect QR code (located in `properties`) into any wallet that supports connecting to a remote LND node over Tor. For a list of compatible wallets, see https://github.com/start9labs/lnd-wrapper/blob/master/docs/wallets.md. + +## Getting On-Chain Funds + +Before you can open and channel and start transacting on the Lightning network, you need some Bitcoin stored on your LND node. Be advised, Bitcoin funds that you transfer to your LND node are hot, meaning, the are stored directly on your Embassy. There is no way to use cold storage when using Lightning, which is why people call it reckless. For this reason, it is usually unwise to move large amounts of Bitcoin to your LND node. That said, you don't want to move a tiny amount either, since that would limit your purchasing power on the Lightning network. We recommend moving about 500,000-5,000,000 satoshis, or .005-.05 Bitcoin, which at current (May 7, 2021) prices is about $250-$2,500. This gives you a solid amount of purchasing power, but hopefully wouldn't ruin your life if something were to go terribly wrong. If you feel comfortable using more Bitcoin, then by all means, go for it. + +## Depositing to LND + +When using LND or any wallet that is connected to LND it is important to note that until "Synced to Chain" in the Properties page is reporting ✅, your deposits to your LND on-chain wallet may not appear. + +## Opening a Channel and Getting Outbound Liquidity + +Once your LND node is synced, it's time to open a channel. Opening a channel with a well-connected node is how you get connected to the rest of the network, and it immediately grants you outbound liquidity. Meaning, you will be able to send money to others. Unless you are planning to become a Lightning Service Provider, you do not want to open more than a couple of channels at most. Managing many channels is difficult, it can be quite expensive, and unless you plan to devote significant resources in the form of time and Bitcoin, there is no profit in it. If your goal is to use Lightning to benefit from instant and near-free transactions, you only need 2-3 good channels. + +If you are looking for destinations for your first channel, we suggest you open a channel with the [Start9 HQ](025d28dc4c4f5ce4194c31c3109129cd741fafc1ff2f6ea53f97de2f58877b2295@64.225.19.231:9735) node, which is already very well connected. + +It is not recommended to open a channel less than 100,000 satoshi, or .001 BTC, or $50 USD in today's prices. Anything less, and it's possible that the cost to open and close the channel might approach the size of the channel itself. The bigger the channel you open, the more outbound liquidity you will have, which means you have more spending power on the network. In this tutorial, we are going to open a channel of 2,000,000 satoshi. When opening a channel with Start9 HQ, we ask that you make it a private channel, meaning it will not display publicly on network graph. The reason for this is that unless you plan to be a very active Lightning Node Operator, having public channels decreases not only the reliability of your node but also hurts Start9's ability to route payments for you. If you do intend to be a serious node operator, we require that your channel be for a minimum of 5,000,000 sats. Please contact us in one of our community channels for further details. + +## Getting Inbound Liquidity + +If you want to receive payments, you will need some inbound liquidity. + +The first, easiest, and best way to get inbound liquidity is to use your outbound liquidity to buy something. Any Bitcoin you spend using your outbound liquidity is Bitcoin you can now receive back. So if there is something you want to buy, like a Start9 Embassy or a t-shirt from the Start9 store, simply make the purchase, and you will then have inbound liquidity equal to the amount of Satoshis you spend. + +Option 2 is to personally ask Start9 for an invoice for however much inbound liquity you want. Then you send Bitcoin to the invoice, and in turn we will transfer fiat currency to you equal to the amount of the Bitcoin you send us. In other words, Start9 will buy some Bitcoin from you at market rate, such that you then have inbound liquidity. In either case, you are spending or selling some Bitcoin. + +The only way to get inbound liquidity without spending or selling Bitcoin is to convince someone to open a channel with you, just as you opened a channel with Start9 HQ. This may be a difficult task, since there is not much incentive for someone to open a channel with you unless you are also very well connected. Also, you will need to make sure that they too, are well connected with plenty of inbound liquidity, or else your inbound liquidity with them will not really matter. In other words, they might be the only person capable of paying you. + +So options 1 or 2 are best. Use your Lightning node's outbound liquidity to either purchase something or sell some Bitcoin. Now, you can pay and get paid using Lightning in an amount equal to your outbound and inbound liquidity. + +## Sending payments over Lightning + +Once you have open channels and are ready to transact on the Lightning Network, it is important to note that until "Synced to Graph" in the Properties page is reporting ✅, you may experience problems finding routes to your destination. + diff --git a/resources/apps/lnd/0.13.3/license.md b/resources/apps/lnd/0.13.3/license.md new file mode 100644 index 0000000..70f1f0d --- /dev/null +++ b/resources/apps/lnd/0.13.3/license.md @@ -0,0 +1,19 @@ +Copyright (C) 2015-2018 Lightning Labs and The Lightning Network Developers + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. diff --git a/resources/apps/lnd/0.13.3/manifest.json b/resources/apps/lnd/0.13.3/manifest.json new file mode 100644 index 0000000..3a465de --- /dev/null +++ b/resources/apps/lnd/0.13.3/manifest.json @@ -0,0 +1,348 @@ +{ + "id": "lnd", + "title": "Lightning Network Daemon", + "version": "0.13.3", + "description": { + "short": "A complete implementation of a Lightning Network node by Lightning Labs", + "long": "LND fully conforms to the Lightning Network specification (BOLTs). BOLT stands for: Basis of Lightning Technology. In the current state lnd is capable of: creating channels, closing channels, managing all channel states (including the exceptional ones!), maintaining a fully authenticated+validated channel graph, performing path finding within the network, passively forwarding incoming payments, sending outgoing onion-encrypted payments through the network, updating advertised fee schedules, and automatic channel management (autopilot).\n" + }, + "assets": { + "license": "LICENSE", + "instructions": "instructions.md", + "icon": "icon.png", + "docker-images": "image.tar", + "assets": null + }, + "build": [ + "make" + ], + "release-notes": "Upgrade to EmbassyOS v0.3.0", + "license": "mit", + "wrapper-repo": "https://github.com/Start9Labs/lnd-wrapper", + "upstream-repo": "https://github.com/lightningnetwork/lnd", + "support-site": "https://lightning.engineering/slack.html", + "marketing-site": "https://lightning.engineering/", + "donation-url": null, + "alerts": { + "install": "READ CAREFULLY! LND and the Lightning Network are considered beta software. Please use with caution and do not risk more money than you are willing to lose. We encourage frequent backups. If for any reason, you need to restore LND from a backup, your on-chain wallet will be restored, but all your channels will be closed and their funds returned to your on-chain wallet, minus fees. It may also take some time for this process to occur.\n", + "uninstall": "READ CAREFULLY! Uninstalling LND will result in permanent loss of data, including its private keys for its on-chain wallet and all channel states. Please make a backup if you have any funds in your on-chain wallet or in any channels. Recovering from backup will restore your on-chain wallet, but due to the architecture of the Lightning Network, your channels cannot be recovered. All your channels will be closed and their funds returned to your on-chain wallet, minus fees. \n", + "restore": "Restoring LND will overwrite its current data, including its on-chain wallet and channels. Any channels opened since the last backup will be forgotten and may linger indefinitely, and channels contained in the backup will be closed and their funds returned to your on-chain wallet, minus fees.\n", + "start": null, + "stop": null + }, + "main": { + "type": "docker", + "image": "main", + "system": false, + "entrypoint": "docker_entrypoint.sh", + "args": [], + "mounts": { + "bitcoind": "/mnt/bitcoind", + "btc-rpc-proxy": "/mnt/btc-rpc-proxy", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + }, + "health-checks": { + "synced": { + "type": "docker", + "image": "main", + "system": false, + "entrypoint": "health-check", + "args": [], + "mounts": {}, + "io-format": "yaml", + "inject": true, + "shm-size-mb": null, + "critical": false + } + }, + "config": { + "get": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "config", + "get", + "/root/.lnd", + "/mnt/assets/config_spec.yaml" + ], + "mounts": { + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + }, + "set": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "config", + "set", + "lnd", + "/root/.lnd", + "/mnt/assets/config_rules.yaml" + ], + "mounts": { + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + } + }, + "properties": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "properties", + "/root/.lnd" + ], + "mounts": { + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + }, + "volumes": { + "bitcoind": { + "type": "pointer", + "package-id": "bitcoind", + "volume-id": "main", + "path": "/root", + "readonly": true + }, + "btc-rpc-proxy": { + "type": "pointer", + "package-id": "btc-rpc-proxy", + "volume-id": "main", + "path": "/root", + "readonly": false + }, + "certificates": { + "type": "certificate", + "interface-id": "control" + }, + "compat": { + "type": "assets" + }, + "main": { + "type": "data" + } + }, + "min-os-version": "0.3.0", + "interfaces": { + "control": { + "name": "Control Interface", + "description": "Specifies the interfaces to listen on for RPC and REST connections.", + "tor-config": { + "port-mapping": { + "8080": "8080", + "10009": "10009" + } + }, + "lan-config": null, + "ui": false, + "protocols": [ + "tcp", + "http", + "grpc" + ] + }, + "peer": { + "name": "Peer Interface", + "description": "Specifies the interfaces to listen on for p2p connections.", + "tor-config": { + "port-mapping": { + "9735": "9735" + } + }, + "lan-config": null, + "ui": false, + "protocols": [ + "tcp", + "http" + ] + }, + "watchtower": { + "name": "Watchtower Interface", + "description": "Specifies the interfaces to listen on for watchtower client connections.", + "tor-config": { + "port-mapping": { + "9911": "9911" + } + }, + "lan-config": null, + "ui": false, + "protocols": [ + "tcp", + "grpc" + ] + } + }, + "backup": { + "create": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "duplicity", + "create", + "/mnt/backup", + "/root/.lnd" + ], + "mounts": { + "BACKUP": "/mnt/backup", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + }, + "restore": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "/mnt/assets/backup-restore.sh", + "args": [ + "duplicity", + "restore", + "/mnt/backup", + "/root/.lnd" + ], + "mounts": { + "BACKUP": "/mnt/backup", + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + } + }, + "migrations": { + "from": {}, + "to": {} + }, + "actions": {}, + "dependencies": { + "bitcoind": { + "version": ">=0.21.1.2 <0.22.0", + "requirement": { + "type": "opt-out", + "how": "Can alternatively configure an external bitcoin node." + }, + "description": "Used to subscribe to new block events.", + "critical": true, + "config": { + "check": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "dependency", + "check", + "lnd", + "bitcoind", + "/root/.lnd", + "/mnt/assets/bitcoind_config_rules.yaml" + ], + "mounts": { + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": null, + "inject": false, + "shm-size-mb": null + }, + "auto-configure": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "dependency", + "auto-configure", + "lnd", + "bitcoind", + "/root/.lnd", + "/mnt/assets/bitcoind_config_rules.yaml" + ], + "mounts": { + "compat": "/mnt/assets" + }, + "io-format": null, + "inject": false, + "shm-size-mb": null + } + } + }, + "btc-rpc-proxy": { + "version": ">=0.3.2.1 <0.4.0", + "requirement": { + "type": "opt-out", + "how": "Can alternatively use the internal full archival bitcoind node or configure an external bitcoin node." + }, + "description": "Used to fetch validated blocks.", + "critical": false, + "config": { + "check": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "dependency", + "check", + "lnd", + "btc-rpc-proxy", + "/root/.lnd", + "/mnt/assets/btc-rpc-proxy_config_rules.yaml" + ], + "mounts": { + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + }, + "auto-configure": { + "type": "docker", + "image": "compat", + "system": true, + "entrypoint": "compat", + "args": [ + "dependency", + "auto-configure", + "lnd", + "btc-rpc-proxy", + "/root/.lnd", + "/mnt/assets/btc-rpc-proxy_config_rules.yaml" + ], + "mounts": { + "compat": "/mnt/assets", + "main": "/root/.lnd" + }, + "io-format": "yaml", + "inject": false, + "shm-size-mb": null + } + } + } + } +} \ No newline at end of file