Develop TF V4 Farming Pool Procedures and Documentation #122

New Issue

mik-tf · 2024-11-01T14:51:08Z

mik-tf commented

2024-11-01 14:51:08 +00:00

Situation

TF V4 will have farming pool

TODO

Define clear procedures and documentation for farming pools on V4

Tasks

Define SLA's, T&C's, Customer Onboarding, ...
Support (replace broken nodes)
Management infrastructure (monitoring, billing, ...)
Sales of The Nodes (or work with vendor(s))
Communication with the Farmers in the Pool
Price Definition (define sales prices of the slices)

Specs

Every V4 nodes need to be in a farming pool

# Situation - TF V4 will have farming pool # TODO - Define clear procedures and documentation for farming pools on V4 # Tasks - Define SLA's, T&C's, Customer Onboarding, ... - Support (replace broken nodes) - Management infrastructure (monitoring, billing, ...) - Sales of The Nodes (or work with vendor(s)) - Communication with the Farmers in the Pool - Price Definition (define sales prices of the slices) # Specs - Every V4 nodes need to be in a farming pool

mik-tf added the

Story

label 2024-11-01 14:51:08 +00:00

mik-tf added this to the ThreeFold V4 project 2024-11-01 14:51:08 +00:00

mik-tf referenced this issue

2024-11-01 16:56:25 +00:00

TF V4 Implementation Project Overview #119

despiegk was assigned by mik-tf

2024-11-01 16:57:59 +00:00

mik-tf self-assigned this 2024-11-01 16:58:43 +00:00

despiegk was unassigned by mik-tf

2024-11-01 16:58:50 +00:00

despiegk commented

2024-11-05 02:31:34 +00:00

we should not interfere with work of a farming pool, we could recommend certain things but its not up to us to run their business

👍 1

mik-tf removed their assignment 2024-11-28 16:01:55 +00:00

mik-tf modified the project from ThreeFold V4 to tfgrid_4_0

2024-12-16 18:36:22 +00:00

mik-tf commented

2024-12-18 21:44:25 +00:00

That is good. Then it means we just need to define clearly the basic of a farming pool, and we let farming pools take it from there. But it still means we need to define a little bit further, IMO.

Are the specs above sufficient? We might just need to expand on each part:

Define SLA's, T&C's, Customer Onboarding, ...
Support (replace broken nodes)
Management infrastructure (monitoring, billing, ...)
Sales of The Nodes (or work with vendor(s))
Communication with the Farmers in the Pool
Price Definition (define sales prices of the slices)

That is good. Then it means we just need to define clearly the basic of a farming pool, and we let farming pools take it from there. But it still means we need to define a little bit further, IMO. Are the specs above sufficient? We might just need to expand on each part: Define SLA's, T&C's, Customer Onboarding, ... Support (replace broken nodes) Management infrastructure (monitoring, billing, ...) Sales of The Nodes (or work with vendor(s)) Communication with the Farmers in the Pool Price Definition (define sales prices of the slices)

mik-tf commented

2024-12-18 21:57:59 +00:00

Update

@RobertJan
@nelson

Define SLA's, T&C's, Customer Onboarding, ...
- TF works on basic SLC, T&C needed, ETA end of December
- Farming pool add their parts
Support (replace broken nodes)
- TF has general support for the grid
  - software
- Manufacturers provide support for hardware
  - farming pools + manufacturers collaborate
Management infrastructure (monitoring, billing, ...)
- The billing is done on chain
- The monitoring of the general grid is done by TF
- The monitoring of the farming pool nodes is done by farming pools
  - TF can provide docs and procedures to help monitoring nodes
Sales of The Nodes (or work with vendor(s))
- Manufacturers work with farming pools to expand and add nodes
Communication with the Farmers in the Pool
- Farmers need to give info to join a farming pool
  - The farming pool can them communicate with the farmers
Price Definition (define sales prices of the slices)
- The coop gives a min and max
- The farmers and farming pools decide within the range

# Update @RobertJan @nelson - Define SLA's, T&C's, Customer Onboarding, ... - TF works on basic SLC, T&C needed, ETA end of December - Farming pool add their parts - Support (replace broken nodes) - TF has general support for the grid - software - Manufacturers provide support for hardware - farming pools + manufacturers collaborate - Management infrastructure (monitoring, billing, ...) - The billing is done on chain - The monitoring of the general grid is done by TF - The monitoring of the farming pool nodes is done by farming pools - TF can provide docs and procedures to help monitoring nodes - Sales of The Nodes (or work with vendor(s)) - Manufacturers work with farming pools to expand and add nodes - Communication with the Farmers in the Pool - Farmers need to give info to join a farming pool - The farming pool can them communicate with the farmers - Price Definition (define sales prices of the slices) - The coop gives a min and max - The farmers and farming pools decide within the range

RobertJan commented

2025-02-24 10:00:33 +00:00

SLA draft proposal:

Service Level Agreement (SLA) – Node Pool

1. Introduction
This Service Level Agreement (SLA) outlines the responsibilities and obligations of node owners (“Farmers”) participating in the Node Pool of YourData Network (“The Pool”). By joining, Farmers agree to the following terms.

2. Purpose of the Pool
The Pool acts as an intermediary between Farmers and customers who purchase capacity. The Pool provides guarantees to customers, such as 99% uptime, and supports Farmers in case of incidents and monitoring.
For Farmers, participating in the Pool offers a key advantage: the likelihood of their node being chosen by a customer is significantly higher than that of an 'anonymous' node outside the Pool. This increases the chances of usage and, consequently, higher earnings in tokens. Customers generally prefer nodes within a Pool due to the guarantees and support provided, meaning that Farmers in the Pool have a greater potential for returns. Additionally, Farmers benefit from centralized monitoring and support, allowing technical issues to be detected and resolved more quickly.
Farmers are allowed to set their own pricing for the use of their node, within a pricing range established by the Pool. This ensures a fair market environment where Farmers can remain competitive while maintaining a stable pricing structure.

3. Obligations of the Farmer
• The Farmer guarantees a minimum uptime of 99% per month.
• The Farmer ensures a stable and properly functioning node, including adequate cooling, power supply, and network connectivity.
• Any scheduled maintenance must be reported to the Pool at least 48 hours in advance.
• The Farmer must respond to Pool notifications about disruptions within 12 hours and cooperate to resolve the issue quickly.

4. Obligations of the Pool
• The Pool monitors the availability and performance of connected nodes.
• The Pool communicates disruptions and maintenance needs with Farmers.
• The Pool serves as a point of contact for customers and coordinates communication between Farmers and customers.
• The Pool may temporarily remove nodes from the pool in cases of repeated non-compliance with the uptime requirement.
• The Pool provides support to improve node performance if necessary.
• The Pool sets a pricing framework within which Farmers can determine their rates.
• The Pool implements a Know Your Customer (KYC) procedure to protect Farmers from fraudulent activities and to ensure security within the Pool.

5. Sanctions and Exclusion
• If uptime drops below 99% without valid reason, the Pool reserves the right to temporarily or permanently exclude the Farmer.
• Repeated non-compliance may result in termination of participation without compensation.

6. Term and Termination
• This agreement remains valid as long as the Farmer participates in the Pool.
• Termination can be initiated by either party with a 30-day notice period.
• In cases of repeated non-compliance, the Pool may terminate the agreement immediately.

7. Miscellaneous
• This SLA may be periodically revised by the Pool. Farmers will be notified in advance of any changes.
• Participation in the Pool implies acceptance of the applicable terms.

Signature
By signing, the Farmer agrees to the terms of this SLA.
Farmer’s Name: ________________________
Date: ________________________
Signature: ________________________

SLA draft proposal: Service Level Agreement (SLA) – Node Pool **1. Introduction** This Service Level Agreement (SLA) outlines the responsibilities and obligations of node owners (“Farmers”) participating in the Node Pool of YourData Network (“The Pool”). By joining, Farmers agree to the following terms. **2. Purpose of the Pool** The Pool acts as an intermediary between Farmers and customers who purchase capacity. The Pool provides guarantees to customers, such as 99% uptime, and supports Farmers in case of incidents and monitoring. For Farmers, participating in the Pool offers a key advantage: the likelihood of their node being chosen by a customer is significantly higher than that of an 'anonymous' node outside the Pool. This increases the chances of usage and, consequently, higher earnings in tokens. Customers generally prefer nodes within a Pool due to the guarantees and support provided, meaning that Farmers in the Pool have a greater potential for returns. Additionally, Farmers benefit from centralized monitoring and support, allowing technical issues to be detected and resolved more quickly. Farmers are allowed to set their own pricing for the use of their node, within a pricing range established by the Pool. This ensures a fair market environment where Farmers can remain competitive while maintaining a stable pricing structure. **3. Obligations of the Farmer** • The Farmer guarantees a minimum uptime of 99% per month. • The Farmer ensures a stable and properly functioning node, including adequate cooling, power supply, and network connectivity. • Any scheduled maintenance must be reported to the Pool at least 48 hours in advance. • The Farmer must respond to Pool notifications about disruptions within 12 hours and cooperate to resolve the issue quickly. **4. Obligations of the Pool** • The Pool monitors the availability and performance of connected nodes. • The Pool communicates disruptions and maintenance needs with Farmers. • The Pool serves as a point of contact for customers and coordinates communication between Farmers and customers. • The Pool may temporarily remove nodes from the pool in cases of repeated non-compliance with the uptime requirement. • The Pool provides support to improve node performance if necessary. • The Pool sets a pricing framework within which Farmers can determine their rates. • The Pool implements a Know Your Customer (KYC) procedure to protect Farmers from fraudulent activities and to ensure security within the Pool. **5. Sanctions and Exclusion** • If uptime drops below 99% without valid reason, the Pool reserves the right to temporarily or permanently exclude the Farmer. • Repeated non-compliance may result in termination of participation without compensation. **6. Term and Termination** • This agreement remains valid as long as the Farmer participates in the Pool. • Termination can be initiated by either party with a 30-day notice period. • In cases of repeated non-compliance, the Pool may terminate the agreement immediately. **7. Miscellaneous** • This SLA may be periodically revised by the Pool. Farmers will be notified in advance of any changes. • Participation in the Pool implies acceptance of the applicable terms. Signature By signing, the Farmer agrees to the terms of this SLA. Farmer’s Name: ________________________ Date: ________________________ Signature: ________________________

❤️ 1

RobertJan commented

2025-02-24 10:02:53 +00:00

We are setting up a corperation too. Despite not mandatory, we are considering making it a requirement to join the corporation (for service, tutorials etc.) ' if' they want to join a Pool. Therefore we think a pool should be a no-brianer, but still a choice and not mandatory.

Sign in to join this conversation.