mirror of
https://github.com/Start9Labs/documentation.git
synced 2026-03-26 10:21:53 +00:00
Merge branch 'master' of github.com:Start9Labs/documentation
This commit is contained in:
BIN
source/_static/images/tor/install_homebrew.png
Normal file
BIN
source/_static/images/tor/install_homebrew.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 411 KiB |
BIN
source/_static/images/tor/install_homebrew1.png
Normal file
BIN
source/_static/images/tor/install_homebrew1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 567 KiB |
BIN
source/_static/images/tor/install_tor.png
Normal file
BIN
source/_static/images/tor/install_tor.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
@@ -4,10 +4,12 @@
|
||||
Running Tor on Linux
|
||||
********************
|
||||
|
||||
For Debian and Debian-based systems, such as Ubuntu, Mint, etc.
|
||||
|
||||
#. Install the Tor proxy service to your system. To do so, open your terminal and run the following command:
|
||||
|
||||
.. code-block::
|
||||
|
||||
sudo apt update && sudo apt install tor
|
||||
|
||||
#. That's it! Your Linux machine is now setup to natively use Tor.
|
||||
#. That's it! Your Linux machine is now setup to natively use Tor.
|
||||
|
||||
@@ -4,36 +4,102 @@
|
||||
Running Tor on MacOS
|
||||
********************
|
||||
|
||||
#. First, you need to install the Tor proxy service to your system. This will require opening your Terminal.
|
||||
Install Homebrew
|
||||
================
|
||||
|
||||
#. To open your terminal, hold the command key ⌘ + spacebar. `Spotlight Search` will appear. Start typing "terminal" and select the program called `Terminal`.
|
||||
For macOS running on ARM chips (ie. newer macs):
|
||||
------------------------------------------------
|
||||
|
||||
#. Paste in the following commands and hit <Enter>.
|
||||
.. warning:: macOS Homebrew running natively on M1/Apple Silicon/ARM has partial functionality. Therefore, some additional steps are needed to setup Homebrew.
|
||||
|
||||
.. code-block::
|
||||
#. Open a command line editor (Terminal), and run the following commands:
|
||||
|
||||
.. code-block::
|
||||
|
||||
softwareupdate --install-rosetta
|
||||
arch -x86_64 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
|
||||
|
||||
#. Use this command to install packages:
|
||||
|
||||
.. code-block::
|
||||
|
||||
arch -x86_64 brew install <package>
|
||||
|
||||
For macOS Big Sur/Catalina:
|
||||
---------------------------
|
||||
|
||||
1. If you do not have Homebrew installed, follow the installation instructions `here <https://brew.sh/>`_.
|
||||
|
||||
TLDR: Open the command line editor (Terminal) and paste the following line:
|
||||
|
||||
.. code-block::
|
||||
|
||||
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
|
||||
|
||||
2. You will be prompted for your system password before installation; proceed with entering your password:
|
||||
|
||||
.. figure:: /_static/images/tor/install_homebrew.png
|
||||
:width: 80%
|
||||
:alt: Homebrew installation
|
||||
|
||||
Enter your password
|
||||
|
||||
3. You will be notified which directories Homebrew is going to create, hit :code:`RETURN`:
|
||||
|
||||
.. figure:: /_static/images/tor/install_homebrew1.png
|
||||
:width: 80%
|
||||
:alt: Homebrew installation
|
||||
|
||||
Homebrew creates the directories and downloads any other files it needs e.g. “Command Line Tool for Xcode” and “Homebrew”.
|
||||
|
||||
Wait a few minutes while it downloads and installs what it needs.
|
||||
|
||||
.. warning:: Surprisingly, Homebrew uses Google Analytics to collect anonymous usage data. You can deselect the option to share usage data by `opting out <https://docs.brew.sh/Analytics#opting-out>`_.
|
||||
|
||||
Install Tor
|
||||
===========
|
||||
|
||||
.. warning:: If you have the Tor Browser open, close it and quit the application.
|
||||
|
||||
For macOS with ARM chips
|
||||
------------------------
|
||||
|
||||
In the command line type:
|
||||
|
||||
.. code-block::
|
||||
|
||||
arch -x86_64 brew install tor
|
||||
|
||||
For macOS Big Sur/Catalina:
|
||||
---------------------------
|
||||
|
||||
In the command line type:
|
||||
|
||||
.. code-block::
|
||||
|
||||
brew install tor
|
||||
|
||||
|
||||
See the `Tor Project <https://2019.www.torproject.org/docs/tor-doc-osx.html.en>`_ for more details.
|
||||
|
||||
Once it is finished you have the following options:
|
||||
|
||||
.. figure:: /_static/images/tor/install_tor.png
|
||||
:width: 80%
|
||||
:alt: Tor installation
|
||||
|
||||
Install Tor
|
||||
|
||||
In the command line type
|
||||
|
||||
.. code-block::
|
||||
|
||||
which brew || /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
|
||||
brew install tor
|
||||
brew services start tor
|
||||
|
||||
#. When this completes, you should see something like:
|
||||
or
|
||||
|
||||
.. code-block::
|
||||
.. code-block::
|
||||
|
||||
==> Successfully started `tor` (label: homebrew.mxcl.tor)
|
||||
arch -x86_64 services start tor
|
||||
|
||||
#. If you notice issues connecting to Tor websites, try restarting the Tor service. Open the terminal and run:
|
||||
|
||||
.. code-block::
|
||||
|
||||
brew services restart tor
|
||||
|
||||
#. After running this command, you should see something like:
|
||||
|
||||
.. code-block::
|
||||
|
||||
Stopping `tor`... (might take a while)
|
||||
==> Successfully stopped `tor` (label: homebrew.mxcl.tor)
|
||||
==> Successfully started `tor` (label: homebrew.mxcl.tor)
|
||||
|
||||
#. That's it! Your Mac is now setup to natively use Tor.
|
||||
depending on your device (as explained above). This will start Tor and ensure that it is always running, even after a restart.
|
||||
|
||||
@@ -6,6 +6,24 @@ Concepts
|
||||
|
||||
Depending on your background, the Embassy platform may deal with some unfamiliar concepts. While it is not strictly *necessary* for you to understand these concepts to use your Embassy, we know many of you would like to.
|
||||
|
||||
|
||||
.. _start9:
|
||||
|
||||
"The Origin of “Start9”
|
||||
=======================
|
||||
|
||||
Pokemon is a game for Gameboy. Twitch is a live video streaming app. “Twitch Plays Pokemon” was a popular phenomenon where Twitch users would collaborate to play a SHARED game of Pokemon on Gameboy. Here’s how it worked:
|
||||
|
||||
Participants would use the Twitch message board to enter commands that then got executed in the gameplay. For example, if someone entered the command "right”, that would cause the player to move 1 space to the right. Commands would execute immediately after they were received, and anyone could enter a valid command at any time. You can think of Twitch Plays Pokemon as the more practical equivalent of placing a Gameboy in the middle of a crowded room and telling everyone to push buttons at the same time. As you might expect, the gameplay of Twitch Plays Pokemon was quite “twitchy”, but in a very "infinite monkey theory" way, progress could eventually be made.
|
||||
|
||||
In an effort to streamline play, a new game mode was devised in which players would “vote” for the next command and, every 4 seconds, whatever command received the most votes over the previous 4 seconds would execute in the game. Also introduced in this mode was the ability to attach multipliers to a command, such that the command would execute that number of times. For example, “right2” would cause the player to move 2 spaces to the right. “right3” would cause the player to move 3 spaces to the right, and so on. The highest number any participant could place after a command was 9, meaning whatever command they entered would execute 9 times. As you might expect, gameplay in this mode was less chaotic, more efficient, but it also meant each participant had less direct and immediate influence over the game. If a group of even 5-10 got together and colluded on their votes, they could practically take over the game and make contrarian ideas irrelevant. The new game mode was called “Democracy”, and the original game mode became known as “Anarchy”. Which game mode was engaged was itself governed by a democratic process: if more participants wanted to play in Democracy mode, then Democracy mode engaged; if more wanted to play in Anarchy mode, then Anarchy mode engaged.
|
||||
|
||||
To summarize: in Anarchy mode, everyone had equal influence over the game, but progress was slow and clunky. In Democracy mode, progress was fast and efficient, but colluding groups could marginalize individual participants and ruin the game for them.
|
||||
|
||||
So…individual participants discovered a means of effective protest whenever Democracy mode became suffocating, but they could not garner enough votes to switch back to Anarchy mode. Someone would type the command “start9” into the comments. This command meant “open the start menu 9 times in a row”, which, as you might imagine, would be enormously disruptive if executed. The entire screen would be blocked by the start menu, over and over. Typing “start9” was a participant’s way of signaling to other participants that they felt marginalized by Democracy mode, and they were ready to fight back. If others felt the same, they could also begin typing “start9” - then, sure enough, “start9” would finally receive more votes than the colluding group’s command, and the menu opening would begin. Every 4 seconds, the menu would open 9 times…again, and again, and again…until finally, the colluding group would be forced to either cooperate in reverting the game mode back to Anarchy mode or quit altogether.
|
||||
|
||||
Playing in Anarchy mode was impractical, but neither did people want to play a game where they had no voice, where a group of insiders had taken total control. And so “start9” became the battle cry of the individual, the out-group, a means of signaling to other individuals that it was time to fight back against the usurpers - to use their own rules against them, until there was
|
||||
|
||||
.. _embassy:
|
||||
|
||||
Embassy
|
||||
@@ -24,6 +42,10 @@ When you see your credit card information on your banking app, your messages in
|
||||
|
||||
One thing is for certain though: if you control your server, then you control your data. Your finances, your communications, all of it is actually yours -- and only yours -- with an Embassy.
|
||||
|
||||
Why do I care?
|
||||
=================
|
||||
As an example, let's talk about the password manager, Bitwarden. It may help convey the concept of a personal server. Currently, when you use Bitwarden, your passwords are stored on a physical device (aka server) owned and operated by the Bitwarden team. Your phone or laptop sends requests to their server when you want to do anything: create an account, create a new password, retrieve existing passwords, etc. Your passwords are stored on their device, encrypted with your Bitwarden password. They are the custodian of your passwords, similar to getting a safe deposit box at the bank. The bank keeps your valuables in their vault, presumably they don't know what's in the box, and any time you want access to your box, you ask the bank for permission. This is exactly how a hosted Bitwarden experience works, as well as just about everything on the internet. When you install Bitwarden on your Embassy, by contrast, it's like building your own safe deposit box in a private bunker whose location is only known to you and whose keys only you posses. You create an account with yourself, store your passwords with yourself, etc. You are your own custodian. This same concept can be applied to just about everything on the Internet, without losing the convenience of the custodial model, which is what we are out to accomplish. This may sound cool, or neat, but it is so much more than that. The custodial data model is amongst the greatest threats to human liberty the world has ever seen.
|
||||
|
||||
How does the Embassy work?
|
||||
==========================
|
||||
|
||||
@@ -139,4 +161,17 @@ Bitcoin Full Node
|
||||
|
||||
The Embassy runs a Bitcoin Full Node. When most people say "full node" what they mean (or should mean) is "fully validating node", meaning that the node is capable of enforcing the consensus rules of Bitcoin by accepting, validating, and relaying every transaction and block produced by the network. Fully validating nodes are necessary for Bitcoin to exist and function properly and are what protect the network from attackers attempting to bypass the consensus rules. A fully validating node (aka full node) does not need to store the entire blockchain to accomplish this. A node that stores the entire blockchain is called a "full archival node". It is the same as a full node, except that it stores every single valid transaction and block ever produced by the network. There are not many reasons why an individual would want to run a full archival node. Most of the benefits of node operatorship are encompassed by a basic full node described above. Full archival nodes have the added benefit of enabling a block explorer. For instace, if you were interested in looking up the history of a particular address or viewing the details of a transaction, neither of which were your own. If an address or transaction is your own, you can view those details using a pruned node.
|
||||
|
||||
All that said, it will soon be possible to run a full archival node with he embassy, should you determine you want block explorer functionality. This will require plugging in an external hard drive to the embassy and changing a setting in the app, and also a resycnhing of the blockchain from genesis.
|
||||
All that said, it will soon be possible to run a full archival node with he embassy, should you determine you want block explorer functionality. This will require plugging in an external hard drive to the embassy and changing a setting in the app, and also a resycnhing of the blockchain from genesis.
|
||||
|
||||
Bitcoin wallets
|
||||
===============
|
||||
|
||||
The word "wallet" has come to mean a lot of things, depending on who you ask and what software you are using. There are (1) software "wallets", (2) hardware "wallets", (3) seed "wallets", and (4) branch "wallets". The one thing all these wallets have in common is that they have almost nothing in common. As the terms are used today, here is usually what they mean.
|
||||
|
||||
(1) SOFTWARE WALLETS - (such as FullyNoded and Specter) Software applications capable of interfacing with hardware wallets (see below), interfacing with one or more nodes, as well as address creation, transaction creation, transaction broadcasting, and transaction display. Most software wallets are also capable of creating and storing public/private keypairs, granting them properties of both hardware wallets (see below) and seed wallets (see below). When we say "wallet", we are referring to software applications that posses a user interface for interacting with the Bitcoin network. If a wallet is capable of creating, storing and using private keys, it should be referred to as just a wallet with signer ability.
|
||||
|
||||
(2) HARDWARE WALLETS – (such as ColdCard and Trezor) Physical devices that create and store public/private keypairs, exporting the public keys, NEVER exporting the private keys, and using the private keys to sign transactions on demand. Hardware wallets must interface with a software wallet in order to be useful to a user. For this reason, some have proposed renaming hardware wallets to "hardware signers" for clarity.
|
||||
|
||||
(3) SEED WALLETS - Basically just the root of a hierarchical deterministic tree of keypairs. It usually takes the form of a mnemonic phrase of 12 or 24 words. Why people refer to their mnemonic seed as a "wallet" is confusing. Just call it a seed.
|
||||
|
||||
(4) BRANCH WALLETS - This is how Specter uses the word wallet, and it is causing a lot of confusion. Whenever you create a new "wallet" in specter, you are actually creating a new hierarchical deterministic branch of your mnemonic seed - or in the case of multisig, multiple seeds. The branch you create can be based on "purpose" (segwit, non-segwit, single-sig, multi-sig, etc), "coin type" (Bitcoin, Doegecoin, etc), or "account" (for personal accounting). Change any of these parameters, and you have yourself a new wallet, which again is just a different branch of the same mnemonic seed that potentially abides by a different set of rules. Perhaps a better name for this concept is "bank". Instead of "wallets", you should be able to create different "banks" from your seed.
|
||||
|
||||
@@ -32,6 +32,28 @@ Does the Embassy have international electrical plugs?
|
||||
-----------------------------------------------------
|
||||
Power supplies for EU, AU, US, and UK are available.
|
||||
|
||||
Is the power supply that comes with Embassy 220v compatible?
|
||||
------------------------------------------------------------
|
||||
Yes.
|
||||
|
||||
How does pricing work for EmbassyOS? Are you targeting a specific USD price?
|
||||
-----------------------------------------------------------------------------
|
||||
The price is changed every 2016 blocks, which occurs about every 14 days. And no, the intent is not to tie EmbassyOS to a USD value, though at the moment USD is a convenient proxy for real purchasing power.
|
||||
|
||||
What are you using for a store backend? Do you store my data?
|
||||
---------------------------------------
|
||||
Great question, here is our exact situation currently:
|
||||
Embassy device sales are processed through Shopify, which we do not like, but it was expedient in the early days, especially for shipping, so we went with it. Aside from a master list of email addresses for those who have explicitly opted in to our mailing list, all customer data is contained within Shopify. We do not duplicate it anywhere. We are asking Shopify to delete our customer data, but they claim it will take upward of 3 months to comply and we of course have no guarantee the data will actually be deleted permanently. This is partly why we exist...as such, we will be moving off of Shopify and onto a self-hosted solution, where Start9 alone controls our customer data for Embassy purchases, which we will delete as a matter of policy following a short grace period after delivery.
|
||||
For EmbassyOS sales, we took the maximally private approach right out of the gate. When you buy EmbassyOS, the only thing we need is an email address, and you can only pay with bitcoin. That's it. Then, unless you have explicitly requested that we keep your email for mailing list purposes, we delete the email immediately upon transaction completion.
|
||||
So...in summary: (1) the shipping data we currently have is stored in Shopify (2) we are asking Shopify to delete all our customer data (3) we will be migrating off of Shopify (4) going forward, we alone will control customer data and will purge it regularly (5) you can always assemble the hardware yourself and just buy EmbassyOS from us with bitcoin, which only requires an email, which is gets purged immediately.
|
||||
|
||||
I want to help, but I'm not a developer. Are there any ways for non-coders to contribute?
|
||||
------------------------------------------------------------------------------------------
|
||||
1. Shill it to everyone and create awareness
|
||||
2. Answer questions from new users in the community channels
|
||||
3. Make tutorial videos
|
||||
4. Write instruction manuals or commit to the docs
|
||||
|
||||
===========
|
||||
Basic Usage
|
||||
===========
|
||||
@@ -48,6 +70,18 @@ Can I run multiple Embassies?
|
||||
-----------------------------
|
||||
Yes, but there is currently no way to synchronize or federate them. We are working on ways to make this possible in the future.
|
||||
|
||||
What if I forget my Embassy password?
|
||||
-------------------------------------
|
||||
Check out the `docs < https://docs.start9labs.com/user-manual/general/forgot-password.html>` on forgot password, and let us know if you have any additional questions. All your services and data will remain.
|
||||
|
||||
Can I move my Embassy to another location? What happens when I do this?
|
||||
------------------------------------------------------------------------
|
||||
Yes, you can move the Embassy to another network. Your service tor addresses will remain the same.
|
||||
|
||||
What’s the advantage of using the .local address over the .onion address?
|
||||
-------------------------------------------------------------------------
|
||||
If you are in your home network it is both faster and more private since the connection never leaves your household. The downside is that it won’t work if you’re on the go.
|
||||
|
||||
Is the software Open Source?
|
||||
----------------------------
|
||||
Yes! EmbassyOS is open sourced under the `Start9 Personal Use License <https://start9labs.com/license>`_. Some of our other projects are currently open sourced under MIT. You can find these in the Start9 Labs `GitHub repository <https://github.com/Start9Labs>`_.
|
||||
@@ -56,6 +90,24 @@ Is there a product warranty?
|
||||
----------------------------
|
||||
Yes! Start9 commits, to the best of our ability, to serving each beta Embassy product released until the wild. We will resolve any issue encountered with our provided hardware or software in a personalized matter. We strive to provide highly available, quality customer service.
|
||||
|
||||
Can you tell me about the License?
|
||||
----------------------------------
|
||||
EmbassyOS is published under our own Start9 Non-Commercial License, which has similar properties to many open source licenses with the exception that users cannot in any way, either through products or services, commercialize the source code, and any changes to the code or derivative works of the code are treated in the same manner. This means people will be welcome to access the source code, download it, use it, run it, fork it, change it, improve it - whatever they want - except sell it or sell services related to it.
|
||||
|
||||
I run a business, can I use an Embassy for tasks such as password management and file sharing?
|
||||
----------------------------------------------------------------------------------------------
|
||||
Absolutely. An Embassy would be a great addition to any business as it is easy to use and provides services that you control, with no subscription fees.
|
||||
|
||||
Why would I even buy this when I can just build it for free??
|
||||
-------------------------------------------------------------
|
||||
(1) White glove support. Because each Embassy comes with a unique product key engraved on it, and we have a record of all product keys ever, we can ask the user to verify their product key in order to receive a higher tier of support, such as phone calls.
|
||||
|
||||
(2) Supporting the project. Buying an Embassy from Start9 is your way of supporting the development of the project. And it's not just out of gratitude, but rather, a recognition that if the project isn't funded, the cool software stops coming.
|
||||
|
||||
(3) Convenience. This is the big one. It's true, some people will choose to use the software without buying an Embassy, but most will not. Very few people on Earth are comfortable using the command line, compiling code, and configuring an OS. Furthermore, hardware is necessary. Sure, some people already have a Raspberry Pi, and others may try to re-purpose an old laptop, but many people would be choosing between buying the Embassy hardware components themselves and assembling vs buying pre-assembled at a reasonable markup. And it's not just a pi, the Ambassador utilizes audio feedback, so a speaker is necessary too. Finally, due to the product key aspect, we can gate certain features of our hosted Service Marketplace. As in, if you buy an Embassy from us, certain services may be free, whereas they may be charged if you don't buy from us. Nothing stops a user from getting the service themselves from elsewhere, but again, convenience.
|
||||
|
||||
Bottom line...We are charging a very marginal rate for something incredibly powerful, and we think the convenience of a plug-and-play device, free service marketplace, and free white glove support is where the money is. Anyone could build their own couches too, but here is a reason furniture stores exist. How much is your time worth?
|
||||
|
||||
The fastest way to get support is via our `Telegram <https://t.me/start9_labs>`_ or `Matrix <https://matrix.to/#/!lMnRwPWnyQvOfAoEnD:matrix.start9labs.com>`_ channels. You can also `email us <support@start9labs.com>`_. Please do not hesitate to reach out!
|
||||
|
||||
=============================
|
||||
@@ -76,14 +128,43 @@ Do I plug the Embassy into my computer?
|
||||
---------------------------------------
|
||||
No. The Embassy only needs to be plugged into power and internet, just like your router. You can set it up right by your router and forget about it.
|
||||
|
||||
How much storage does the Embassy have?
|
||||
---------------------------------------
|
||||
Currently, the Embassy ships with a 128gb of storage.
|
||||
|
||||
Are my Internet requests anonymous and secure?
|
||||
----------------------------------------------
|
||||
EmbassyOS and every service on the Embassy serve their own Tor Hidden Services with unique Tor addresses. The private keys used to create these addresses are generated on your phone or computer when you first set up the Embassy. No one, not even Start9, has any idea what your Tor addresses are, let alone the password(s) you choose to authenticate with them.
|
||||
|
||||
Can multiple Embassys be setup to run redundantly in physically separate locations?
|
||||
-----------------------------------------------------------------------------------
|
||||
Soon (tm). Currently no, be we have plans for a feature that will enable Embassies to provide encrypted, automated backup services for one another.
|
||||
|
||||
How does the Embassy compare to other Bitcoin nodes or personal servers?
|
||||
------------------------------------------------------------------------
|
||||
The cheapest way to run a Bitcoin/Lightning node is to buy a Raspberry Pi (or equivalent), compile the software from source yourself, and host everything on Tor. This takes even technical people significant time to accomplish. On the other end of the spectrum is something like the Embassy, which "just works". In between is stuff like MyNode, Nodl, Dojo, Umbrel, and Raspiblitz, which all require some degree of command line effort and network configuration. The biggest benefit of the Embassy is that it is infinitely extensible to all of open-source, self-hosted software. The service listing will expand enormously over time in ways the other platforms cannot.
|
||||
|
||||
Would you consider (Umbrel, Nodl, Dojo, etc) a competitor to you guys, or are they different enough to be compatible?
|
||||
---------------------------------------------------------------------------------------------------------------------
|
||||
Other node devices are competitors, and there are distinct trade-offs to each platform, but we are definitely moving toward the same future, which is a win for everyone!
|
||||
We are taking more a general approach to all of open-source, self-hosted software, including Bitcoin/Lightning. They are more Bitcoin/Lightning oriented.
|
||||
|
||||
Is a more powerful device in the works??
|
||||
----------------------------------------
|
||||
In the near future, the Embassy will move to more powerful hardware.
|
||||
|
||||
I heard on an old podcast that there will be an Embassy Two, to be launched in 2021. Is there an ETA on this?
|
||||
--------------------------------------------------------------------------------------------------------------
|
||||
Do not expect a new device in 2021, but we are always doing R&D.
|
||||
|
||||
Can I mine Bitcoin with this?
|
||||
-----------------------------
|
||||
No, you can not.
|
||||
|
||||
Does the Embassy only work over Tor? No http or VPN...??
|
||||
----------------------------------------------------
|
||||
The Embassy’s current primary communication is Tor, yes. In many cases we use HTTP over Tor (they are not mutually exclusive), you can see this by navigating to the Tor address in a browser and see the “http” in front of it. A VPN is a feature we’re exploring as an alternative to Tor to make things faster without meaningfully impacting privacy. You can also connect directly via LAN if you are on the same network as your device.
|
||||
|
||||
=========================
|
||||
Setup and Troubleshooting
|
||||
=========================
|
||||
@@ -116,14 +197,128 @@ Why does the Bitcoin service take so long to be ready?
|
||||
------------------------------------------------------
|
||||
On first install, the Bitcoin service must verify the entire history of transactions in order to verify transactions going forward. This can take approximately a week depending on your internet connection. You can continue to use the Embassy normally in the meantime.
|
||||
|
||||
Can the IBD (Initial Block Download) be made faster? Or can wait times be improved?
|
||||
------------------------------------------------------------------------------------
|
||||
We have some work planned to improve the wait times, which we think is the better way to deal with painful sync times without sacrificing the trust minimization.
|
||||
|
||||
Can this run 'X' Service??
|
||||
--------------------------
|
||||
Potentially. The list of software that can be self-hosted is growing rapidly. Feel free to drop us a comment letting us know what you'd like to see on the Embassy!
|
||||
|
||||
Does the Embassy run a full archival Bitcoin node?
|
||||
--------------------------------------------------
|
||||
The Embassy runs a full node, but does not run a full *archival* node, it's pruned. This means it does not store the entire Blockchain. As it syncs, it discards blocks and transactions it does not need.
|
||||
It is fully validating and verifying consensus all the way from Genesis. Really, the only reason to store the entire Blockchain is if you want to run a block explorer. Learn more :ref:`here <node>`.
|
||||
|
||||
What actions, specifically, are only possible with an archival, or ‘unpruned’ node?
|
||||
-----------------------------------------------------------------------------------
|
||||
The more sophisticated the blockchain analysis being done is, the more index data is required, which will increase the system resources required. For example, if you wanted to run a block explorer, you would require not only a full archival node, but also a full transaction index.
|
||||
|
||||
Is it insecure to run a pruned node?
|
||||
------------------------------------
|
||||
As a user, pruned nodes and archival nodes provide you the same security. In a larger sense, if 100% of people ran pruned nodes, the security of the network could be in dire circumstances and be put at risk if no nodes kept history, as then no one could bootstrap new nodes. The reality however, is that most Embassy owners are new node operators, so there is no net systemic risk introduced.
|
||||
|
||||
Why would I want to run a lightning node?
|
||||
-----------------------------------------
|
||||
The Lightning Network (LN) is a second 'layer,' built on top of the Bitcoin Protocol. As a result all transactions on LN are backed up by the full security of the Bitcoin network. Lightning is designed for instant payments between nodes, but similar to running a Bitcoin node, running your own is the only way to be sovereign. When you have your own node, you will have the convenience of linking a Lightning wallet, for use on the go. It is also possible to earn an income (granted a very small one at this time), if you are willing to learn how to become a 'routing node.'
|
||||
|
||||
Are there any resources for learning about how to use Bitcoin and the Lightning Network?
|
||||
----------------------------------------------------------------------------------------
|
||||
It may be helpful to start `here <lopp.net/bitcoin>`_ for Bitcoin and `here <lopp.net/lightning>`_ for Lightning.
|
||||
|
||||
I opened a Lightning channel, but my local balance is lower than I expected. Where is the remainder?
|
||||
-----------------------------------------------------------------------------------------------------
|
||||
A fee to close the channel (onchain) is set aside at opening.
|
||||
|
||||
How is that fee estimation calculated?
|
||||
--------------------------------------
|
||||
The commitment fees are automatically negotiated every few blocks with your peer. They are on chain txs like all channel closes but they are not broadcast until you attempt to close the channel.
|
||||
|
||||
What would happen if I shut down an Embassy that is running a Lightning node with open channels?
|
||||
------------------------------------------------------------------------------------------------
|
||||
It is REALLY IMPORTANT that people understand that if they shut off their Lightning services for long periods of time (days on end) it is possible for your peers to cheat you out of money. If you are not prepared to LOSE ALL THE MONEY IN YOUR CHANNELS, KEEP YOUR NODE RUNNING.
|
||||
That said, malicious actors on the network right now are probably sparse, however you are still open to that risk if you do not keep your node online.
|
||||
|
||||
Is there a solution to this?
|
||||
----------------------------
|
||||
Yes, the concept of a Watchtower was originally conceptualized in the LN whitepaper. A Watchtower is simply a lightning node to which you can give the authority to monitor transactions associated with your open payment channels.
|
||||
|
||||
Is a wallet vulnerable to hacking if it’s always online??
|
||||
-------------------------------------------------------
|
||||
Funds are not stored on the node typically. The node simply serves as a source of truth for the state of the blockchain. Attacks depend on where the keys are and where the signing happens. You can use something like a hardware wallet for better security. Though, to be fair, a lot of attacks depend on you or your machine being targeted specifically, and a whole bunch of attack vectors are highly theoretical and obscure.
|
||||
Most successful attacks seem to be either fake/doctored software or a social attack (tricking you into installing some malware or giving your seed outright or something like that).
|
||||
Keep in mind, however, the more value there is out there to steal, the more sophisticated attacks will get automated (bots, crawlers etc). So its not just the risk profile of today, but also tomorrow you have to consider. That’s why something like a hardware wallet or dedicated mobile device for key signing is a good idea.
|
||||
Even if your wallet is plugged into your Embassy, whether your wallet is hot or cold depends on the hardware that stores the keys.
|
||||
|
||||
|
||||
How does Bitcoin Proxy request (and verify) data when that data is needed by some app using it?
|
||||
-----------------------------------------------------------------------------------------------
|
||||
Proxy fetches blocks from your pruned node if it still has them, and fetches them from peers when it does not. Proxy can ensures the fetched block is valid by comparing it to its header, which is retained by the pruned node. The header is a product of the hash of the block itself, amongst other things, so it can't be faked.
|
||||
|
||||
Can it be used as a firewall?
|
||||
-----------------------------
|
||||
Potentially. The PiHole service is on the roadmap.
|
||||
|
||||
Will there be a VPN?
|
||||
--------------------
|
||||
We are looking into adding as a Wireguard service for VPN access when you are not home. A client-to-client VPN may also be possible.
|
||||
|
||||
Is the Embassy a Tor relay node?
|
||||
--------------------------------
|
||||
Not, currently it is not, but we plan to add that functionality in the future.
|
||||
|
||||
What is the difference between the Bitcoin Wallet Tracker and the Electrum Personal Server?
|
||||
-------------------------------------------------------------------------------------------
|
||||
Bitcoin Wallet Tracker and Electrum Personal Server are 2 services that do the same thing, similar to bitcoind vs btcd, or lnd vs c-lightning.
|
||||
Both work with your Bitcoin node to provide a richer set of information to wallets than could be done with bitcoind alone. They are basically identical in purpose, their differences are notably in the software memory requirements and how snappily they can answer the same questions.
|
||||
Electrum (and some other wallets) require more than just a Bitcoin node to run in a sovereign way, they require an “Electrum Server”. Both Electrum Personal Server and Bitcoin Wallet Tracker are “Electrum servers”.
|
||||
|
||||
Which wallets can I use that sync with my Embassy Bitcoin node?
|
||||
---------------------------------------------------------------
|
||||
There are many wallets that support linking to your own full node. You will need one that supports tor. Here are a few options that are compatible: FullyNoded, Samourai, Specter, Wasabi, Zap, and Zeus.
|
||||
|
||||
Are files on File browser encrypted on disk?
|
||||
--------------------------------------------
|
||||
No, not currently.
|
||||
|
||||
Can I use my CUPS instance with other people? How does that work?
|
||||
-----------------------------------------------------------------
|
||||
Cups does not have multiple accounts support. Each person would need their own Embassy. We are considering adding multi-account support to Cups, but it's just not a priority at the moment.
|
||||
|
||||
Is the embassy able to connect to Sphinxchat?
|
||||
---------------------------------------------
|
||||
Maybe, but we are also planning to add Sphinxchat to the Embassy directly.
|
||||
|
||||
Is it possible to run c-lightning and lnd parallel on the Embassy?
|
||||
------------------------------------------------------------------
|
||||
Yes, you may run both. They will operate in their own environments and allow you to run services that depend on either.
|
||||
|
||||
How do I connect my Spark mobile app to the Embassy Spark server?
|
||||
-----------------------------------------------------------------
|
||||
To use a Spark client, you still need to have Spark installed on the Embassy (which ‘serves’ Spark). Then, under Properties, there is a "Pairing URL". The first part of this is the server URL, and the end portion of it is the access key.
|
||||
|
||||
When attempting to add new peer, RTL says "server is still in the process of starting," but chain state seems to be fully up to date. What can I do?
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
Check the LND logs, it can take a while to bootstrap, and starting RTL before this completes could cause errors.
|
||||
|
||||
"Server is still in the process of starting," but LND and RTL are running. How can I address this?
|
||||
---------------------------------------------------------------------------------------------------
|
||||
You may need to restart LND.
|
||||
|
||||
Can the browser extension be used with Bitwarden hosted on the embassy?
|
||||
-----------------------------------------------------------------------
|
||||
Yes, but only in a tor-enabled browser. Just add your .onion address as the server in the extension.
|
||||
|
||||
What's the best way to move a small lightning balance?
|
||||
------------------------------------------------------
|
||||
It is possible to have lightning balances that are so low that they will not (or barely will) cover the on-chain fees to recoup into an on-chain wallet.
|
||||
|
||||
I don't see an answer to my question regarding a certain service. Is there more documentation?
|
||||
-----------------------------------------------------------------------------------------------
|
||||
While we are intent on providing the most friendly experience possible to our customers, ultimately it will be impossible for Start9 to create documentation and tutorials for every service we make available on the Embassy. Each service *should* have its own documentation produced by the service developers themselves, and we will do our best keep track, consolidate, and link to it. Also, much of the reason good tutorials don't exist is simply because no one in the community has taken the time to produce it. If you come across something useful or write something up yourself, please let us know and we will promote it. Otherwise we will do our best to answer questions as they arise and gradually build out tutorials where they are lacking.
|
||||
|
||||
I want to understand in depth how a Service works and it's available configuration options. Where can I go to learn more?
|
||||
--------------------------------------------------------------------------------------------------------------------------
|
||||
Depending on the app, the config options can be quite involved. Bitcoin Core, for example, has an enormous amount of complex options, almost none of which are useful to a normal user doing normal things. We chose some very sane defaults that should work for normal use cases. Here is an example config from the Bitcoin `GitHub <https://github.com/bitcoin/bitcoin/blob/master/share/examples/bitcoin.conf>`.
|
||||
By reading the descriptions in the link above, as well as doing some extra searching on your favorite search engine, you can begin to discover all the crazy ways in which someone can customize their Bitcoin node. Here is another list of `possible options <https://en.bitcoinwiki.org/wiki/Running_Bitcoind>`.
|
||||
We translated much of (but not all of) the tons of options into a clean and easy-to-use GUI with toggles, dropdowns, inputs, etc, which is what you're seeing in your config screen. If you notice the little "?" icons on the left of each option, clicking them will provide a brief description as to what the option does. Also, our config GUI restricts the possible values you can enter such that you don't accidentally crash Bitcoin. That said, be very careful about just randomly changing things, lest your node starts to behave strangely.
|
||||
|
||||
|
||||
@@ -11,6 +11,8 @@ Download the Setup App
|
||||
|
||||
`Google Play <https://play.google.com/store/apps/details?id=com.start9labs.setup>`_
|
||||
|
||||
`APK direct download <https://github.com/Start9Labs/setup-app/releases>`_
|
||||
|
||||
Power On
|
||||
========
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Creating A Backup
|
||||
|
||||
To begin the backup process:
|
||||
|
||||
1. Enter the USB stick provided with the Embassy kit, or any USB drive with enough storage capacity, into a USB port on the device.
|
||||
1. Enter a USB drive with sufficient capacity into a USB port on the device. The blue ports are USB 3.0. The black ports are USB 2.0.
|
||||
2. Navigate to the `Services` sub menu from the main dashboard menu.
|
||||
3. Select the service to be backed-up.
|
||||
4. Select the floppy disc icon next to the `Last Backup` menu item. If a backup was never completed, this should say "never".
|
||||
|
||||
Reference in New Issue
Block a user