manual, update new pr

This commit is contained in:
Mik-TF
2024-05-14 17:06:21 -04:00
parent cf82a6f7b9
commit 4228ae6e1a
23 changed files with 326 additions and 83 deletions

View File

@@ -437,7 +437,7 @@ There are only a few steps needed to update the Farmerbot to a new release.
## Can't Find the Logs
If you can't find the logs of the Farmerbot, make sure that you ran the bot before! Once the Farmerbot runs, it should print logs in a file called `farmerbot.log` in the directory where it is running.
If you can't find the logs of the Farmerbot, make sure that you ran the bot before! Once the Farmerbot runs, it prints logs in a file called `farmerbot.log` in the directory where it is running.
You can try a search for any files under the home directory with the `.log` extension in case it's been moved:
@@ -445,6 +445,8 @@ You can try a search for any files under the home directory with the `.log` exte
find ~/ -name '*.log'
```
If you've deleted the log file while the bot is running, the bot won't recreated it. In this case, you will need to restart the bot, e.g. `systemctl restart farmerbot`. The bot will then automatically create a log file.
# Questions and Feedback
If you have questions concerning the Farmerbot, feel free to ask for help on the [ThreeFold Forum](https://forum.threefold.io/) or on the [ThreeFold Farmer chat](https://t.me/threefoldfarmers).

View File

@@ -231,7 +231,7 @@ power:
periodic_wake_up_start: 01:00PM
```
Note that if the user wants to include all the nodes within a farm, they can simply omit the `included_nodes` section. In this case, all nodes of the farm will be included in the Farmerbot, as shown in the example below:
Note that if the user wants to include all the nodes within a farm, they can simply omit the `included_nodes` section. In this case, all nodes of the farm will be included in the Farmerbot, as shown in the example below. If you are proceeding like this, make sure that you don't have any unused node IDs on your farm, as the Farmerbot would try to wake up nodes that aren't running anymore on the grid.
```
farm_id: 1

View File

@@ -23,6 +23,7 @@ To buy a certified node from an official ThreeFold vendor, check the [ThreeFold
- [Room Parameters](farm_room_parameters.md)
- [Farming Costs](farming_costs.md)
- [Calculate Your ROI](calculate_roi.md)
- [Farming Requirements](farming_requirements.md)
- [Advanced Networking](advanced_networking_toc.md)
- [Networking Overview](networking_overview.md)
- [Network Considerations](network_considerations.md)

View File

@@ -10,4 +10,5 @@ The section [Build a 3Node](3node_building.md) covered the notions necessary to
- [Minting Periods](minting_periods.md)
- [Room Parameters](farm_room_parameters.md)
- [Farming Costs](farming_costs.md)
- [Calculate Your ROI](calculate_roi.md)
- [Calculate Your ROI](calculate_roi.md)
- [Farming Requirements](farming_requirements.md)

View File

@@ -0,0 +1,28 @@
<h1> Farming Requirements </h1>
<h2> Table of Contents </h2>
- [Introduction](#introduction)
- [Uptime Requirements](#uptime-requirements)
- [Farmerbot Consideration](#farmerbot-consideration)
---
## Introduction
This section contains information on the farming requirements.
## Uptime Requirements
To be eligible for proof-of-capacity farming rewards, farmers need to ensure that their nodes have a minimum uptime per minting period.
- 95% uptime requirements for DIY nodes
- This means that nodes have 36 hours of allowed downtime per month
- 98% uptime requirements for certified nodes
- This means that nodes have 14.4 hours of allowed downtime per month
A minting period is 720 hours.
### Farmerbot Consideration
When minting considers a node running the Farmerbot, it counts standby time as uptime, as long as the node is healthy. If the node fails to wake within 24 hours, those 24 are deducted. This means that if the node misses two different wakeup within 24 hours, it will not have sufficient uptime for this minting period. This accounts for both certified and DIY cases.