- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
+
+
+What is a DAO?
+ +A DAO, or Decentralized Autonomous Organization, is an organization represented by rules encoded as a computer program that is transparent, controlled by the organization members, and not influenced by a centralized government. It operates autonomously and can execute actions such as making decisions and managing resources based on pre-defined rules or through a consensus mechanism. + +
+
diff --git a/docs/dao/liquidity-mining.md b/docs/dao/liquidity-mining.md
new file mode 100644
index 000000000..54adebd2a
--- /dev/null
+++ b/docs/dao/liquidity-mining.md
@@ -0,0 +1,35 @@
+# Liquidity Mining
+
+Liquidity Mining (LM) launched on Jul 17 2021, 20:00:00 GMT. 5.5% of the total token supply, 5.5 Million NODE, has been allocated to the first LM round of 6 months. NODE reward distribution for the 4 pools available is as follows:
+
+- Sushiswap NODE/ETH Pool - 40% - 2,200,000 NODE
+- Uniswap NODE/ETH Pool - 40% - 2,200,000 NODE
+- NODE Governance Staking xDai - 10% - 550,000 NODE
+- NODE Governance Staking Mainnet -10% - 550,000 NODE
+
+A further 5.5% of the token supply has been reserved for future rounds of LM. At the end of the first round the team will re-assess the Liquidity Mining program, potentially deploying new pools and distribution.
+
+### Liquidity Provision Pools Contract Addresses
+
+- Sushiswap NODE/ETH Pool - [0x60cd8dcc7cce0cca6a3743727ce909b6f715b2d8](https://etherscan.io/address/0x60cd8dcc7cce0cca6a3743727ce909b6f715b2d8)
+- Uniswap NODE/ETH Pool - [0xee3b01b2debd3df95bf24d4aacf8e70373113315](https://etherscan.io/address/0xee3b01b2debd3df95bf24d4aacf8e70373113315)
+
+### LP Token Addresses (Mainnet)
+
+- Uniswap v2 ETH/NODE LP - [0xee3b01b2debd3df95bf24d4aacf8e70373113315](https://etherscan.io/address/0xee3b01b2debd3df95bf24d4aacf8e70373113315)
+- Sushiswap ETH/NODE LP - [0x60cd8dcc7cce0cca6a3743727ce909b6f715b2d8](https://etherscan.io/address/0x60cd8dcc7cce0cca6a3743727ce909b6f715b2d8)
+
+## Liquidity Mining Contracts
+
+- NODE Governance Staking Mainnet - [0x19992b52338B7B49De9679ae018A7027803dB1Aa](https://etherscan.io/address/0x19992b52338B7B49De9679ae018A7027803dB1Aa)
+- NODE Governance Staking xDai - [0xF66823fdc33B9F4C66dB4C3394FF139872C12f16](https://blockscout.com/xdai/mainnet/address/0xF66823fdc33B9F4C66dB4C3394FF139872C12f16/transactions)
+- Uniswap Liquidity Mining - [0x072115DbD5c8b47E971890357d2951d4569F6B27](https://etherscan.io/address/0x072115DbD5c8b47E971890357d2951d4569F6B27)
+- Sushiswap Liquidity Mining - [0x89F2e26F20Bf66bBFAc947A3b628b4b4724AaA5c](https://etherscan.io/address/0x89F2e26F20Bf66bBFAc947A3b628b4b4724AaA5c)
+
+### Weekly Distribution
+
+Round 1 (26 weeks) weekly NODE rewards distribution percentages based on LM supply are as follows:
+
+| % per week | 0.00% | 3.80% | 3.80% | 3.00% | 3.00% | 2.50% | 2.50% | 2.50% | 2.50% | 2.60% | 2.80% | 3.00% | 3.20% | 3.40% | 3.60% | 3.80% | 4.00% | 4.20% | 4.40% | 4.60% | 4.80% | 5.00% | 5.20% | 5.40% | 5.60% | 5.80% | 5.00% |
+| ---------- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
+| Week | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 |
diff --git a/docs/dao/node-basics.md b/docs/dao/node-basics.md
new file mode 100644
index 000000000..235eda6ec
--- /dev/null
+++ b/docs/dao/node-basics.md
@@ -0,0 +1,72 @@
+# The NODE Economy
+
+### NODE Basics
+
+Token Address on Mainnet - [0xDa007777D86AC6d989cC9f79A73261b3fC5e0DA0](https://etherscan.io/address/0xDa007777D86AC6d989cC9f79A73261b3fC5e0DA0)
+
+Token Address on xDai - [0xc60e38C6352875c051B481Cbe79Dd0383AdB7817](https://blockscout.com/xdai/mainnet/address/0xc60e38C6352875c051B481Cbe79Dd0383AdB7817/transactions)
+
+NODE has a total initial supply of 100,000,000 tokens. These tokens have been distributed in accordance with the following chart:
+
+
+
+### NODEdrop
+
+NODE has been airdropped in a NODEdrop to our community of faithful supporters. Recipients of the NODEdrop include:
+
+- Dappnode Team Members
+- Dappnode Founders
+- Purchasers of Dappnode hardware
+- Code Contributors
+- Active community members, ranked by our sourcecred algorithm
+- Donors to Dappnode in Gitcoin Grants Rounds (with donations above $1)
+- Eth2 stakers who have self-identified as Dappnode runners by including the word "Dappnode" in their graffiti
+- Eth2 stakers present in the Genesis of Eth2
+
+Check your NODEdrop [here](http://app.dappnode.io/nodedrop).
+
+### NODEstream
+
+90% of the entire initial supply of NODE has been allocated to the "NODEstream" which is set to flow for a period of 3 years (36 months - i.e. until July 2024). This is essentially a continous stream of NODE that flows out of the "Reservoir" and into the "Claimable" section of the dashboard. NODEstream distribution can be roughly tracked as follows:
+
+Table for Eth
+
+| Date | Month | Claimable | Held in Reservoir |
+| ------------------------------------------------------------- | ----- | --------- | ----------------- |
+| Jul 17 2021, 22:00:00 GMT+0200 (Central European Summer Time) | 0 | 10% | 90% |
+| Apr 17 2022, 22:00:00 GMT+0200 (Central European Summer Time) | 9 | 32.5% | 67.5% |
+| Jan 17 2023, 22:00:00 GMT+0200 (Central European Summer Time) | 18 | 55% | 45% |
+| Oct 17 2023, 22:00:00 GMT+0200 (Central European Summer Time) | 27 | 77.5% | 22.5% |
+| Jul 17 2024, 16:00:00 GMT+0200 (Central European Summer Time) | 36 | 100% | 0% |
+
+Table for xDai
+
+| Date | Month | Claimable | Held in Reservoir |
+| ------------------------------------------------------------- | ----- | --------- | ----------------- |
+| Jul 17 2021, 22:00:00 GMT+0200 (Central European Summer Time) | 0 | 0% | 100% |
+| Apr 17 2022, 22:00:00 GMT+0200 (Central European Summer Time) | 9 | 25% | 75% |
+| Jan 17 2023, 22:00:00 GMT+0200 (Central European Summer Time) | 18 | 50% | 50% |
+| Oct 17 2023, 22:00:00 GMT+0200 (Central European Summer Time) | 27 | 75% | 35% |
+| Jul 17 2024, 16:00:00 GMT+0200 (Central European Summer Time) | 36 | 100% | 0% |
+
+The NODEstream works on a time-based linear function, meaning the reservoir will gradually hold a smaller percentage of your NODE and thus more NODE is made instantly available from your staking rewards. At the end of the NODEstream The reservoir will no longer hold any NODE and 100% of your staking rewards will be instantly claimable.
+
+This chart show how the function works in Etherum network.
+
+What is the purpose and mission of the Dappnode DAO?
+ +DappNode's DAO aims to promote and simplify the use of decentralized infrastructure. It aspires to create a more decentralized web by providing tools that make running nodes, DApps, and blockchain-related software more user-friendly and accessible to a wider audience. By establishing a DAO, DappNode ensures that its mission and direction are decided collectively by its community, allowing for a more democratic and transparent decision-making process. The DappNode DAO encourages collaboration, fostering a community that is actively involved in the project's evolution, and ensuring the sustainability and success of the platform in the decentralized space. + +
+ 
+
+ 
+
+ 
+
- 
-
-
- 
-
-
+
+
+What do I need to do to claim my rewards?
+ Once your pending rewards are transformed into accumulated rewards after your block proposal, a small claim transaction will be required from the withdrawal address to send the ETH rewards to your wallet. +
+
+
+Is there a fee that Dappnode takes for participating in Smooth?
+ 7% of all the Rewards goes to supporting the development of Dappnode and sustainability of Smooth. +
+
+
+If I want to unsubscribe my validator from Smooth, when is the best time to do it?
+ Unsubscribing a validator from Smooth causes it to lose all its pending rewards. Hence, the ideal moment to exit Smooth is just after your last successful block proposal is reflected in Smooth's Smart Contract. A successful block proposal transfers all pending rewards claimable, allowing you to claim them before unsubscribing. This approach minimizes the pending rewards lost when unsubscribing. +
+
+
+## Glossary
+
+`Reward`: Any balance denominated in ETH that is sent to Smooth. Rewards are detected by the oracle and shared fairly among all the participants in the pool. The oracle will detect all types of rewards and distribute them fairly. All rewards are denominated in `ETH` and other types of tokens such as ERC20 are not considered by the oracle. The vast majority of rewards come from block proposals of Smooth's validators and Donations.
+
+`Pending rewards`: Pending rewards are those to be owned by the validator but not yet consolidated, rendering them unclaimable. Upon a successful block proposal by the validator, these rewards transition into the 'Accumulated rewards' category, becoming claimable. This mechanism ensures that validators can only claim rewards after contributing to the pool, guarding against cheating or exploiting the system.
+
+`Accumulated rewards`: All consolidated rewards your validator has generated, i.e. those claimed and claimable.
+
+`Claimable rewards`: Rewards ready to claim. Claimable rewards are the sum of all your accumulated rewards minus the rewards that have been claimed already. Only the withdrawal address of the validator can claim it's rewards.
\ No newline at end of file
diff --git a/docs/smooth/in-depth-overview.md b/docs/smooth/in-depth-overview.md
new file mode 100644
index 000000000..a5e5b1758
--- /dev/null
+++ b/docs/smooth/in-depth-overview.md
@@ -0,0 +1,140 @@
+# General Overview
+
+In this page, you will find an in-depth explanation on how Smooth works. This includes the different components of Smooth, all states possible of a subscribed Smooth validator, and much more!
+
+:::info
+We recommend reading and understanding the contents of this page before subscribing to Smooth.
+:::
+
+## Configuration parameters
+
+The smoothing pool shall contain the following configuration parameters:
+* `COLLATERAL_GWEI`: Amount of collateral in gwei that a validator need to join the pool.
+* `DEPLOYED_SLOT`: Slot when the smoothing pool contract was deployed.
+* `CHECKPOINT_SIZE_SLOTS`: How often the smart contract root is updated with new rewards, in slots.
+* `OWNER_ADDRESS`: Set of addresses with `0x` prefix that are allowed to update the smoothing pool contract.
+* `QUORUM`: Amount of `OWNER_ADDRESS` that have to agree on the merkle root before it's considered consolidated. As an example this number could be 3/4, where 4 addresses are allowed to update the root and 3 of them have to agree.
+* `POOL_CONTRACT_ADDRESS`: Address with `0x` prefix of the smoothing pool contract.
+* `NETWORK`: Network where rewards are being calculated: `mainnet` or `goerli`.
+* `POOL_FEES_ADDRESS`: Address with `0x` prefix of the account that can claim the smoothing pool fees.
+* `POOL_FEES_PERCENT`: Amount in % (scaled by 100) that `POOL_FEES_ADDRESS` gets for every reward sent to the smoothing pool. Note that it also gets rounding remainders on top, but this is almost neglectable.
+
+## Smooth's source of rewards
+
+A `Reward` is considered to be any balance denominated in Eth that is sent to the `POOL_CONTRACT_ADDRESS`. These are detected by the oracle and shared fairly among all the participants in the pool at a given time. The oracle shall detect all these types of rewards and distribute them fairly (see rewards calculation section). All of these rewards are denominated in `ETH` and other types of tokens such as ERC20 are not considered by the oracle:
+* `MevBlock`: Comes from a block proposal where the reward was obtained via an off-chain agreement using tools such as mev-boost, usually coming as the last transaction in the block.
+* `VanilaBlock`: Comes from a block proposal where no MEV relays participated.
+* `Donation`: Any address can send an arbitrary amount, either via an Eth tx or via a smart contract to the pool.
+
+## Subscribe/unsubscribe/ban
+
+Only the following validators can subscribe into the pool:
+* Validators in active state (not exiting nor slashed). Validators with a wrong state will be ignored.
+* Validators with eth1 withdrawal credentials. Validators with BLS credentials will be ignored.
+
+Rewards are only shared among subscribed participants in the pool. Hereunder it's explained the different ways in which a validator can join or leave the pool. Joining can be done with manual or automatatic subscription. And leaving can be done by unsubscribing to the pool or by being banned from it.
+
+**Subscribing** to the pool:
+* `Automatic Subscription`: If any validator sends a `MevBlock` or `VanilaBlock` reward to the smoothing pool contract `POOL_CONTRACT_ADDRESS` it is considered automatically subscribed into the pool, and will start accruing rewards from that moment. This type of subscription doesn't require any collateral or lock up of funds, since by successfully proposing a block with the correct fee recipient, we consider that this validator has enough skin in the game. However, since block proposals are a rare event, it can take weeks or even months for a validator to get automatically subscribed. This is not ideal because it won't be leveraging the benefits of the smoothing pool during this time.
+* `Manual Subscription`: On the other hand, a validator can start earning rewards from the very beginning if it adds `COLLATERAL_GWEI` amount as collateral. This collateral can be deposited by calling the register function in the oracle smart contract. This type of subscription allows the validator to start earning rewards without having to wait weeks or months until a proposal is detected. A subscription is only considered valid if:
+ * `collateral>=COLLATERAL_GWEI`
+ * The `validatorIndex` included is the transaction
+ * The account that sent the transaction matches the `validatorIndex` withdrawal credentials.
+
+
+Note that the collateral that a validator deposits via its withdrawal address is added to the validator `PendingRewards`. This means that it is returned after the first valid block proposal. In other words, the pool doesnt get the collateral, it just blocks it until the validator proposes a block. See `PendingRewards`, `AccumulatedRewards` down below. Note also that if by mistake a validator deposits the colateral twice, the second one is also returned.
+
+**Unsubscribing** from the pool:
+* `Unsubscribe`: Similarly, the oracle shall detect the following event from the smoothing pool smart contract, which signals that a given `validatorIndex` was unsubscribed from the pool. Note that the unsubscription is only considered valid if the `sender` matches the validator withdrawal address.
+
+**Banning** from the pool:
+* The oracle shall detect if an active validator in the smoothing pool proposed a block with a `fee_recipieint` different than `POOL_CONTRACT_ADDRESS`. This means that this validator sent its reward to a different address, so we consider this misbehaving and the validator will be banned forever from the smoothing pool.
+
+:::danger
+Comprehending the purpose of the fee recipient and why it's vital for validators not to change it while subscribed to Smooth is crucial. Modifying a validator's fee recipient to an address that is not Smooth's and proposing a block with it while being subscribed to the pool constitutes misconduct. Such behavior will lead to the validator being banned from participating in the pool.
+:::
+
+## State machine
+
+The oracle uses the following **state machine** to track the status of the different validators that are subscribed to Smooth. Different actions can trigger a state change and in the following image all possible transitions are described.
+
+
+
+There are 5 different states a validator can have:
+* `Active`: A validator is active and subscribed to the pool, earning rewards over the time.
+* `YellowCard`: The validator missed only its last block proposal, but still earns rewards.
+* `RedCard`: The validator missed two block proposals in a row. In this state the validator does not earn rewards until a valid block has been proposed by it.
+* `NotSubscribed:` The validator is no longer subscribed to the pool, but still tracked by the validator. For example, a validator that unsubscribed. Note that this is still tracked because a validator can unsubscribe but it may still have pending balance to claim. In this state the validator does not earn rewards.
+* `Banned`: The validator is banned forever from the pool. **A validator is banned when its subscribed to the pool but proposes a block with the wrong fee recipient**.
+* `Untracked`: The validator is not tracked by the pool. It never subscribed before nor has any active subscription.
+
+And 6 different actions can trigger a state transition:
+* `ProposalOk`: The validator proposed a valid block with its rewards correctly sent to the smoothing pool address.
+* `ProposalMissed`: The validator should have proposed a block but missed its proposal.
+* `ProposalWrongFee`: The validator proposes a block but with a wrong fee recipient.
+* `ManualSubscription`: The validator manually subscribes to the pool, depositing collateral for its validator index by calling the smart contract function (see event).
+* `AutoSubscription`: The validator is automatically subscribed to the pool, by setting as fee recipient the smoothing pool address.
+* `Unsubscribe`: The validator manually unsubscribes to the pool, calling the unsubscribe function from the smart contract (see event).
+
+## Rewards calculation
+
+When a validator has an active subscription to the pool (`Active` or `YellowCard` state) it is eligible for rewards, meaning that it will receive a given share of each reward that is sent to the pool. Validators in `RedCard` are considered subscribed, but don't earn rewards until they become active again.
+
+There are two **sources of rewards**:
+* Block proposals (execution layer rewards earned via tips or MEV), see `MevBlock` or `VanilaBlock`.
+* Donations by any user that sends an arbitrary amount of Eth balance to the contract, see `PayableDonation` or `NonPayableDonation`.
+
+With the incoming rewards to the pool, the oracle calculates two different types of validator rewards:
+* `AccumulatedRewards`: This rewards are already consolidated, meaning that they can be claimed at any time, by submitting a valid proof to the smart contract. This assumes that a `CHECKPOINT_SIZE_SLOTS` has been reached, and rewards are ready to be claimed onchain.
+* `PendingRewards`: This rewards are not *consolidated* yet, meaning that they belong to the validator but they can be claimed, until a valid block proposal is sent to the smoothing pool.
+
+It's defined as **consolidate balance** when a validator proposes a block whose fee recipient address is correctly sent to the smoothing pool (`POOL_CONTRACT_ADDRESS` address). When a validator consolidates its rewards, all its `PendingRewards` are added to its `AccumulatedRewards`, meaning that what was pending is now ready to claim at any time. Note also that after performing this operation the `PendingRewards` are reset. So consolidating can be seen as a way of converting the `Pending` into `Accumulated`.
+
+All validator rewards are updated on every **finalized** block that is added to the chain. It is important to highlight that it is only done on finalized blocks, since this implies that the block is non-reversable and no reorgs are possible at this point (unless something major happens).
+
+When calculating the rewards, the pool operator takes a cut for each reward that is sent to the pool, where `POOL_FEES_ADDRESS` gets `POOL_FEES_PERCENT`. The rest of the rewards are shared evenly among all eligible validators. This value shall not be higher than 100% and its stored as scaled by x100, which allows to have two decimal points.
+
+Regarding the pool fees, note that the funds are not sent *per se* to the `POOL_FEES_ADDRESS` but they are added as a leaf in the merkle tree (see merkle tree section). In other words, the owner of the pool can claim the fees as if it were a validator, by providing a valid merkle proof and using said address as sender.
+
+For each reward (see types of rewards) that is sent to the pool on a finalized block, it is distributed as follows:
+* Get the amount of eligible validators (validators that are eligible for rewards) `Active` or `YellowCard` state.
+* The pool takes `POOL_FEES_PERCENT` of that reward, increasing its balance `AccumulatedRewards` by that amount + remainder (if any). Note that all the arithmetic is integer based without decimals, hence the remainder.
+* The reward minus the cut (and the remainder) is shared among all eligible validators. Note that if there is also a reminder, it goes to the `POOL_FEES_ADDRESS`, increasing its `AccumulatedRewards`.
+* Each eligible validator gets its `PendingRewards` increased by that amount.
+* If the reward comes from a block proposal, the validator gets its `AccumulatedRewards` consolidated, since it has proven that is participating in the pool.
+
+Note that the pool gets the remainders from two different divisions, but this is done for simplicity and since the calculations are in wei, the value of it is neglectable. Doing this makes the oracle fair with all validators, since each one of them gets the exact same amount of rewards. So in practice, `POOL_FEES_ADDRESS` just gets `POOL_FEES_PERCENT`.
+
+## Merkle trees and proofs
+
+Since storing all rewards calculations on-chain would be almost impossible and very expensive, merkle trees are used to summarize the state of all validators tracked by the oracle in a given value called **merkle root*. All the computation of the rewards is done off-chain by the oracle, and on every `CHECKPOINT_SIZE_SLOTS` all rewards all calculated and summarized in a new merkle root that is stored on-chain in Ethereum.
+
+Each leaf of the tree contains two values, the withdrawal address and the accumulated balance. Note that in order to be more gas efficient and allow to claim of multiple validators in just one transactions, all validators belonging to the same withdrawal address are aggregated.
+
+```go
+type RawLeaf struct {
+ WithdrawalAddress string
+ AccumulatedBalance *big.Int
+}
+```
+
+
+
+* The merkle tree leafs are ordered by its deposit address in ascending order.
+* The merkle tree is prepended (first element) with a leaf containing `POOL_FEES_ADDRESS` and the accumulated balance. See rewards calculation section.
+* The merkle leafs are hashed with solidity `sha3` hashing algorithm.
+* Withdrawal addresses in the merkle tree shall be unique.
+* The hashing algorithm for the merkle tree is `keccak256`.
+* The hashing algotithm for the merkle tree shall sort sibling pairs.
+* The withdrawal addresses in the merkle tree shall be in lower case.
+
+Every `CHECKPOINT_SIZE_SLOTS` the oracle updates in the smoothing pool smart contract stored in the Ethereum blockchain a new merkle root, that summarizes the rewards that each address can claim. Anyone that controls said address, can claim their rewards by providing a valid merkle proof, prooving that a given leaf is contained within the merkle tree represented by that merkle root.
+
+Since all this data is not available in Ethereum, the oracle shall provide this proofs so that they can be used off-chain. Note that these proofs can be generated by anyone compliying with this specs and with the existing available data on-chain. See [merkle proofs](https://ethereum.org/es/developers/tutorials/merkle-proofs-for-offline-data-integrity/)
+
+
+## Smart contract
+
+See https://github.com/dappnode/mev-sp-contracts
+
+
diff --git a/docs/smooth/subscribe-to-smooth/automatic.md b/docs/smooth/subscribe-to-smooth/automatic.md
new file mode 100644
index 000000000..7b8877de0
--- /dev/null
+++ b/docs/smooth/subscribe-to-smooth/automatic.md
@@ -0,0 +1,16 @@
+# Automatic Subscription
+
+This is the simplest way to subscribe to Smooth. It consists of changing the fee recipient of your validator to Smooth's address and subscribing automatically when proposing your next block.
+
+### Step 1: Change your fee recipient to Smooth's address.
+
+Go to your dappnode's [staking brain](http://brain.web3signer.dappnode/) and change the fee recipient of the validators you want to subscribe to Smooth's address (`0xAdFb8D27671F14f297eE94135e266aAFf8752e35`). Once Smooth recieves the rewards from your validator, it will automatically subscribe your validator to Smooth, and you will start receiving rewards from other members of Smooth!
+
+
+:::danger Keep the fee recipient set to Smooth's address!
+It is extremely important that you keep the fee recipient of your validator set to Smooth's address (`0xAdFb8D27671F14f297eE94135e266aAFf8752e35`) as long as it is subscribed to Smooth. If, at any point, you change the fee recipient of your validator and propose a block without unsubscribing first, you will be banned from Smooth and will not be able to participate in it again.
+:::
+
+### Step 2: Check your subscription status!
+
+Go to [Smooth's website](https://smooth.dappnode.io/) and log in with your wallet. A list of all the validators with the same withdrawal address as your logged in wallet will appear. Once the validator proposes a block, it will appear as subscribed. We recommend you familiarize yourself with this website! It is the place where you will manage your validators going forward.
diff --git a/docs/smooth/subscribe-to-smooth/manual.md b/docs/smooth/subscribe-to-smooth/manual.md
new file mode 100644
index 000000000..a82fffcbe
--- /dev/null
+++ b/docs/smooth/subscribe-to-smooth/manual.md
@@ -0,0 +1,96 @@
+# Manual Subscription
+
+Would you rather not wait until your next proposed block to subscribe and begin earning rewards? You can take a proactive step and opt for manual subscription right away. During this process, you'll change your validator's fee recipient to Smooth's address, just like in the automatic subscription. However, instead of waiting for your next proposed block, you'll immediately start accumulating rewards from Smooth.
+
+The manual subscription is done through **[Smooth's website](https://smooth.dappnode.io/)**.
+
+### Step 1: Change your fee recipient to Smooth's address.
+
+Change the fee recipient of your validator to Smooth's address, just as if you were subscribing automatically. In Dappnode, this process is as simple as changing the fee recipient in your [staking brain](http://brain.web3signer.dappnode/).
+
+
+
+**This step is extremely important**. Make sure you're changing the fee recipient of the validators you are going to manually subscribe and that the fee recipient is correctly set to Smooth's address (`0xAdFb8D27671F14f297eE94135e266aAFf8752e35`). If a subscribed validator proposes a block with an incorrect fee recipient, it will be banned from Smooth and will not be able to participate in it again.
+
+:::danger Keep the fee recipient set to Smooth's address!
+It is crucial that you keep the fee recipient of your validator set to Smooth's address (`0xAdFb8D27671F14f297eE94135e266aAFf8752e35`) as long as it is subscribed to Smooth. If, at any point, you change the fee recipient of your validator and propose a block without unsubscribing first, you will be banned from Smooth and will not be able to participate in it again.
+:::
+### Step 2: Log in to Smooth's website.
+
+Go to [Smooth's website](https://smooth.dappnode.io/) and log in with your wallet. A list of all the validators with the same withdrawal address as your logged in wallet will appear.
+
+### Step 3: Select your validator .
+
+Select the validator you want to subscribe to Smooth by clicking on the "Subscribe" button.
+
+
+When clicking on the "Subscribe" button, Smooth will check if your validator is registered to any MEV relay. If it is, it will also check if the fee recipient of your validator is set to Smooth's address in each relay. **Three different dialogs can appear**, depending on the state of your validator and the MEV relays it is registered to.
+
+#### Scenario 1: Validator is not registered to any MEV relay.
+
+Does Smooth take my Consensus Layer (CL) rewards?
+ No, Smooth does not take your CL rewards. CL rewards are always sent directly to your withdrawal address. Smooth only takes the execution layer rewards, which are the fees or MEV of the blocks you propose. These are the rewards that are sent to the fee recipient. +
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+
\ No newline at end of file
diff --git a/docs/smooth/subscribe-to-smooth/overview.md b/docs/smooth/subscribe-to-smooth/overview.md
new file mode 100644
index 000000000..339f9c71e
--- /dev/null
+++ b/docs/smooth/subscribe-to-smooth/overview.md
@@ -0,0 +1,14 @@
+# Subscribing to Smooth
+
+Hello! In this section you will find all the information on how to subscribe your Validators to Smooth. Even though the process is simple, it is important to follow the steps carefully.
+
+:::danger Before subscribing to Smooth!
+Only validators with ETH1 withdrawal addresses can be subscribed to Smooth. If you have a validator with a BLS withdrawal address, please update it to an ETH1 withdrawal address before subscribing to Smooth.
+
+Ensure that you have control over the ETH1 withdrawal address of the validators you plan to subscribe to Smooth. This address is the one you will need to use when logging into Smooth's website and manage your validators going forward. Only the withdrawal address has the capability to claim rewards generated by your validators from Smooth.
+:::
+You have **two options** to subscribe to Smooth:
+
+1. [**Automatic subscription**](/docs/smooth/subscribe-to-smooth/automatic.md): The simplest way to subscribe, change the fee recipient of your validators to Smooth's address and subscribe automatically when proposing your next block!
+
+2. [**Manual subscription**](/docs/smooth/subscribe-to-smooth/manual.md): Change the fee recipient of your validators to Smooth's address and use the Smooth's website to subscribe right now, without waiting for your validators to propose a block. Start earning rewards right away!
diff --git a/docs/smooth/unsubscribe-from-smooth.md b/docs/smooth/unsubscribe-from-smooth.md
new file mode 100644
index 000000000..dda7efd83
--- /dev/null
+++ b/docs/smooth/unsubscribe-from-smooth.md
@@ -0,0 +1,36 @@
+# Unsubscribing from Smooth.
+
+Unsubscribing from Smooth is as simple as subscribing to it. You can unsubscribe from Smooth at any time, it is done through **[Smooth's website](https://smooth.dappnode.io/)** and it only takes one simple transaction.
+
+:::caution
+When unsubscribing a validator from Smooth, you will lose all pending rewards attached to it. We recommend unsubscribing just after successfully proposing a block, so lost pending rewards are minimized.
+:::
+
+## Step 1: Log in to Smooth's website.
+
+Go to [Smooth's website](https://smooth.dappnode.io/) and log in with your wallet. A list of all the validators with the same withdrawal address as your logged in wallet will appear.
+
+## Step 2: Click on the "Unsubscribe" button of the validator you want to unsubscribe.
+
+Once logged in, click on the "Unsubscribe" button of the validator you want to unsubscribe from Smooth.
+
+
+
+## Step 3: Follow the dialog instructions.
+
+I have changed my fee recipient but the "Fee recipient warning" warning still appears!
+ +If you have changed your fee recipient to Smooth's address (0xAdFb8D27671F14f297eE94135e266aAFf8752e35) but this warning still appears, it could be because of two reasons:
+-
+
- The relays you are registered to are not reflecting the change in the fee recipient yet. It can take up to a few minutes for the relays to reflect your fee recipient update. This is something that is out of Smooth's control. We recommend you to wait a few minutes and try again. +
- The fee recipient is only updated in your current active relays. This means that if you used to be registered to a relay, but you are not using it anymore, the fee recipient of your validator will not be updated in that relay. This is something expected and that it wont affect your validator's subscription to Smooth. If you want to update the fee recipient in the relays you are no longer registered to, you can quickly register and unregister again to the outdated relays to force an update the fee recipient there. +
+ 
+
+ 
+
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
- 
-
+ 
+
+
+
+Android
+ +1. Launch the OpenVPN for Android app. +2. Tap on "Import file". +3. Upload the `.ovpn` file you downloaded earlier. +4. Click on "Connect". +5. Allow the app to create a VPN connection. + +
+ 
+
+
+
+iPhone/iPad
+ +1. Go to the URL you obtained in the previous step. +2. Download the `.ovpn` file. +3. Click on "Open in OpenVPN". +4. Click on "Add". +5. Click on "Connect" +6. Allow the app to create a VPN connection. + +
+ 
+
+
+
+macOS
+ +1. Launch Tunnelblick app for macOS. +2. Click on "VPN Details" in the top bar menu. +3. Drag and drop the `.ovpn` file you downloaded earlier in the left side bar. +4. Click on Connect. + +
+ 
+
+
+
+Windows
+ +1. Launch the OpenVPN for Windows app. +2. Click on "Import file". +3. Upload the `.ovpn` file you downloaded earlier. +4. Allow the app to create a VPN connection. + +
+ 
+
+
+
+Recent Ubuntu
+ +1. Open Settings>Network. +2. Click on the "+" button to add a new VPN connection. +3. Select "Import from file". +4. Upload the `.ovpn` file you downloaded earlier. +5. Click on "Add". +6. Toggle the switch button to connect. + +
+ 
+
+ 
+
+
+
+Other Linux
+ +1. Open the terminal. +2. Navigate to the directory where you have stored your `.ovpn` file. +3. Execute the command: `sudo openvpn Dappnode_VPN.ovpn`. + ++ +:::tip Testing Your Connection +Once connected, you can directly type [http://my.dappnode](http://my.dappnode) in your browser to access the Dappmanager. +::: diff --git a/docs/user/access-your-dappnode/vpn/overview.md b/docs/user/access-your-dappnode/vpn/overview.md new file mode 100644 index 000000000..110092eb3 --- /dev/null +++ b/docs/user/access-your-dappnode/vpn/overview.md @@ -0,0 +1,28 @@ +# VPN Access to Dappnode + +Virtual Private Network (VPN) is a robust method for accessing your Dappnode. It ensures a secure and encrypted connection between your device and the Dappnode, allowing you to manage your Dappnode from virtually anywhere. Depending on your needs and preferences, Dappnode offers support for two primary VPN technologies: **WireGuard** and **OpenVPN**. + +:::note +It is not possible to use both Dappnode WiFi hotspot and VPN at the same time. If you want to use VPN, you'll need to disconnect your device from the WiFi hotspot. +::: + +## VPN Clients + +### [WireGuard](/docs/user/access-your-dappnode/vpn/wireguard) (Recommended) +- WireGuard is a newer, streamlined VPN protocol known for its simplicity, speed, and security. +- It requires less configuration and is considered more efficient in terms of CPU usage. [Learn more](https://www.wireguard.com/) + +### [OpenVPN](/docs/user/access-your-dappnode/vpn/openvpn) +- OpenVPN is a well-established VPN protocol praised for its security and reliability. +- It's more versatile and can bypass most network restrictions and firewalls. [Learn more](https://openvpn.net/) + +## Local vs. Remote Access + +- **Local Access**: Connecting to your Dappnode when you're on the same local network. Generally, this means that your Dappnode machine and the device you're using to access it are connected to the same router. + +- **Remote Access**: Connecting to your Dappnode from a different network or location. This is one of the major advantages of using a VPN. + +:::info +VPN provides a balance of security, versatility, and remote access capability. You can choose the VPN technology that best suits your needs and preferences, both fufill the requirements of most users. +::: + diff --git a/docs/user/access-your-dappnode/vpn/wireguard.md b/docs/user/access-your-dappnode/vpn/wireguard.md new file mode 100644 index 000000000..11bd26227 --- /dev/null +++ b/docs/user/access-your-dappnode/vpn/wireguard.md @@ -0,0 +1,169 @@ +# WireGuard Access to Dappnode + +WireGuard is a modern, high-performance VPN protocol that offers a simple and streamlined approach for securely accessing your Dappnode. This guide will walk you through setting up WireGuard with your Dappnode. + +You will need: +1. Your dappnode +2. A Wireguard client installed on your usual device (laptop, mobile, etc.) + +## Setting Up WireGuard + +### 1. Get VPN Credentials + +There are two primary methods to obtain your VPN credentials: + +#### Option 1: Via Dappmanager UI + + + + +If you have access to the Dappmanager: + +- Navigate to **VPN > WireGuard**. + + - **If you don't see any device added to the list:** + 1. Provide a name for your device. + 2. Click on 'Add New Device'. + + - **To retrieve the credentials:** + 1. Click on the 'Get Credentials' button. + 2. Copy the credentials displayed directly from the UI. + + - **For Local Access Credentials:** + 1. Click on 'Show Local Credentials'. + 2. Copy the local credentials displayed. + + +#### Option 2: Via Dappnode Terminal + +If you can't access the Dappmanager, you'll need to get the credentials via the Dappnode terminal: + +1. Access the Dappnode terminal, as explained [here](/docs/user/access-your-dappnode/terminal). + +2. Execute the command: `dappnode_wireguard`. + +3. The credentials will be displayed directly on the terminal. Copy these credentials. + + - **For Local Access Credentials:** + 1. Execute the command: `dappnode_wireguard --local`. + 2. Copy the local credentials displayed. + +:::info Local Credentials Explained +Local credentials allow you to establish a connection to your Dappnode when you are on the same local network. They are especially useful when remote credentials might not work due to certain network restrictions or configurations. + +While remote credentials enable access from outside your local network, local credentials ensure a reliable connection within your home or office network. It's recommended to use local credentials when you are in proximity to your Dappnode to guarantee a stable and swift connection. + +Always remember: Local credentials **only work inside your own network**. If you're trying to access your Dappnode from a different location or network, you'll need to use the remote credentials. +::: + + +:::tip +Ensure you store these credentials securely. They provide direct access to your Dappnode. Treat them with the same level of caution as you would a password. +::: + +### 2. Installing WireGuard Client + +After obtaining your VPN credentials, the next step is to install the WireGuard client. You can download the one that's compatible with the device you are going to use to connect to the Dappnode machine from the [WireGuard website](https://www.wireguard.com/install/). + +### 3. Setting Up WireGuard Client + +After installing the client: + +1. Launch the WireGuard application. +2. Click on 'Add Tunnel' or 'Import Tunnel from File' based on your platform. +3. Import the credentials you obtained in the earlier steps. +4. Once imported, connect to your Dappnode by activating the tunnel. + +:::tip Connection Status +You can verify your connection status within the WireGuard application. It will display if the tunnel is active, as well as data transfer rates. +::: + +### 4. Connecting to Dappnode via WireGuard + +
+
+
+Android
+ +1. Launch the OpenVPN for Android app. +2. Tap on "+" icon. +3. Select the option that fits you best to import the credentials: Scan QR code, Import file or Paste from clipboard to an empty profile. + +
+ 
+
+
+
+iPhone/iPad
+ +1. Launch the OpenVPN for Android app. +2. Tap on "Add a tunnel". +3. Select the option that fits you best to import the credentials: Scan QR code, Import file or Paste from clipboard to an empty profile. + +
+ 
+
+
+
+Linux
+ +1. Create a file for your credentials: `sudo nano /etc/wireguard/wg0.conf` +2. Paste your credentials there and save the file (Ctrl+Shift+V, Ctrl+O, Ctrl+X). +3. Activate the tunnel: `sudo wg-quick up wg0` + +:::note Tunnel Deactivation +To deactivate the tunnel, execute the command: `sudo wg-quick down wg0`. +::: + +
+
+
+macOS
+ +1. In the list of Applications, search for WireGuard and launch it. +2. Click on "Manage Tunnels". +3. Click on the "+" button. +4. Select "Add empty tunnel". +5. Paste the credentials you obtained earlier. +6. Give a name to this profile and click on "Save". +7. Click on "Activate" to connect to your Dappnode. + +
+ 
+
+ 
+
+
+
+Windows
+ +1. Launch the OpenVPN for Windows app. +2. Click on "Add Tunnel". +3. Paste the credentials you obtained earlier and save. +4. Activate the tunnel. + +
+ 
+
+ 
+
+ 
+
+ +:::tip Testing Your Connection +Once connected, you can directly type [http://my.dappnode](http://my.dappnode) in your browser to access the Dappmanager. +::: \ No newline at end of file diff --git a/docs/user/access-your-dappnode/wifi.md b/docs/user/access-your-dappnode/wifi.md new file mode 100644 index 000000000..4c3f5565f --- /dev/null +++ b/docs/user/access-your-dappnode/wifi.md @@ -0,0 +1,23 @@ +# Wi-Fi Access to Dappnode + +If you bought a Dappnode from our store, or installed Dappnode on a computer with a built-in Wi-Fi chip, you can easily connect to the **Dappmanager** (Dappnode web UI) using the Dappnode's Wi-Fi hotspot. + +For those who got their hardware elsewhere, there's a chance the Wi-Fi card might not be recognized by the operating system. If this happens, you might need to install the required firmware. Since the steps vary based on the hardware, please contact our support on Discord if you face any issues. + +## Connecting to Dappnode Wi-Fi + +1. 📱 On a device of your choice, navigate to the **Wi-Fi settings**. +2. 🔍 Search and select the network labeled as `DappnodeWIFI`. +3. 🔑 Enter the password: `dappnode`. +4. 🌐 Open a browser and go to http://my.dappnode/. + +:::caution +After connecting for the first time, go to the Wi-Fi section in the left menu of **Dappmanager** and change the hotspot password to something only you know. +::: + +## Wi-Fi Settings in Dappmanager + +Once in the Wi-Fi section, you'll find two main options: + +1. **Toggle Wi-Fi**: Here, you can turn the Wi-Fi feature on or off. +2. **Wi-Fi Credentials**: Set a new network name (SSID) and password for your Dappnode's Wi-Fi. We strongly advise you to change the default settings for better security. \ No newline at end of file diff --git a/docs/user/ethical-metrics/metrics.md b/docs/user/ethical-metrics/metrics.md new file mode 100644 index 000000000..8391605c9 --- /dev/null +++ b/docs/user/ethical-metrics/metrics.md @@ -0,0 +1,63 @@ +# Metrics Collected by Ethical Metrics + +Dappnode has absolutely no hidden telemetry and is completely private by design. We were reluctant of setting up a Monitoring Service because we did NOT want to collect any data from our users. Because of the request of our users to offer alerts, we came up with a private solution so we can offer alerts without compromising your privacy. + +Even if we cannot associate the metrics that your Dappnode sends with you, **we are fully committed to maintaining total transparency about the metrics we collect from your dappnode when using Ethical Metrics**. We want you to have a clear understanding of the information that is being monitored. The metrics we collect fall into several categories. Here's an overview of the metrics we gather. + +:::info +These metrics also help us better allocate resources by knowing what our users are running on their dappnodes. This way, we can better understand what packages are most popular and what packages need improvement. +::: + +:::note +Ethical Metrics is one of our newest packages and it is still under improvement. This section will be updated as we add or remove metrics. +::: + +## Dappnode host metrics + +These are all the metrics related directly to the host machine running your dappnode. All of these metrics are collected by the Dappnode Exporter package. +- `node_cpu_seconds_total`: Total CPU usage in seconds by the node. +- `container_memory_usage_bytes`: Memory usage in bytes by containers. +- `container_memory_cache`: Memory cache usage by containers. +- `node_memory_MemTotal_bytes`: Total memory available in bytes on the node. +- `node_memory_MemFree_bytes`: Free memory in bytes on the node. +- `node_memory_Buffers_bytes`: Memory used for buffers in bytes on the node. +- `node_memory_Cached_bytes`: Cached memory in bytes on the node. +- `node_disk_io_time_seconds_total`: Total disk I/O time in seconds on the node. +- `node_disk_reads_completed_total`: Total completed disk reads on the node. +- `node_disk_writes_completed_total`: Total completed disk writes on the node. +- `container_fs_usage_bytes`: Filesystem usage by containers in bytes. +- `node_filesystem_size_bytes`: Total size of the filesystem in bytes on the node. +- `node_filesystem_free_bytes`: Free space in the filesystem in bytes on the node. +- `container_last_seen`: Timestamp of the last seen container. +- `cadvisor_version_info`: Information about the cAdvisor version. +- `container_cpu_usage_seconds_total`: Total CPU usage in seconds by containers. + +## Dappmanager metrics +The following are all the metrics related to your dappnode configuration. These are all stored in your dappmanager. +- `dappmmanager_staker_config`: Your current staking package. +- `dappmanager_ipfs_client_target_local`: Wether IPFS client is in local or remote mode. +- `dappmanager_eth_fallback_enabled`: Wether the ethereum fallback client is enabled. +- `dappmanager_eth_client_target_local`: Wether ethereum client is in local or remote mode. +- `dappmanager_auto_updates_user_packages`: Wether auto updates for user packages is enabled. +- `dappmanager_auto_updates_system_packages`: Wether auto updates for system packages is enabled. +- `dappmanager_host_info`: Details including Docker and Docker Compose versions, kernel version, operating system version, and architecture type. + +## Staking Metrics +The following metrics are all related directly to the staking packages, including web3signer. +- `eth2_slashingprotection_prevented_signings`: Number of prevented slashing signings. +- `signing_signers_loaded_count`: Count of loaded validators signing in web3signer. +- `signing_bls_signing_duration`: Duration of BLS signing. +- `signing_bls_signing_duration_count`: Count of BLS signing durations. +- `signing_bls_signing_duration_sum`: Sum of BLS signing durations. +- `signing_bls_missing_identifier_count`: Count of missing BLS identifier. +- `api_rpc_cons_peers`: Number of connected peers to your staking execution clients. +- `api_rpc_exec_peers`: Number of connected peers to your staking consensus clients. +- `api_rpc_cons_syncing`: Wether your staking execution clients are syncing. +- `api_rpc_exec_syncing`: Wether your staking consensus clients are syncing. + + +To sum it up, the metrics we collect give us a peek into how your dappnode is doing, like how it uses resources, memory, disk, and even info related to staking. Rest assured, your privacy is of utmost importance to us, and all data transmission occurs through the TOR network to protect your privacy. + +:::note +For any questions or concerns about the metrics collected by Ethical Metrics, feel free to reach out to our support team. +::: \ No newline at end of file diff --git a/docs/user/ethical-metrics/notifications.md b/docs/user/ethical-metrics/notifications.md new file mode 100644 index 000000000..bbc809842 --- /dev/null +++ b/docs/user/ethical-metrics/notifications.md @@ -0,0 +1,13 @@ +# Notifications + +Ethical Metrics provides you with a range of notifications to keep you informed about the status and performance of your dappnode. These notifications are designed to help you proactively address any potential issues. Currently, the following notifications are available: + +1. **Dappnode Down Notification:** When your dappnode goes offline and is unable to send its metrics to our monitoring servers for an entire hour, you'll receive this notification. + +2. **Dappnode CPU Over 80% for 15 Minutes:** If your dappnode's CPU usage surpasses 80% for a continuous duration of 15 minutes, Ethical Metrics will send you a notification. This alert helps you identify instances where your dappnode's resources are nearing capacity. + +3. **Dappnode CPU Over 90% for 5 Minutes:** If your dappnode's CPU usage spikes above 90% and maintains this level for 5 consecutive minutes, you'll receive a notification. This alert enables you to respond promptly to high CPU utilization scenarios. + +:::note +We're committed to enhancing your monitoring experience, and we're continuously working to improve Ethical Metrics. In the future, we plan to introduce additional notifications to provide you with even more insights into your dappnode's health and performance. +::: diff --git a/docs/user/ethical-metrics/overview.md b/docs/user/ethical-metrics/overview.md new file mode 100644 index 000000000..823bb5ea9 --- /dev/null +++ b/docs/user/ethical-metrics/overview.md @@ -0,0 +1,70 @@ +# Ethical Metrics + +:::note +Ethical Metrics requires the [Dappnode Monitoring Service (DMS)](../packages/dms.md) as a dependency. +::: + +## Introduction + +When it comes to monitoring your dappnode, the [Dappnode Monitoring Service (DMS)](../packages/dms.md) offers valuable insights into the health and performance of your packages and system. Yet, there's a key thing that DMS can't do: **DMS can't notify you when your dappnode goes offline**. This limitation arises because DMS operates from within your dappnode, so it can't help when your dappnode experiences downtime. + +**Ethical Metrics solves this DMS limitation.** It is a service that allows for external monitoring of your dappnode externally **without leaking any identifying information**. This way, you will be able to recieve notifications when your dappnode goes offline and other useful cases, such as when your dappnode is at high CPU usage during an extended period of time or your disk space is running out. + +:::info +Ethical Metrics comes from the request of the users to have useful alerts and the strict compromise of Dappnode of preserving privacy for its users. +::: + +So, how did we manage to overcome the difficulty of monitoring your dappnode without compromising your privacy? In order to keep your privacy intact, **all the communication between your dappnode and our monitoring servers is done through the TOR network**. The TOR network is enables anonymous communication by directing Internet traffic via a free, worldwide, volunteer overlay network that consists of more than seven thousand relays. + +:::tip +In a nutshell, your dappnode signals that it's alive via a private channel so we don't know where it comes from. If it stops sending the signal that it's alive, we can assume that it's offline and send an alert to the email associated with that particular dappnode. This way, your dappnode's IP address remains hidden and nobody (not even us) can identify which metrics belong to who. +::: + +:::caution +To send alerts, it is necessary that you provide an alert where to send these alerts. In order to remain private, we recommend you to use an email address that can't be linked to your identity. For example, John Doe probably wouldn't want to use "JohnDoe@gmail.com" if he wanted to remain anoymous. +::: + +**To put it simply:** Ethical Metrics enables us to monitor a group of dappnode metrics for you. In the event that your dappnode goes offline, Ethical Metrics can send notifications to an email address you provide during installation. All this communication occurs via the TOR network, which guarantees the protection of your DappNode's IP address and the confidentiality of your metrics. + + + +:::info +Ethical metrics is one of our newest packages and it is still under constant improvement. Please come back to this page to check for updates on this package. +::: + +## Set-up Ethical Metrics + +In order to setup your Ethical Metrics notification system, you need to follow these steps: + +1. Navigate to http://my.dappnode/system/notifications +2. Introduce the email address where you want to receive the notifications and click on the switch to activate the notifications. +3. Thats it! Your ethical metrics will automatically register your tor instance with the email address you provided through the Tor network preserving your privacy. (you should have received a welcome email) + + + +
+ +## Troubleshooting + +
+
+
+How can I make sure my dappnode is registered?
+ + Upon registering, an email will be sent to your configured email address. If you don't receive this email, please check your spam folder. +
+
+
+How can I test a "dappnode down" notification?
+ + There are various ways to test a "dappnode down" notification. The easiest way is to stop your dappnode, but you can also test it by stopping the "prometheus" service of your Ethical Metrics package. After an hour, you should receive a "dappnode down" notification in your email. +
+
diff --git a/docs/user/faqs/index.md b/docs/user/faqs/index.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/docs/user/getting-started/access-dappnode-via-wifi.md b/docs/user/getting-started/access-dappnode-via-wifi.md
new file mode 100644
index 000000000..c2b3c629a
--- /dev/null
+++ b/docs/user/getting-started/access-dappnode-via-wifi.md
@@ -0,0 +1,38 @@
+# Access Dappnode via Wi-Fi
+
+After connecting your Dappnode to the router and power, and turning it on, it's time to connect to it.
+
+:::tip
+You **don't need** a monitor, keyboard, or mouse to use Dappnode. You just need to plug it to your router and you can access it from your laptop or mobile phone's browser!
+:::
+
+
+## 1. **Connect to DappnodeWIFI**:
+ - After a couple of minutes of being turned on, your dappnode will generate a WiFi hotspot
+ - From the device you wish to connect with, look for the Wi-Fi network named **DappnodeWIFI**.
+ - Connect using the default password: **dappnode**.
+
+ 
+
+## 2. **Access the Dappnode Interface**:
+ - Open your web browser.
+ - Navigate to: [http://my.dappnode/login](http://my.dappnode/login)
+
+## Troubleshooting:
+
+How can I unregister from the Ethical Metrics monitoring system?
+ +1. Using the Dappnode Interface: For an active Dappnode, simply navigate to System > Notifications and toggle off Ethical Metrics. This will stop all notifications and halt metric collection from your Dappnode. As long as Ethical Metrics notifications are enabled in the Dappnode UI, your device remains registered in our monitoring system.
+ +2. For Inactive Dappnodes: If your Dappnode is no longer accessible, locate the unregister link in the welcome email you received upon registration. Keep in mind that using this method won't employ our IP hiding measures, but you can enhance security using tools like a VPN. Please keep in mind that if your DAppNode is still up and running with Ethical Metrics notifications turned on, it'll register again by itself.
+ +3. Manual Unregistration: Lost the welcome email? You can also unregister by inputting the following URL into your browser: https://ethical-metrics.dappnode.io/unregister-from-email/?instance=YOUR_INSTANCE.onion%3A9090. Make sure to replace YOUR_INSTANCE with the unique identifier for your Dappnode, excluding ".onion:9090", which is already included in the provided URL.
+
+
+How can I change my Dappnode Wi-Fi password?
+ To change the Wi-Fi password: + + 1. While connected to the Dappnode, go to Wi-Fi Settings + + 2. Enter your new desired password in both the "New Password" and "Confirm New Password" fields. + + 3. Click on "Change Credentials". + +
+
diff --git a/docs/user/getting-started/choose-your-path.md b/docs/user/getting-started/choose-your-path.md
new file mode 100644
index 000000000..5eecc8583
--- /dev/null
+++ b/docs/user/getting-started/choose-your-path.md
@@ -0,0 +1,21 @@
+# Choose your path
+
+Regardless of how you wish to utilize Dappnode, taking the initiative to contribute to decentralization and earning rewards is commendable. Embark on your desired path and experience the full potential of Dappnode.
+
+:::note
+Interested in purchasing a Dappnode? Explore our official store.
+:::
+
+I can't access my Dappnode via Wi-Fi
+ You can explore other methods to access your Dappnode here. +
+
+ 
+ 
+
diff --git a/docs/user/getting-started/connect-dappnode-to-the-router.md b/docs/user/getting-started/connect-dappnode-to-the-router.md
new file mode 100644
index 000000000..4ed388b66
--- /dev/null
+++ b/docs/user/getting-started/connect-dappnode-to-the-router.md
@@ -0,0 +1,47 @@
+# Connect your dappnode to the router and power
+
+Dappnode offers a seamless plug-and-play experience. For optimal performance and to ensure smooth operation, please connect your Dappnode to your router and enable UPnP settings within the router.
+
+
+
+Make sure you also connect your Dappnode to a power outlet and you are ready to turn it on.
+
+## Enable UPnP in your router
+
+Enabling UPnP (Universal Plug and Play) on a router allows devices on your network to set up port forwarding rules for themselves automatically. This simplifies device communication and functions, especially for applications that require open ports, like some games and peer-to-peer programs.
+
+Here are basic instructions to enable UPnP on most routers:
+
+1. **Log into Your Router**: Open a web browser on a computer connected to your network.
+ Enter your router's IP address in the address bar. Common addresses include 192.168.1.1, 192.168.0.1, or 10.0.0.1. If you're unsure of your router's IP, you can check your device's network settings or consult the router's manual.
+ You'll be prompted for a username and password. If you haven't changed them, the default details are usually admin/admin, admin/password, or some similar combination. Refer to your router's documentation if you're unsure.
+
+2. **Navigate to the UPnP Section**: Once logged in, look for a section labeled "UPnP", often found under "Advanced Settings", "WAN", "NAT", or similar categories. The exact path can vary based on the router manufacturer and model.
+
+3. **Enable UPnP**: There should be an option to enable or disable UPnP. Make sure it's set to "Enable" or "On".
+ Save or apply the changes.
+
+
+ Dappnode is installed
+I have bought a Dappnode or I already installed it
+ + + +
+ I want to install Dappnode
+I own a machine where I want to install Dappnode software
+ ++ +### Troubleshooting + +
+
+How can I verify that the ports were successfully opened by UPnP?
+ +Access your dappnode support > ports view and execute an API scan of the ports. + +An alternative is to manually check if the ports have been opened successfully, follow these steps: + +1. Use an online port checker tool, like "YouGetSignal" or "Canyouseeme." +2. Enter your external IP address and the port number you want to check. +3. Click "Check." If the port is open and accessible from the outside, the tool will confirm it. + +Alternatively, you can use tools like `nmap` to scan your own ports from a different network. + +
+
diff --git a/docs/user/getting-started/next-steps.md b/docs/user/getting-started/next-steps.md
new file mode 100644
index 000000000..ecbdbecf1
--- /dev/null
+++ b/docs/user/getting-started/next-steps.md
@@ -0,0 +1,9 @@
+# Next Steps
+
+Now that your DAppNode is set up and ready to go, it's time to explore further configurations and features to get the most out of your experience. Here are some of the most common next steps:
+
+[**🔐 Configure VPN access**](/docs/user/access-your-dappnode/vpn/overview): Using either Wireguard or OpenVPN, you will be able to connect to your Dappnode from wherever you are in the world. You will be able to access your dappnode outside of the range of the wifi, while on holidays or during your commute!
+
+[**💰 Start Staking and Earning Rewards**](/docs/user/staking/overview.md): You can start validating Proof-of-Stake networks like Ethereum, Gnosis Chain or LUKSO and earn rewards for securing the network.
+
+[**🔔 Configure Ethical Metrics**](docs/user/ethical-metrics/overview.md): Ethical metrics is a privacy-focused monitoring tool for Dappnode. You will be able to receive alerts related to your Dappnode's performance and health.
diff --git a/docs/user/getting-started/register.md b/docs/user/getting-started/register.md
new file mode 100644
index 000000000..2bbb3d7a7
--- /dev/null
+++ b/docs/user/getting-started/register.md
@@ -0,0 +1,70 @@
+# Register
+
+## 1. Register as New User
+
+Start by setting up your new account:
+
+1. **Input** your desired **Username**.
+2. **Select a secure password**. It should include a combination of characters, numbers, and special symbols for optimal security.
+3. **Confirm your password** to ensure accuracy.
+4. Click the **Register** button.
+
+Why can't I connect my DappNode to the router via Wi-Fi?
+ +Currently, Dappnode doesn't support Wi-Fi connections to a router. Ensure your Dappnode is connected directly to the router using an ethernet cable. + +
+ 
+
+ 
+
+ 
+
+
+
+Want to change your password?
+Visit Profile Settings to reset it. +
+
+
+Forgot your password?
+Go to the Login page and click on "Forgot your password?". You'll be prompted to enter the recovery token you saved during registration. Once entered, you'll be able to reset your password. +
+
diff --git a/docs/user/getting-started/setup.md b/docs/user/getting-started/setup.md
new file mode 100644
index 000000000..3932fb1a0
--- /dev/null
+++ b/docs/user/getting-started/setup.md
@@ -0,0 +1,63 @@
+# Setup
+
+Setting up Dappnode is a straightforward process. This guide will walk you through configuring your Dappnode for the first time.
+
+
+
+## Choose Repository Source
+
+
+
+Before you dive in, choose the source from which Dappnode retrieves its data:
+
+- **Remote Node**: Connect your Dappnode to an external Ethereum node. This option is lightweight, as you won't need to host the blockchain data on your machine.
+
+- **Full Node**: Have your Dappnode host the complete Ethereum blockchain. This ensures maximum decentralization and independence, but it requires more storage and bandwidth.
+
+:::info Why is this important?
+Dappnode uses smart contracts to publish the dapps that are accessible in the dappstore. For this reason, Dappnode needs access to an Ethereum node to read the contents of said smart contract. Choosing between a remote and a full node directly impacts how decentralized your setup is.
+
+**Decentralization Benefits**: By relying less on third-party services, you enhance security, reduce points of failure, and support the Ethereum network's robustness, but it might not work for you if you have limited storage or bandwidth.
+:::
+
+## Enable/Disable System Auto Updates
+
+Dappnode comes with an auto-update feature. This means it will automatically update itself with new releases, ensuring you always have the latest and most secure version. Activate auto-updates to lessen maintenance and better guard against vulnerabilities.
+
+
+
+:::tip
+We **strongly** recommend activating auto-updates to ensure your Dappnode is always up to date with the latest versions.
+:::
+
+## Enable system notifications
+
+Dappnode can send you notifications about important events, such as your dappnode being offline or high CPU usage. This is a great way to stay on top of your Dappnode's health and performance.
+
+
+
+## Change Host User Password
+
+Beneath the hood, Dappnode operates on a Linux framework, protected by a password, which will be needed to access your [Dappnode's terminal](/docs/user/access-your-dappnode/terminal) To amplify your Dappnode's defense:
+
+1. **Change** the **default Linux** machine **password** for user `dappnode`.
+2. Choose a **strong, unique password** that's not easily guessable.
+3. Remember to **store this password in a secure location**. If you lose access to this password, you could be locked out of your Dappnode.
+
+:::caution
+Always save and backup your password. This is crucial for ensuring uninterrupted access to your Dappnode.
+:::
+
+
+
+## All Set!
+
+Congratulations! Your Dappnode is now configured and ready for use. Dive into the world of decentralized applications and enjoy the self-hosted, decentralized internet experience.
+
+With these steps, your Dappnode should be up and running efficiently. Always refer to the official Dappnode documentation or community for any further queries or support.
+
+:::info Keep your Dappnode up to date
+Remember to regularly check for updates and best practices to ensure your Dappnode stays secure and efficient.
+:::
+
+
diff --git a/docs/user/install/arm.md b/docs/user/install/arm.md
new file mode 100644
index 000000000..6e2789639
--- /dev/null
+++ b/docs/user/install/arm.md
@@ -0,0 +1,42 @@
+# Install - ARM
+
+## Hardware Recommendations
+
+- 8 Gb RAM memory
+- Screen and keyboard (Only for the first installation)
+- Wired connection to the Dappnode
+
+## Install Dappnode via Script
+
+Follow the instructions you can find in [Script Installation](/docs/user/install/script)
+
+## Add an external SSD
+
+In case you have installed Dappnode in a Raspberry using a SD card and you want to add an external SSD you should mount docker data in it. To do this, follow the next steps:
+
+- Stop Docker service
+ `systemctl stop docker`
+
+- Create a new mountpoint for docker data. As an example:
+ `mkdir /data`
+
+- Add your partition on the new device to `/etc/fstab`. You can identify its UUID using the `blkid` tool. Make sure your device is properly partitioned first. Your line in `/etc/fstab` should look like this:
+ `UUID=b311b983-bda6-4e9f-835c-266d40d64f07 /data/ ext4 defaults 0 0`
+
+- Mount your SSD drive
+ `mount /data`
+
+- Move docker data to the mountpoint
+ `mv /var/lib/docker/* /data/`
+
+- Edit Docker settings to use the alternative location. Edit `/etc/docker/daemon.json` as follows:
+
+```json
+{
+ "data-root": "/data"
+}
+```
+
+- Restart docker
+
+`systemctl start docker`
diff --git a/docs/user/install/dappnode-commands.md b/docs/user/install/dappnode-commands.md
new file mode 100644
index 000000000..b0f9cafc8
--- /dev/null
+++ b/docs/user/install/dappnode-commands.md
@@ -0,0 +1,44 @@
+# Dappnode commands
+
+Dappnode comes with a set of commands that can be used to manage the system. These commands can be used directly from the command line.
+
+
+
+:::tip
+Go to the [Access your Dappnode's terminal](/docs/user/access-your-dappnode/terminal) section to learn more about how to access the terminal.
+:::
+
+Below is a list of available commands in Dappnode:
+
+- `dappnode_help`: prints out this message
+
+- `dappnode_wifi`: get wifi credentials (SSID and password)
+
+- `dappnode_openvpn`: get Open VPN credentials
+
+- `dappnode_wireguard`: get Wireguard VPN credentials. Use `dappnode_wireguard --help` for more info
+
+- `dappnode_connect`: check connectivity methods available in Dappnode
+
+- `dappnode_status`: get status of dappnode containers
+
+- `dappnode_start`: start dappnode containers
+
+- `dappnode_stop`: stop dappnode containers
+
+To run a command, enter it in your Dappnode terminal. For example:
+
+```bash
+dappnode_help
+```
+
+Lost your recovery token?
+If you've lost your recovery token, there is still a chance to regain access to the Dappmanager UI. However, you will require accessing via terminal. Once you are in, you can get your recovery token by running the following command: + +```bash +cat /usr/src/dappnode/DNCORE/admin-recovery-token.txt +``` + +
+
diff --git a/docs/user/install/iso.md b/docs/user/install/iso.md
new file mode 100644
index 000000000..eed28a79a
--- /dev/null
+++ b/docs/user/install/iso.md
@@ -0,0 +1,65 @@
+# ISO Installation
+
+When you want to perform a clean installation by installing the base operating system and Dappnode. Installing from an ISO will wipe the machine data and install Dappnode over Debian.
+
+## Get the ISO
+
+You can get the image downloading directly from [Dappnode ISO](https://github.com/dappnode/Dappnode/releases) or if you prefer you can build it from the [source](https://github.com/dappnode/Dappnode#install-dappnode-with-iso).
+
+:::note Attended VS Unattended ISO
+
+- **Attended ISO**: An attended ISO installation involves a manual setup process where the user must be present to make choices, answer prompts, and guide the installation through its various stages. It provides more control over the configuration, allowing for customization based on specific needs.
+
+- **Unattended ISO**: The unattended ISO installation is an automated process where pre-defined settings are used to install Dappnode without user intervention. This is ideal for straightforward installations where default configurations are preferred. It speeds up the process and ensures consistency in the setup.
+
+Consider your specific requirements and the level of customization you need when deciding between these two installation methods.
+:::
+
+
+## Burn the ISO in a USB
+
+Burn the ISO to an USB stick. To do so we recommend using [Balena Etcher](https://www.balena.io/etcher/) for the OS with which you will prepare the USB to boot from your server and install Dappnode.
+
+:::danger
+If you trigger the installation in a machine containing data, all existing data will be erased.
+:::
+
+## Boot from the USB
+
+After burning the ISO to the USB stick:
+
+1. **Insert** the USB stick into the machine where you want to install Dappnode.
+2. **Reboot** the machine.
+3. During the boot process, access the **boot menu** (the key to press varies depending on the machine manufacturer; commonly used keys include F2, F10, F12, ESC, or DEL).
+4. **Select** the USB stick as the boot device.
+
+The machine should now boot from the USB, and you'll see the Dappnode installation interface.
+
+## Follow the Installation Prompts
+
+- If you've chosen the **Attended ISO**, you'll be presented with a series of prompts asking for configuration details and preferences. Follow the on-screen instructions and provide the necessary input to proceed.
+
+- If you've opted for the **Unattended ISO**, the installation will proceed automatically, using predefined settings.
+
+:::tip Default Credentials
+If you're using the Unattended ISO, the default credentials are:
+
+**user**: `dappnode`
+
+**pass**: `dappnode.s0`
+:::
+
+## Final Steps
+
+Once the installation is complete:
+
+1. **Remove** the USB stick.
+2. **Reboot** the machine (you might need to do this twice)
+3. On startup, Dappnode should be running. You can check it by executing `docker ps` in the terminal and some of the [Dappnode Commands](/docs/user/install/dappnode-commands)
+4. Finally, you can begin the post-installation setup and configuration.
+
+:::info
+Remember to keep your Dappnode running 24/7 for optimal performance, especially if you are hosting blockchain nodes or other continuous services.
+:::
+
+Congratulations! You've successfully installed Dappnode using the ISO method. For any further assistance or troubleshooting, always refer to the official Dappnode documentation or community support.
diff --git a/docs/user/install/overview.md b/docs/user/install/overview.md
new file mode 100644
index 000000000..ffb651321
--- /dev/null
+++ b/docs/user/install/overview.md
@@ -0,0 +1,44 @@
+# Installation Overview
+
+## Specifications & Minimum Requirements
+Dappnode is a Debian-based OS, which makes it friendly with most available commercial hardware. Depending on what you intend to run in your Dappnode you might need higher specifications, but a great number of available features can be used with the following recommendations:
+- Intel Core i5/i7
+- 32 GB RAM
+- 4 TB NVMe storage
+
+As minimum requirements we recommend:
+- Intel Core i3
+- 16 GB RAM
+- 2 TB NVMe or fast SSD storage
+
+If you don't have enough technical experience to customize your own hardware, remember you can always get a plug n play [Dappnode Home](https://dappnode.com/collections/all) in our online shop.
+
+## Installation Methods
+
+Installing Dappnode can be achieved through two primary methods:
+
+### 1. [ISO Installation](/docs/user/install/iso)
+- **Description**: This method involves downloading the Dappnode ISO file and using it to directly install Dappnode on your system.
+- **Best for**: Most users as it provides a comprehensive setup designed specifically for Dappnode.
+
+### 2. [Script Installation](/docs/user/install/script) over Debian-based Distribution
+- **Description**: If you're already running a Debian-based distribution, you can utilize the Dappnode script to facilitate the installation process.
+- **Best for**: Users who want to install Dappnode on a cloud server, ARM device (where it's the only option), or those who desire a specific Debian-based distro.
+
+:::note
+For ARM-based systems, only the script installation method is available.
+:::
+
+Choose the method that best fits your needs and system setup. Make sure to follow the respective installation instructions carefully for a smooth and successful Dappnode deployment.
+
+:::caution Continuous Uptime
+
+Dappnode is designed to run 24/7. Many features and functions within Dappnode, especially blockchain nodes, rely on continuous uptime to maintain their state, sync, and functionality. For instance:
+
+- **Blockchain Nodes**: If you have a synced blockchain node and you turn off Dappnode, the node will lose its sync. This means when you turn it back on, it'll take time to catch up to the latest state, which can be resource-intensive and time-consuming.
+
+- **Validator Nodes**: For users staking on certain blockchain networks, continuous uptime is crucial. Being offline might result in missed opportunities or even penalties.
+
+Considering these aspects, it's recommended to ensure your Dappnode device remains powered on and running at all times.
+:::
+
diff --git a/docs/user/install/script.md b/docs/user/install/script.md
new file mode 100644
index 000000000..1f64955bb
--- /dev/null
+++ b/docs/user/install/script.md
@@ -0,0 +1,49 @@
+# Script installation
+
+You can install Dappnode using the installation script. In this case, we recommend you use Ubuntu or Debian as your operating system.
+
+## Prerequisites
+
+Before installing Dappnode, you need to install some prerequisites:
+
+- [Docker](https://docs.docker.com/install/)
+- [Docker-compose](https://docs.docker.com/compose/install/)
+- [xz](https://packages.debian.org/sid/xz-utils)
+
+To install all the above prerequisites, execute the command below in the terminal of the machine you want to install Dappnode. If you already have the dependencies installed or you want to install them on your own you can skip this step.
+
+```bash
+sudo wget -O - https://prerequisites.dappnode.io | sudo bash
+```
+
+## Install Dappnode
+
+To install Dappnode, execute the next script:
+
+```bash
+sudo wget -O - https://installer.dappnode.io | sudo bash
+```
+
+## Reboot
+
+To finalize the installation once it has finished completing, reboot your machine (you might need to do this twice):
+
+```bash
+shutdown -r now
+```
+
+## Restore to the latest version
+
+If you are experiencing any problem or just want to make sure you are running the latest Dappnode versions, execute this command in the Dappnode terminal. This will update the core packages to the latest versions without erasing any data from your volumes.
+
+```bash
+sudo wget -O - https://installer.dappnode.io | sudo UPDATE=true bash
+```
+
+## Uninstall
+
+This command will uninstall Dappnode components (but not docker et al.).
+
+```bash
+wget -qO - https://uninstaller.dappnode.io | sudo bash
+```
diff --git a/docs/user/packages/MysteriumVPN b/docs/user/packages/MysteriumVPN
new file mode 100644
index 000000000..5d7a06c78
--- /dev/null
+++ b/docs/user/packages/MysteriumVPN
@@ -0,0 +1,5 @@
+# MysteriumVPN
+Mysterium will let you earn passive income by making your bandwidth available through a VPN.
+
+### Disclaimer
+This package allows you to share your bandwidth with other users of the Mysterium network. Depending on your country, there might be laws restricting the websites you can visit. Kindly keep in mind that Dappnode is not responsible for any internet activity happening through your bandwidth via this package. Mysterium offers an option for accepting only whitelisted traffic. Please read their FAQ to know more about Mysterium's network encryption, whitelisting policy and exit node guidance.
diff --git a/docs/user/packages/avalanche.md b/docs/user/packages/avalanche.md
new file mode 100644
index 000000000..4dfd6663c
--- /dev/null
+++ b/docs/user/packages/avalanche.md
@@ -0,0 +1,14 @@
+# Avalanche
+
+## Avalanche: A Revolutionary Consensus Protocol
+Avalanche is an innovative open-source platform designed for launching decentralized finance applications and enterprise blockchain deployments within a single, highly scalable ecosystem. Developers leveraging Avalanche’s capabilities can effortlessly craft robust, secure applications and tailor-made blockchain networks. This platform empowers them to construct intricate rulesets or build atop existing private or public subnets, ultimately driving the creation of reliable and impactful solutions.
+
+## AVAX Staking on Dappnode: Earn Rewards while supporting Avalanche Network
+
+:::info
+A guide to running an Avalanche validator node on Dappnode is coming soon. In the meantime, you can find more information on the [Avalanche website](https://www.avalabs.org/).
+:::
+
+By running an Avalanche node on Dappnode, you actively participate in the decentralization of the network. Through this engagement, you contribute to the security and reliability of Avalanche’s consensus model.
+
+Engage in AVAX staking to contribute to the security and decentralization of the Avalanche network. Stake your AVAX tokens to become a delegator or validator, and in return, earn rewards for your participation in the Proof of Stake consensus mechanism. With a minimum of 2000 AVAX tokens required to start a validator, AVAX staking presents an opportunity to support the network while earning rewards.
\ No newline at end of file
diff --git a/docs/user/packages/bitcoin.md b/docs/user/packages/bitcoin.md
new file mode 100644
index 000000000..d221d9892
--- /dev/null
+++ b/docs/user/packages/bitcoin.md
@@ -0,0 +1,10 @@
+# Bitcoin
+
+## Exploring Bitcoin: The Pioneer of Cryptocurrency
+Bitcoin, the first and most well-known cryptocurrency, is a digital asset that introduced the concept of blockchain technology to the world. Created by an anonymous person or group under the pseudonym Satoshi Nakamoto, Bitcoin revolutionized the financial landscape by offering a decentralized and borderless form of value transfer.
+
+## Running a Bitcoin Node on Dappnode and Supporting the Network
+Running a Bitcoin node on Dappnode allows you to actively participate in the Bitcoin network’s operations. As a node operator, you help validate transactions, maintain a copy of the blockchain, and contribute to the network’s overall security and resilience. Operating a Bitcoin node not only benefits the network by enhancing its decentralization but also provides you with an opportunity to engage with the technology that powers the cryptocurrency revolution.
+
+## Bitcoin’s Role in Decentralization: A Decade of Innovation
+Bitcoin’s journey over the past decade has been marked by remarkable advancements and widespread adoption. As the original cryptocurrency, Bitcoin has demonstrated the potential of blockchain technology to disrupt traditional financial systems. Its decentralized nature, limited supply, and transparent ledger have positioned it as a store of value and a medium of exchange. By running a Bitcoin node on Dappnode, you contribute to the continued success and decentralization of the Bitcoin network.
\ No newline at end of file
diff --git a/docs/user/packages/dms.md b/docs/user/packages/dms.md
new file mode 100644
index 000000000..2f8a34cf3
--- /dev/null
+++ b/docs/user/packages/dms.md
@@ -0,0 +1,51 @@
+# Dappnode Monitoring Service (DMS)
+
+As a Dappnode user, there are times when having insights into the performance of your packages or your whole system can be incredibly beneficial. This means understanding the condition or "health" of your packages, the utilization of your computer resources such as CPU, RAM, and disk space, as well as monitoring network traffic flow. Yet, managing all of these aspects can become complex and tedious, even for those with experience. This is precisely where the Dappnode Monitoring Service (DMS) steps in to simplify matters.
+
+## How It All Works
+
+DMS acts as a strong monitoring solution, simplifying the complex task of monitoring your packages and system by automatically collecting all available data and visualizing it for you. But how does it achieve this? DMS primarily comprises two key components: Prometheus and Grafana. Let's break it down
+
+1. **Prometheus Integration:** DMS seamlessly incorporates [Prometheus](https://prometheus.io/), a comprehensive monitoring toolkit. Prometheus is responsible of gathering all data coming from other Dappnode packages. This information is the foundation for understanding your package's performance.
+
+2. **Grafana Dashboards:** To transform raw data coming from Prometheus into meaningful insights, DMS brings in [Grafana](https://grafana.com/), renowned for its exceptional data visualization capabilities. Through customizable dashboards, you gain instant access to both real-time and historical perspectives on how your packages are functioning.
+
+:::info
+💡 While DMS can monitor data from your installed packages on its own, we highly recommend installing the **Dappnode Exporter** package as well. This package expands DMS's capabilities to monitor critical Dappnode system metrics, such as network traffic, CPU, RAM, and disk usage. Moreover, it unlocks new Grafana dashboards that visualize this data for your convenience. You can easily find the Dappnode Exporter in your DAppStore.
+:::
+
+**Your Privacy Matters:**
+
+At Dappnode, we respect your privacy. Rest assured that all the metrics collected by DMS are stored locally, ensuring your information remains private and secure.
+
+## Installing and accessing DMS
+
+Locate DMS in your DAppStore, listed among the Featured packages. The installation process is straightforward, much like any other Dappnode package. After installation, you can access DMS Grafana and explore all its dashboards by visiting http://dms.dappnode.
+
+## Monitoring through Dashboards
+
+As explained in the [official Grafana documentation](https://grafana.com/docs/grafana/latest/dashboards/), Grafana simplifies data visualization through organized views known as dashboards. In the context of Dappnode, many packages, especially our staker packages, come equipped with pre-built Grafana dashboards that seamlessly integrate into DMS upon installation. These dashboards are designed to provide specific insights into the performance of the corresponding packages. To explore the range of available Grafana dashboards within DMS, follow these simple steps:
+
+
+1. **Accessing Dashboards:** Find the "Dashboards" icon on the left-hand side of the DMS interface and hover your mouse over it. Click on "Browse" to proceed.
+I get the error "command not found"
+ +If you get the error `command not found` when trying to execute a dappnode command, it means that the command is not available in your system. You need to load the dappndoe profile as follows: + +```bash +source /usr/src/dappnode/DNCORE/.dappnode_profile +``` + +
+
+ 
+
+
+2. **Dashboard Folders:** In the dashboard browsing view, you'll see different dashboard folders. Each folder contains one or more dashboards related to specific aspects of your Dappnode environment. For instance, let's click on the "Docker" dashboard provided by the **Dappnode Exporter** package.
+
+ 
+
+3. **Exploring a Dashboard:** That's it! You are now within the chosen dashboard, such as the "Docker" dashboard. Here, you'll find valuable information about all your installed packages, including relevant metrics and performance indicators.
+
+ 
+
+As you navigate through these Grafana dashboards, it's worth mentioning that the [official Grafana documentation](https://grafana.com/docs/grafana/latest/) provides a wealth of information about dashboards, visualization techniques, and best practices. Exploring this documentation can greatly enhance your ability to interpret and utilize the data presented in DMS dashboards. Whether you're new to Grafana or seeking advanced tips, the official documentation is a valuable resource for maximizing your monitoring experience.
+
+:::info
+💡 If you're looking for specific dashboards beyond what comes pre-installed, [Grafana's dashboard repository](https://grafana.com/grafana/dashboards/) makes it easy to search and import dashboards created by the community.
+:::
+
+Feel free to check out the different dashboard folders and adjust how things look based on what you like. Grafana offers a bunch of cool features, so have fun exploring and making the dashboards work just right for you!
+
diff --git a/docs/user/packages/ethclassic.md b/docs/user/packages/ethclassic.md
new file mode 100644
index 000000000..010c24124
--- /dev/null
+++ b/docs/user/packages/ethclassic.md
@@ -0,0 +1,6 @@
+# Ethereum Classic
+## Introducing Ethereum Classic: Preserving Blockchain Principles
+Ethereum Classic, a steadfast blockchain, emerged from the Ethereum chain split, committed to upholding the unwavering principles of blockchain immutability. Ethereum Classic champions the preservation of transaction history and decentralized governance.
+
+## Ethereum Classic on Dappnode: Supporting Decentralization
+Step into the Ethereum Classic universe and become a steward of its principles. Ethereum Classic’s commitment to blockchain origins offers a space for decentralized ideals to thrive. Through an Ethereum Classic node on Dappnode, you contribute to the preservation of an ecosystem where code remains law and history remains unaltered.
\ No newline at end of file
diff --git a/docs/user/packages/monero.md b/docs/user/packages/monero.md
new file mode 100644
index 000000000..b62ea0922
--- /dev/null
+++ b/docs/user/packages/monero.md
@@ -0,0 +1,7 @@
+# Monero
+
+## Introducing Monero: A Privacy-Centric Cryptocurrency
+Monero stands as a privacy-focused cryptocurrency with a core focus on anonymity and transaction fungibility. Monero uses innovative cryptographic techniques to obscure transaction details, making it difficult to trace the sender, receiver, and transaction amount.
+
+## Monero’s Package on Dappnode
+By running a Monero node in Dappnode, you play a crucial role in supporting the decentralized nature of the Monero ecosystem. You actively contribute to the decentralization of the network, playing a role in shaping a financial ecosystem that values privacy and security.
\ No newline at end of file
diff --git a/docs/user/packages/swarm.md b/docs/user/packages/swarm.md
new file mode 100644
index 000000000..816ae31d9
--- /dev/null
+++ b/docs/user/packages/swarm.md
@@ -0,0 +1,48 @@
+# Guide to Installing Bee Node on Dappnode
+
+## Introduction to Swarm
+Swarm is a decentralized data storage and distribution technology. Ready to power the next generation of censorship-resistant, unstoppable, serverless dApps.
+
+Node operators can [stake BZZ](https://docs.ethswarm.org/docs/bee/working-with-bee/staking/#stake-your-node-with-bee) to participate in the redistribution of funds, allowing Bee node operators to receive BZZ in return for providing storage and bandwidth.
+
+Node operators are rewarded with BZZ tokens, the native ERC-20 token.
+
+Beyond earning rewards, the Bee node serves as your personalized gateway to the Swarm network, offering you interactive access to content and dApps hosted on Swarm. The app enables you to:
+
+- Securely store (upload and download) files on Swarm's decentralized storage.
+- Share files privately and securely with others.
+- Host and manage HTML websites conveniently.
+
+## Introduction to Dappnode
+DappNode is a decentralized platform that serves as critical infrastructure for launching and managing decentralized applications (dApps) with an essence of providing users with self-sovereign data management and secure, uncensorable application interfaces.
+
+Node operators on DappNode can gain enhanced control over their participation in various blockchain networks and ensure that their activities, whether it be validating transactions, participating in consensus mechanisms, or supporting network security, are conducted in a seamless, autonomous manner.
+
+The unique DappNode ecosystem ensures:
+
+- Seamless deployment and management of decentralized applications and nodes.
+- Enhanced user control over data and privacy.
+- Autonomous and secure participation in various blockchain networks.
+- Simplification of running blockchain nodes, reducing technical barriers for participants.
+
+## Gnosis Chain
+Swarm uses [Gnosis Chain](https://www.gnosis.io/), formerly known as xDai, for managing its incentives.
+
+Therefore, the Swarm Bee client necessitates a connection to the Gnosis Chain. As such, we recommend installing Nethermind (direct Dappnode install link) as your RPC endpoint.
+
+## Installing a Bee node
+Step 1: Navigate to the package installer — [Install Swarm](http://my.dappnode/installer/public/swarm.public.dappnode.eth)(direct Dappnode install link). Click Install to initiate the installation.
+
+Step 2: Setup optional parameters:
+- **Swap RPC Endpoint (Gnosis Chain)** — if you installed Nethermind and are running your own node, you can leave the default settings. Otherwise, if you use an external RPC endpoint, this is where you should set it.
+- **ENS resolver RPC (Ethereum Mainnet)** — As bee can resolve ENS (a special type of blockchain name), it requires an Ethereum mainnet RPC endpoint. Install links are available for a variety of clients, or you can use an Infura RPC endpoint, or alternatively leave it blank to disable the ENS resolver.
+- **Initial chequebook deposit (xBZZ)** — is the amount of xBZZ the bee node must have deposited to its address in order to deploy the chequebook. You have the option to set this to 0 and deposit BZZ into the chequebook later via the UI.
+- **Welcome message** — some graffiti that you can admire at Swarm Scan or if you happen to be peering through the logs
+- **Full node mode** — must be set to true or false, in order to stake and participate in storage incentives, and subsequently be rewarded, it should be set to true
+- **Storage data mountpoint** — for advanced users; recommended to leave at default.
+
+### Engage in Storage Incentives by Staking Your BZZ
+1. Import your gift code into Metamask or another web3 wallet on Gnosis chain. Remember, the gift code is a private key that holds 12 BZZ and 0.12xDAI.
+2. Transfer funds to your Node wallet address, which can be found in the logs or at Swarm UI/Account/[Wallet](http://dashboard.swarm.public.dappnode/#/account/wallet).
+3. Visit Account/[Staking](http://dashboard.swarm.public.dappnode/#/account/staking).
+4. Click on 'Stake', input an amount of 10 BZZ, and then press the 'Stake' button.
\ No newline at end of file
diff --git a/docs/user/repository/ethereum.md b/docs/user/repository/ethereum.md
new file mode 100644
index 000000000..a1c741705
--- /dev/null
+++ b/docs/user/repository/ethereum.md
@@ -0,0 +1,55 @@
+# Ethereum repository
+
+Dappnode uses smart contracts to distribute the dappnode packages available in the Dappstore. The smart contracts are deployed in the Ethereum blockchain and the Dappnode client interacts with them to get the list of available packages and to download them. Your dappnode will need a connection to an Ethereum node in order to read the smart contracts and download the packages. There are two ways to establish this connection:
+
+- **Full Node**: By running a Full Node, you host the Ethereum blockchain. This ensures maximum control and independence, but requires syncing and maintaining the blockchain's latest state.
+
+- **Remote Node**: Using a Remote Node means relying on an external Ethereum node. It's less resource-intensive but demands trust in the node operator.
+
+
+:::tip
+To configure your dappnode Ethereum repository go to http://my.dappnode/repository/eth
+:::
+
+## Run your own Ethereum node
+
+When choosing to run your own Ethereum node, you will need to select:
+
+1. **Execution client**
+2. **Consensus client**
+
+Moreover, it is **highly recommended to enable** these additional options:
+
+3. **Use remote during syncing or errors**: If enabled, this will auto-switch from your Local node to the Dappnode Remote node under certain conditions. For instance, if your Ethereum node is syncing or if it's unavailable for some reason. Activating this option ensures uninterrupted access to the Dappnode smart contracts even if there's an issue with your Local node.
+
+4. **Use checkpointsync**: By enabling this, your consensus client will utilize a checkpoint to fast-track the syncing of the Ethereum blockchain, making the process much quicker quicker.
+
+:::caution
+Making changes here will also modify selections in the [Stakers](http://my.dappnode/stakers) tab.
+:::
+
+
+
+:::caution
+Running your own Ethereum node requires a lot of resources. You will need a powerful machine with a lot of storage and a good internet connection. If you don't have a powerful machine, you can use a remote Ethereum node.
+:::
+
+## Use a remote Ethereum node
+
+You can use a remote Ethereum node to connect to the Ethereum network. You will need to trust the node operator.
+
+
+
+:::note
+At the moment, we only support Dappnode official Ethereum node. We are working on a way to allow users to add their own remote Ethereum nodes RPC endpoints. See https://github.com/dappnode/DNP_DAPPMANAGER/issues/1245
+:::
+
++ +### Troubleshooting + +
+
diff --git a/docs/user/repository/ipfs.md b/docs/user/repository/ipfs.md
new file mode 100644
index 000000000..392286f2f
--- /dev/null
+++ b/docs/user/repository/ipfs.md
@@ -0,0 +1,85 @@
+# IPFS repository
+
+Dappnode leverages IPFS for distributing packages available in the Dappstore. To download these packages, your Dappnode requires a connection to an IPFS node. When it comes to connecting to the IPFS network, you have two primary choices:
+
+- **Run Your Own IPFS Node**: By opting for this, you maintain full control, ensuring that you directly access the distributed packages without intermediaries. However, it might require some disk space.
+- **Use a Remote Node**: This is a convenient option, but it comes with the caveat of needing to trust the remote node operator. It is really useful in case your own IPFS node becomes unreliable or unavailable.
+
+:::tip
+To configure your dappnode IPFS repository go to http://my.dappnode/repository/ipfs
+:::
+
+## Run your own IPFS node
+
+You can run your own IPFS node to connect to the IPFS network. This is the recommended option for those users who want to have full control over their dappnode. Dappnode comes with an IPFS node preinstalled and configured. You can access the [IPFS Web UI](http://ipfs.dappnode:5001/webui) while connected to your Dappnode.
+
+
+
+:::caution
+Running your own IPFS node may affect your internet connection. If you don't want to run your own IPFS node, you can use a remote IPFS node. Consider stopping your IPFS node if you are not using it at [IPFS Package](http://my.dappnode/packages/system/ipfs.dnp.dappnode.eth/info)
+:::
+
+## Use a remote IPFS node
+
+You can use a remote IPFS node gateway to connect to the IPFS network. You will need to trust the node operator. Dappnode provides an [Official IPFS gateway](https://gateway.ipfs.dappnode.io) by default, but you can choose any other IPFS gateway.
+
+
+
+:::note IPFS gateways and security
+
+Connecting to IPFS remote gateways could entail security risks. For example, the gateway could attempt to serve malicious content to the user. We mitigate this risk by verifying the content downladed with [CID technology](https://docs.ipfs.io/concepts/content-addressing/).
+
+If the Dappnode IPFS gateway is not available (we make no uptime guarantees and we offer it on a best-effort basis) the user can set another IPFS gateway in the input field as last resort. Check out all the [IPFS gateways available](https://ipfs.github.io/public-gateway-checker/)
+:::
+
+Why did my clients change in the Full Node Repository selection?
+ + At the moment, Dappnode only supports running one Ethereum mainnet node. If you change your selection in the [Stakers](http://my.dappnode/stakers/ethereum) menu, it will also change in the [Repository](http://my.dappnode/repository/eth) menu. ++ +### Troubleshooting + +
+
+
+I can't see the logos of the packages in the Dappstore/Stakers tab. Why?
++ +This might be related to an issue with IPFS. Try the following solutions: + +1. **IPFS Mode**: + + - Navigate to the [repository](http://my.dappnode/repository/ipfs). + - Toggle between `local` and `remote` IPFS modes to see which one works. + +2. **IPFS Package Status**: + + - If your IPFS mode is set to `local`, ensure that the IPFS package is running. + - Visit [IPFS Package](http://my.dappnode/packages/system/ipfs.dnp.dappnode.eth/info) to verify its status and click on "Start" if it is stopped. + - If it's restarting, consider updating the IPFS package to its latest version. Post update, remove its volumes to address any potential database migration issues. + +3. **Gateway Validity**: + - For `remote` IPFS mode, make sure the gateway URL in the [repository](http://my.dappnode/repository/ipfs) is correct. + +
+
+
diff --git a/docs/user/rollups/optimism.md b/docs/user/rollups/optimism.md
new file mode 100644
index 000000000..2507b3fc8
--- /dev/null
+++ b/docs/user/rollups/optimism.md
@@ -0,0 +1,22 @@
+# Optimism Rollup
+
+Optimism is Ethereum's Layer 2 solution, leveraging Optimistic Rollups to enhance transaction speeds and lower costs. It conducts transactions off-chain, reconciling final states on the main Ethereum chain, all while preserving compatibility with Ethereum smart contracts.
+
+
+
+## Setting Up an Optimism Node
+
+Optimism stands out as the inaugural choice in the Rollups suite. Initiating an Optimism node on Dappnode parallels the familiar Stakers Menu, yet with some distinctions:
+
+- Utilize an `op-node` client to link with the Optimism Mainnet.
+- Employ `op-geth` or `op-erigon` to bridge your `op-node` to Ethereum's execution layer, echoing the beacon chain/consensus client's role on the mainnet.
+- For archive nodes, `op-legacy` is essential for transactions predating the Bedrock upgrade.
+- A connection to an Ethereum Mainnet node is required. If your Dappnode already operates one, the Rollups menu will streamline configuration. Otherwise, integrate a public RPC for Ethereum Mainnet connection.
+
+For a deeper dive, consult Optimism’s documentation:
+
+- [OP Geth docs](https://op-geth.optimism.io/)
+
+- [Test In Prod - OP Erigon](https://github.com/testinprod-io/op-erigon)
+
+- [OP Node Operator](https://community.optimism.io/docs/developers/bedrock/node-operator-guide/)
diff --git a/docs/user/rollups/overview.md b/docs/user/rollups/overview.md
new file mode 100644
index 000000000..ad81eb895
--- /dev/null
+++ b/docs/user/rollups/overview.md
@@ -0,0 +1,15 @@
+# Ethereum Rollups: An Overview
+
+Rollups are advanced layer-2 scaling solutions designed to increase the throughput of the Ethereum network. By executing and storing transaction data off the main Ethereum chain while keeping a cryptographic commitment on-chain, Rollups enhance scalability and reduce fees. Rollups can be broadly categorized into two types: Optimistic Rollups and zk-Rollups, each with its unique approach and trade-offs.
+
+Currently, we support:
+
+- [**:four_leaf_clover: Optimism**](/docs/user/rollups/optimism): An optimistic Layer 2 solution for Ethereum, enhancing speed and efficiency.
+
+## Enable rollups
+
+To enable this feature, you need to switch on the rollups module in the top bar of the Dappnode UI (Dappmanager):
+
+I'm using local IPFS and encountering issues downloading packages. What should I do?
++ +This could arise from various factors: + +1. **Internet Connection**: + + - Your connection might be unstable. Consider switching your IPFS node mode to `lowpower` by accessing [IPFS config](http://my.dappnode/packages/system/ipfs.dnp.dappnode.eth/config). + +2. **Disk Space**: + + - Your local IPFS node might be out of storage. + - Clear the storage by opting for "Remove volumes" at [IPFS package info](http://my.dappnode/packages/system/ipfs.dnp.dappnode.eth/info). + +3. **Dappnode Official Gateway as Peer**: + + - Ensure that the Dappnode Official Gateway is added as a peer to your local IPFS. + - You can add it directly by clicking [here](http://my.dappnode/system/add-ipfs-peer/%2Fdns4%2Fipfs.dappnode.io%2Ftcp%2F4001%2Fipfs%2FQmfB6dT5zxUq1BXiXisgcZKYkvjywdDYBK5keRaqDKH633). + +**Tip**: If these solutions don't resolve the issue, switch to the `remote IPFS mode` at [IPFS repository](http://my.dappnode/repository/ipfs). + +
+
+ 
+
- 
-
- 
-
-
-
- 
-
- 
-
+
+ );
+}
+
+export default function HomepageFeatures(): JSX.Element {
+ return (
+
+ {isSvg ? (
+ 
+ )}
+
+
+
+ {title}
+{description}
+
+
+
+ {FeatureList.map((props, idx) => (
+
+
+
+ {siteConfig.title}
+{siteConfig.tagline}
+
+ {crashCourseVideos
+ .filter((video) => video.featured)
+ .map((video, index) => (
+
+ {activeVideo && (
+ handleVideoClick(video)}
+ >
+
+
+
+ ))}
+
+
+ )}
+
+
+
+
+