init projectmycelium
This commit is contained in:
mik-tf
122
specs/3nodes.md
Normal file
122
specs/3nodes.md
Normal file
@@ -0,0 +1,122 @@
|
||||
# 3Nodes
|
||||
|
||||
3Nodes are physical computing hardware (servers, computers) that can be bought and sold within the TF Marketplace using TFP. Users can purchase 3Nodes in two distinct ways: either hosted by the supplier or physically transferred to the buyer.
|
||||
|
||||
## Core Principles
|
||||
|
||||
- **Hardware Exchange**: Direct marketplace for physical computing equipment
|
||||
- **Sovereignty**: Buyers gain full ownership of purchased hardware
|
||||
- **Fair Pricing**: Market-driven pricing with transparency
|
||||
- **TFP-Based**: All transactions conducted using TFP
|
||||
- **Quality Assurance**: Hardware specifications verified and rated
|
||||
- **Flexible Ownership**: Options for hosted or physically transferred hardware
|
||||
- **Upfront Payments**: One-time TFP payment for both ownership models
|
||||
|
||||
## How It Works
|
||||
|
||||
### For Sellers
|
||||
|
||||
- **Hardware Registration**:
|
||||
- Register available hardware with detailed specifications
|
||||
- Upload verification photos and documentation
|
||||
- Set pricing in TFP
|
||||
- Define shipping options and costs
|
||||
|
||||
- **Listing Management**:
|
||||
- Update hardware availability
|
||||
- Modify pricing based on market conditions
|
||||
- Respond to buyer inquiries
|
||||
- Track sales and shipping
|
||||
|
||||
### For Buyers
|
||||
|
||||
- **Hardware Discovery**:
|
||||
- Browse available 3Nodes with filtering options
|
||||
- Compare specifications and pricing
|
||||
- Review seller ratings and history
|
||||
- Ask questions about specific hardware
|
||||
|
||||
- **Purchase Options**:
|
||||
- **Option 1: Supplier-Hosted 3Nodes**
|
||||
- Buy the 3Node with upfront TFP payment but have it hosted in the supplier's facility
|
||||
- Maintain ownership while the supplier handles physical maintenance
|
||||
- Revenue sharing model where the hoster (who is also the seller) gets part of the farming revenue
|
||||
- Hoster/seller defines the revenue share percentage
|
||||
- Ideal for buyers without suitable hosting facilities
|
||||
|
||||
- **Option 2: Physical Transfer**
|
||||
- Buy the 3Node with upfront TFP payment and have it physically shipped to your location
|
||||
- Complete physical control and responsibility for the hardware
|
||||
- Suitable for buyers with their own hosting capabilities
|
||||
|
||||
- **Purchase Process**:
|
||||
- Select desired 3Node and purchase option (hosted or transferred)
|
||||
- Pay upfront using TFP for either option
|
||||
- For physical transfer: arrange shipping and delivery
|
||||
- For hosted option: receive access credentials
|
||||
- Verify functionality and condition
|
||||
|
||||
## Hardware Specifications
|
||||
|
||||
3Nodes can include various types of computing hardware:
|
||||
|
||||
- **Servers**: Enterprise-grade rack servers
|
||||
- **Desktop Computers**: Repurposed or custom-built desktops
|
||||
- **Mini PCs**: Compact computing devices
|
||||
- **Custom Builds**: Purpose-built hardware for TF Grid farming
|
||||
|
||||
Each listing includes detailed specifications:
|
||||
|
||||
- CPU type and core count
|
||||
- Memory capacity and type
|
||||
- Storage capacity and type
|
||||
- Network interfaces
|
||||
- Power consumption
|
||||
- Physical dimensions
|
||||
- Age and condition
|
||||
|
||||
## TFP Exchange Mechanism
|
||||
|
||||
- **Suppliers**: Hardware owners selling their equipment
|
||||
- **Consumers**: Users looking to acquire physical computing hardware
|
||||
- **Exchange Process**:
|
||||
- **For Physically Transferred Hardware**:
|
||||
- TFP transferred from buyer to seller upon purchase agreement
|
||||
- Escrow system protects both parties during shipping
|
||||
- Final release upon confirmed delivery and verification
|
||||
|
||||
- **For Supplier-Hosted Hardware**:
|
||||
- Upfront TFP payment to secure ownership
|
||||
- Revenue sharing agreement between buyer and hoster/seller
|
||||
- Hoster defines and receives a portion of farming revenue
|
||||
- Clear SLAs define uptime and performance guarantees
|
||||
|
||||
## Benefits
|
||||
|
||||
- **Direct Exchange**: No intermediaries between hardware sellers and buyers
|
||||
- **Ecosystem Growth**: Facilitates expansion of the TF Grid through hardware redistribution
|
||||
- **Resource Optimization**: Gives new life to underutilized hardware
|
||||
- **Sovereignty**: Buyers gain full ownership of their hardware, regardless of hosting location
|
||||
- **Flexibility**: Choose between hosted or physically transferred hardware based on needs
|
||||
- **Community Building**: Connects hardware providers with potential farmers
|
||||
|
||||
## Integration with TF Grid
|
||||
|
||||
- Hardware purchased can be registered as farming nodes
|
||||
- Seamless pathway to becoming a resource provider
|
||||
- Technical support available for setting up purchased hardware
|
||||
- Community resources for optimizing hardware performance
|
||||
|
||||
## Hosting vs. Physical Transfer Comparison
|
||||
|
||||
| Aspect | Supplier-Hosted | Physical Transfer |
|
||||
|--------|----------------|-------------------|
|
||||
| **Physical Location** | Supplier's facility | Buyer's location |
|
||||
| **Payment Model** | Upfront TFP payment | Upfront TFP payment |
|
||||
| **Revenue Sharing** | Yes - hoster gets portion of farming revenue | No - buyer keeps 100% of farming revenue |
|
||||
| **Maintenance** | Handled by supplier | Buyer's responsibility |
|
||||
| **Power & Cooling** | Provided by supplier | Buyer's responsibility |
|
||||
| **Internet Connectivity** | Provided by supplier | Buyer's responsibility |
|
||||
| **Physical Access** | Limited or none | Complete |
|
||||
| **Setup Complexity** | Minimal (handled by supplier) | Buyer must set up |
|
||||
| **Best For** | Users without hosting facilities | Users with hosting capabilities |
|
||||
171
specs/apps.md
Normal file
171
specs/apps.md
Normal file
@@ -0,0 +1,171 @@
|
||||
# TF Grid Self-Healing Applications
|
||||
|
||||
The TF Grid ecosystem includes a range of self-healing applications that provide alternatives to traditional centralized services. These applications operate on a unique model where the App Service provider manages the applications while using the customer's slices, ensuring sovereignty and reliability.
|
||||
|
||||
## Core Principles
|
||||
|
||||
- **Sovereignty**: Users maintain ownership of their data and infrastructure
|
||||
- **Self-Healing**: Applications automatically recover from failures
|
||||
- **Decentralization**: No single point of control or failure
|
||||
- **Privacy**: Data remains under user control
|
||||
- **Reliability**: Continuous monitoring and automated recovery
|
||||
|
||||
## Application Development Approaches
|
||||
|
||||
- **Native Development**:
|
||||
- Applications built specifically for the TF Grid
|
||||
- Designed from the ground up for decentralized operation
|
||||
- Optimized for the Mycelium network architecture
|
||||
- Integrated with TF Grid monitoring and self-healing capabilities
|
||||
|
||||
- **Open Source Integration**:
|
||||
- Adaptation of existing open source solutions
|
||||
- Modified to work with TF Grid infrastructure
|
||||
- Enhanced with self-healing capabilities
|
||||
- Integrated with monitoring and backup systems
|
||||
|
||||
## Example Applications
|
||||
|
||||
- **Collaborative Office Suite** (GDrive Alternative):
|
||||
- Document, spreadsheet, and presentation creation and editing
|
||||
- Real-time collaboration capabilities
|
||||
- Version control and history
|
||||
- Integration with Mycelium Names for sharing
|
||||
- End-to-end encryption for security
|
||||
|
||||
- **Communication Platform** (Zoom Alternative):
|
||||
- Video conferencing with end-to-end encryption
|
||||
- Screen sharing and collaborative whiteboarding
|
||||
- Chat functionality with persistent history
|
||||
- No user data collection or tracking
|
||||
- Operates entirely on user-owned infrastructure
|
||||
|
||||
- **Customer Relationship Management** (CRM):
|
||||
- Contact and lead management
|
||||
- Sales pipeline tracking
|
||||
- Marketing campaign management
|
||||
- Analytics and reporting
|
||||
- Complete data sovereignty
|
||||
|
||||
- **Other Applications**:
|
||||
- Code repositories and development platforms
|
||||
- Database services
|
||||
- Content management systems
|
||||
- Email and messaging services
|
||||
- File storage and sharing
|
||||
|
||||
## Unique Service Model
|
||||
|
||||
- **Resource Ownership**:
|
||||
- Users provide their own slices (compute resources)
|
||||
- Data remains on user-controlled infrastructure
|
||||
- No vendor lock-in as with traditional SaaS
|
||||
|
||||
- **Service Provider Responsibilities**:
|
||||
- Application deployment and configuration
|
||||
- Ongoing maintenance and updates
|
||||
- Monitoring system health
|
||||
- Implementing self-healing procedures
|
||||
- Backup management
|
||||
- Security patching
|
||||
|
||||
- **Points Exchange**:
|
||||
|
||||
- Users pay service providers in [TFP Points](./tfp.md) for management services
|
||||
- Payment based on service level and application complexity
|
||||
- No charges for the underlying infrastructure (user-owned)
|
||||
|
||||
## Self-Healing Architecture
|
||||
|
||||
```kroki-mermaid
|
||||
graph TD
|
||||
subgraph "User-Owned Slices"
|
||||
S1[Application Slice 1]
|
||||
S2[Application Slice 2]
|
||||
S3[Database Slice]
|
||||
S4[Storage Slice]
|
||||
end
|
||||
|
||||
subgraph "Service Provider Systems"
|
||||
MS[Monitoring System]
|
||||
AS[Alerting System]
|
||||
HS[Healing System]
|
||||
BS[Backup System]
|
||||
US[Update System]
|
||||
end
|
||||
|
||||
MS --> S1
|
||||
MS --> S2
|
||||
MS --> S3
|
||||
MS --> S4
|
||||
|
||||
MS --> AS
|
||||
AS --> HS
|
||||
HS --> S1
|
||||
HS --> S2
|
||||
HS --> S3
|
||||
HS --> S4
|
||||
|
||||
BS --> S1
|
||||
BS --> S2
|
||||
BS --> S3
|
||||
BS --> S4
|
||||
|
||||
US --> S1
|
||||
US --> S2
|
||||
US --> S3
|
||||
US --> S4
|
||||
|
||||
classDef slice fill:#9cf,stroke:#333,stroke-width:1px;
|
||||
classDef system fill:#f96,stroke:#333,stroke-width:2px;
|
||||
|
||||
class S1,S2,S3,S4 slice;
|
||||
class MS,AS,HS,BS,US system;
|
||||
```
|
||||
|
||||
## Monitoring and Management
|
||||
|
||||
- **Continuous Monitoring**:
|
||||
- Real-time health checks of all system components
|
||||
- Performance metrics collection
|
||||
- Resource utilization tracking
|
||||
- Application-specific monitoring
|
||||
- Proactive issue detection
|
||||
|
||||
- **Automated Healing Processes**:
|
||||
- Service failure detection
|
||||
- Automatic service restart
|
||||
- Container or VM recreation when needed
|
||||
- Data consistency verification
|
||||
- Load balancing adjustments
|
||||
- Rollback to known good states when necessary
|
||||
|
||||
- **Backup Systems**:
|
||||
- Automated regular backups
|
||||
- Incremental and full backup options
|
||||
- Secure, encrypted backup storage
|
||||
- Point-in-time recovery capabilities
|
||||
- Backup verification and testing
|
||||
|
||||
- **Update Management**:
|
||||
- Zero-downtime updates where possible
|
||||
- Staged rollouts to minimize risk
|
||||
- Automatic rollback on failed updates
|
||||
- Security patch prioritization
|
||||
- Feature updates on scheduled cadence
|
||||
|
||||
## Deployment Process
|
||||
|
||||
- **Initial Setup**:
|
||||
- User allocates required slices based on application needs
|
||||
- Service provider deploys application components across slices
|
||||
- Initial configuration and customization
|
||||
- Integration with Mycelium Names and Gateways
|
||||
- Security hardening and testing
|
||||
|
||||
- **Ongoing Operation**:
|
||||
- 24/7 monitoring by service provider systems
|
||||
- Automatic scaling based on demand (using additional user slices)
|
||||
- Regular maintenance during defined windows
|
||||
- Performance optimization
|
||||
- Security audits and updates
|
||||
81
specs/bandwidth_providers.md
Normal file
81
specs/bandwidth_providers.md
Normal file
@@ -0,0 +1,81 @@
|
||||
# Bandwidth Providers
|
||||
|
||||
Bandwidth Providers are specialized participants in the TF Marketplace who supply bandwidth to Mycelium Gateways (MGWs).
|
||||
|
||||
|
||||
## Core Principles
|
||||
|
||||
- **Specialized Service**: Only visible to qualified bandwidth providers
|
||||
- **TFP-Based Billing**: Providers compensated in TFP based on bandwidth delivered
|
||||
- **Volume Pricing**: Pricing set per TB of data transferred
|
||||
- **Quality of Service**: Performance metrics tracked and rewarded
|
||||
- **Infrastructure Support**: Critical for the operation of Mycelium Gateways
|
||||
|
||||
## How It Works
|
||||
|
||||
### Provider Qualification
|
||||
|
||||
- **Requirements**:
|
||||
- Significant bandwidth capacity
|
||||
- Reliable network infrastructure
|
||||
- Geographic diversity (preferred)
|
||||
- Stable connectivity
|
||||
- Minimal latency
|
||||
|
||||
- **Registration Process**:
|
||||
- Apply for bandwidth provider status
|
||||
- Verify network capabilities
|
||||
- Complete technical integration
|
||||
- Set pricing per TB of bandwidth
|
||||
|
||||
### Operational Model
|
||||
|
||||
- **Bandwidth Delivery**:
|
||||
- Direct connection to TF-run Mycelium Gateways
|
||||
- Automated traffic routing based on efficiency
|
||||
- Real-time usage monitoring
|
||||
- Dynamic capacity allocation
|
||||
|
||||
- **Management Interface**:
|
||||
- Monitor bandwidth consumption
|
||||
- Track TFP earnings
|
||||
- Adjust available capacity
|
||||
- View performance metrics
|
||||
|
||||
## Technical Specifications
|
||||
|
||||
- This service is not visible to all marketplace participants and is specifically designed for providers with significant bandwidth capacity.
|
||||
|
||||
- **Connection Requirements**:
|
||||
- Direct peering arrangements
|
||||
- Transit provider connections
|
||||
- Dedicated links where available
|
||||
|
||||
- **Performance Requirements**:
|
||||
- Minimum uptime guarantees
|
||||
- Latency thresholds
|
||||
- Packet loss limitations
|
||||
- Throughput commitments
|
||||
|
||||
## TFP Exchange Mechanism
|
||||
|
||||
- **Measurement**: Bandwidth usage measured in TB transferred
|
||||
- **Pricing**: Providers set their own price per TB
|
||||
- **Payment**: TFP automatically transferred based on verified usage by Mycelium GW
|
||||
- **Settlement**: Regular settlement periods (typically monthly)
|
||||
|
||||
## Benefits for Providers
|
||||
|
||||
- **Monetization**: Convert excess bandwidth capacity into TFP
|
||||
- **Predictable Income**: Based on actual bandwidth delivered
|
||||
- **Flexibility**: Adjust capacity and pricing as needed
|
||||
- **Integration**: Become an essential part of the TF Grid infrastructure
|
||||
- **Scaling**: Opportunity to grow with the TF ecosystem
|
||||
|
||||
## Benefits for the TF Grid
|
||||
|
||||
- **Reliability**: Multiple bandwidth sources ensure network resilience
|
||||
- **Performance**: Optimized routing improves user experience
|
||||
- **Scalability**: Distributed model allows for global growth
|
||||
- **Cost Efficiency**: Market-based pricing optimizes resource allocation
|
||||
|
||||
55
specs/certified.md
Normal file
55
specs/certified.md
Normal file
@@ -0,0 +1,55 @@
|
||||
# ThreeFold Certification
|
||||
|
||||
## Overview
|
||||
|
||||
ThreeFold Certification is a quality assurance program for farmers and solution providers who take a license with support from ThreeFold. This certification enables providers to offer enhanced reliability and guaranteed support to their customers.
|
||||
|
||||
## Benefits of Certification
|
||||
|
||||
- **Guaranteed Support**: Certified farmers and solution providers receive priority support directly from ThreeFold.
|
||||
- **Enhanced Reliability**: Certification ensures higher standards of service quality and uptime.
|
||||
- **Trust Signal**: Users can easily identify certified providers in the marketplace.
|
||||
- **SLA Endorsement**: Certified providers commit to specific Service Level Agreements endorsed by ThreeFold.
|
||||
- **Priority Resolution**: Issues affecting certified slices receive expedited attention from ThreeFold support teams.
|
||||
|
||||
## How Certification Works
|
||||
|
||||
1. **Licensing**: Farmers or solution providers enter into a support license agreement with ThreeFold.
|
||||
2. **Verification**: ThreeFold verifies that the provider meets all technical and operational requirements.
|
||||
3. **Certification**: Upon approval, the provider receives certified status.
|
||||
4. **Flagging**: All slices offered by certified providers are automatically flagged as "certified" in the marketplace.
|
||||
|
||||
## Certification Flag on Slices
|
||||
|
||||
When browsing the TF Marketplace, users can filter for certified slices. The certification flag indicates:
|
||||
|
||||
- The slice is provided by a certified farmer or solution provider
|
||||
- ThreeFold guarantees support for this slice
|
||||
- The slice meets higher reliability standards
|
||||
- Support requests will receive priority handling
|
||||
|
||||
## Becoming Certified
|
||||
|
||||
Farmers and solution providers interested in certification can:
|
||||
|
||||
1. Contact ThreeFold to inquire about licensing options
|
||||
2. Review and sign the software and support license agreement
|
||||
3. Complete the certification process
|
||||
4. Begin offering certified slices in the marketplace
|
||||
|
||||
## Maintaining Certification
|
||||
|
||||
To maintain certified status, providers must:
|
||||
|
||||
- Continuously meet or exceed the agreed SLAs
|
||||
- Keep their support license active and in good standing
|
||||
- Participate in periodic reviews and audits (TBD)
|
||||
- Address any compliance issues promptly
|
||||
|
||||
## For Users
|
||||
|
||||
When selecting slices in the marketplace, look for the certification flag to ensure you're getting resources with guaranteed ThreeFold support and enhanced reliability.
|
||||
|
||||
## License agreement needed
|
||||
|
||||
> TODO: ...
|
||||
58
specs/marketplace.md
Normal file
58
specs/marketplace.md
Normal file
@@ -0,0 +1,58 @@
|
||||
# TF Marketplace
|
||||
|
||||
The TF Marketplace is a central platform facilitating the exchange of value through the mutual credit [TFP](./tfp.md) system. It connects suppliers (providers) and consumers, enabling the discovery, acquisition, and management of various resources and services.
|
||||
|
||||
## Core Marketplace Categories
|
||||
|
||||
The marketplace is organized into categories that align with the exchange mechanisms described in the [TFP system](./points.md) document:
|
||||
|
||||
| Marketplace | Description | Suppliers | Consumers | TFP Exchange |
|
||||
|-------------|-------------|-----------|-----------|----------------|
|
||||
| **Compute Resources (Slices)** | Primary marketplace for compute capacity | Farmers providing hardware resources | Users needing compute capacity | TFP transferred based on resource utilization |
|
||||
| **[3Nodes](./3nodes.md)** | Physical computing hardware marketplace | Hardware sellers | Hardware buyers | TFP transferred based on hardware value |
|
||||
| **Mycelium Gateways** | Internet connectivity services | Gateway providers | Users requiring internet access | TFP paid based on bandwidth consumption |
|
||||
| **[Bandwidth Providers](./bandwidth_providers.md)** | Bandwidth supply for TF-run Mycelium Gateways | Bandwidth providers | TF-run Mycelium Gateways | TFP paid based on TB of bandwidth delivered |
|
||||
| **Mycelium Names** | Global fair name system | TF COOP (name provider) | Users registering names | TFP paid based on name length (shorter names cost more) |
|
||||
| **Human Energy Services** | Professional technical services | Service providers (designers, admins, developers) | Users needing expertise | TFP transferred based on agreed rates |
|
||||
| **Application Solutions** | Pre-configured, self-healing applications | Solution providers | End users | Users provide slices to solution providers while maintaining sovereignty |
|
||||
| **TFP Exchange** (phase 2)| Trading platform for TFP | TFP sellers | TFP buyers | Direct exchange of TFP for currencies (TFT, USD, etc.) |
|
||||
|
||||
## Marketplace Features
|
||||
|
||||
### Discovery and Filtering
|
||||
|
||||
- **Resource Discovery**: Browse available resources using filters for location, reputation, uptime, bandwidth, and price
|
||||
- **Solution Catalog**: Curated collection of pre-configured applications with specified resource requirements
|
||||
- **Service Directory**: List of available professional services with ratings and specializations
|
||||
|
||||
### Acquisition Models
|
||||
|
||||
- **Flexible Terms**: Resources can be acquired on various terms (hourly, monthly, yearly)
|
||||
- **Discounts**: Available for longer-term commitments
|
||||
- **Service Credits**: Purchase credits for accessing different tiers of technical support
|
||||
|
||||
### Advanced Features
|
||||
|
||||
#### Buy Orders (Future Enhancement)
|
||||
|
||||
The marketplace will support an order system allowing consumers to place buy orders, signaling demand for specific configurations or price levels rather than only browsing available offers.
|
||||
|
||||
#### Reputation System
|
||||
|
||||
Suppliers build reputation based on:
|
||||
- Meeting service level agreements
|
||||
- Uptime and reliability
|
||||
- Consumer ratings
|
||||
- Length of participation in the marketplace
|
||||
|
||||
## Benefits of the Marketplace
|
||||
|
||||
- **Sovereignty**: Consumers maintain control over their resources and deployed solutions
|
||||
- **Transparency**: Clear pricing and reputation metrics
|
||||
- **Efficiency**: Direct matching of suppliers and consumers
|
||||
- **Flexibility**: Multiple acquisition models to suit different needs
|
||||
- **Community Growth**: Encourages participation from both suppliers and consumers
|
||||
|
||||
## Governance
|
||||
|
||||
The marketplace operates under the same governance principles as the TFP system, with transparent rules and community consensus ensuring fair practices and preventing manipulation.
|
||||
152
specs/mycelium_gw.md
Normal file
152
specs/mycelium_gw.md
Normal file
@@ -0,0 +1,152 @@
|
||||
# Mycelium Gateways (MGW)
|
||||
|
||||
Mycelium Gateways are critical infrastructure components that bridge the Mycelium network with the public internet, functioning as reverse proxies that enable bidirectional connectivity between TF Grid resources and the outside world.
|
||||
|
||||
## Core Principles
|
||||
|
||||
- **Decentralized Access**: Distributed gateway network with no single point of failure
|
||||
- **Low Latency**: Optimized routing for minimal connection delays
|
||||
- **Scalability**: Designed to support thousands of interconnected gateways
|
||||
- **Flexibility**: Compatible with both Mycelium Names and traditional DNS
|
||||
- **Fair Pricing**: [TFP Points](./tfp.md)-based billing for actual bandwidth consumed
|
||||
|
||||
## How It Works
|
||||
|
||||
- **Reverse Proxy Functionality**:
|
||||
- Acts as an intermediary between the public internet and the Mycelium network
|
||||
- Routes incoming requests to the appropriate slice or service
|
||||
- Forwards outgoing traffic from slices to the internet
|
||||
- Provides protocol translation where necessary
|
||||
|
||||
- **Connectivity Options**:
|
||||
- Can be attached to Mycelium Names for seamless integration
|
||||
- Works with existing DNS names for compatibility with traditional systems
|
||||
- Supports multiple domains and subdomains per gateway
|
||||
- Enables both HTTP/HTTPS and TCP/UDP traffic
|
||||
|
||||
- **Network Architecture**:
|
||||
- Thousands of gateways distributed globally
|
||||
- Interconnected mesh topology for redundancy
|
||||
- Automatic routing to nearest gateway for optimal performance
|
||||
- Load balancing across multiple gateways for high-traffic services
|
||||
|
||||
## TFP Exchange Mechanism
|
||||
|
||||
- **Suppliers**: Gateway providers offering internet connectivity
|
||||
- **Consumers**: Users requiring internet access for their resources
|
||||
- **Billing Model**:
|
||||
- Pay-per-use based on actual bandwidth consumed
|
||||
- Measured in both incoming and outgoing traffic
|
||||
- Tiered pricing possible based on quality of service
|
||||
- TFP Points flow directly from consumers to gateway providers
|
||||
|
||||
## Technical Specifications
|
||||
|
||||
- **Performance**:
|
||||
- High-throughput connections
|
||||
- Low-latency routing
|
||||
- Automatic failover between gateways
|
||||
- DDoS protection capabilities
|
||||
|
||||
- **Security Features**:
|
||||
- TLS termination
|
||||
- Traffic filtering
|
||||
- Rate limiting
|
||||
- Access control lists
|
||||
|
||||
- **Management Interface**:
|
||||
- Create and delete gateway configurations
|
||||
- Monitor traffic and performance
|
||||
- Configure routing rules
|
||||
- Set up domain mappings
|
||||
|
||||
## Use Cases
|
||||
|
||||
- **Web Applications**:
|
||||
- Expose web services running on slices to the internet
|
||||
- Host websites with custom domains
|
||||
- Provide API endpoints for external consumption
|
||||
|
||||
- **IoT Connectivity**:
|
||||
- Connect IoT devices to services running on the TF Grid
|
||||
- Aggregate and process data from distributed sensors
|
||||
- Provide secure command and control channels
|
||||
|
||||
- **Enterprise Connectivity**:
|
||||
- Secure access to private resources on the TF Grid
|
||||
- Extend corporate networks with sovereign infrastructure
|
||||
- Create hybrid deployments spanning traditional and TF Grid resources
|
||||
|
||||
## Benefits
|
||||
|
||||
- **Sovereignty**: Control over your internet access points
|
||||
- **Resilience**: Multiple gateways ensure continuous connectivity
|
||||
- **Performance**: Low-latency connections through optimal routing
|
||||
- **Cost-Efficiency**: Pay only for bandwidth actually consumed
|
||||
- **Simplicity**: Easy configuration and management
|
||||
|
||||
## Network Visualization
|
||||
|
||||
```kroki-mermaid
|
||||
graph TD
|
||||
subgraph Internet
|
||||
DNS[DNS System]
|
||||
Web[Web Users]
|
||||
API[API Clients]
|
||||
end
|
||||
|
||||
subgraph "Mycelium Gateway Network"
|
||||
MGW1[Mycelium Gateway 1]
|
||||
MGW2[Mycelium Gateway 2]
|
||||
MGW3[Mycelium Gateway 3]
|
||||
MGW4[Mycelium Gateway 4]
|
||||
MGW5[Mycelium Gateway 5]
|
||||
MGW6[Mycelium Gateway 6]
|
||||
|
||||
MGW1 --- MGW2
|
||||
MGW2 --- MGW3
|
||||
MGW3 --- MGW4
|
||||
MGW4 --- MGW5
|
||||
MGW5 --- MGW6
|
||||
MGW6 --- MGW1
|
||||
MGW1 --- MGW4
|
||||
MGW2 --- MGW5
|
||||
MGW3 --- MGW6
|
||||
end
|
||||
|
||||
subgraph "Mycelium Network (TF Grid)"
|
||||
MN[Mycelium Network]
|
||||
|
||||
subgraph "Compute Slices"
|
||||
S1[Web Server Slice]
|
||||
S2[Database Slice]
|
||||
S3[Application Slice]
|
||||
S4[Storage Slice]
|
||||
end
|
||||
|
||||
MN --- S1
|
||||
MN --- S2
|
||||
MN --- S3
|
||||
MN --- S4
|
||||
end
|
||||
|
||||
Web --> MGW1
|
||||
API --> MGW3
|
||||
DNS --> MGW1
|
||||
DNS --> MGW3
|
||||
|
||||
MGW1 --> MN
|
||||
MGW2 --> MN
|
||||
MGW3 --> MN
|
||||
MGW4 --> MN
|
||||
MGW5 --> MN
|
||||
MGW6 --> MN
|
||||
|
||||
classDef gateway fill:#f96,stroke:#333,stroke-width:2px;
|
||||
classDef slice fill:#9cf,stroke:#333,stroke-width:1px;
|
||||
classDef internet fill:#fcf,stroke:#333,stroke-width:1px;
|
||||
|
||||
class MGW1,MGW2,MGW3,MGW4,MGW5,MGW6 gateway;
|
||||
class S1,S2,S3,S4 slice;
|
||||
class Web,API,DNS internet;
|
||||
```
|
||||
85
specs/names.md
Normal file
85
specs/names.md
Normal file
@@ -0,0 +1,85 @@
|
||||
# Mycelium Names
|
||||
|
||||
Mycelium Names is a global fair name system that provides addressing services within the TF Grid ecosystem. It operates on principles of decentralization, fairness, and community benefit, addressing the limitations of traditional DNS systems.
|
||||
|
||||
## Core Principles
|
||||
|
||||
- **Decentralized**: No central authority controls the naming system
|
||||
- **Fair Pricing**: Cost based on name length, with shorter names commanding higher prices
|
||||
- **Community Benefit**: 100% of revenue used for ecosystem development
|
||||
- **Sovereignty**: Users define their own names and administrators
|
||||
- **Scalability**: Designed to scale globally
|
||||
- **Geo-Awareness**: Queries return results from the closest location
|
||||
- **Load Balancing**: Distributes traffic across multiple sites based on location
|
||||
|
||||
## How It Works
|
||||
|
||||
### Name Structure
|
||||
|
||||
- **Top Names**: Format of `xxxx.yyyy`
|
||||
- Price depends on the length of both segments
|
||||
- Shorter names (vanity names) are more expensive
|
||||
- Names with 8+ characters in each segment are nearly free
|
||||
- Each name is globally unique
|
||||
- **Circle Names**:
|
||||
- Top names link to a Circle and its administrators
|
||||
- Edge names are stored per circle
|
||||
- Can be any depth (subdomains)
|
||||
- Updates are frictionless and free
|
||||
|
||||
### Technical Implementation
|
||||
|
||||
- Name services are built into the TF Grid infrastructure
|
||||
- Replicated across all subnets for redundancy and performance
|
||||
- Queries are resolved to the nearest geographic location
|
||||
- Load balancing automatically distributes traffic for busy sites
|
||||
- Supports unlimited subdomains with efficient updates
|
||||
|
||||
### Administration Model
|
||||
|
||||
- Each person can define their own names
|
||||
- Multiple administrators can be assigned (more than 1)
|
||||
- Decentralized governance prevents single points of control
|
||||
- Community-driven development and improvement
|
||||
|
||||
## Pricing Model
|
||||
|
||||
- **Pricing Factors**:
|
||||
- Length of name segments (shorter = more expensive)
|
||||
- Registration period (longer periods may offer discounts)
|
||||
- Renewal fees follow the same pricing structure
|
||||
- **Examples**:
|
||||
- Very short names (3-4 characters): Highest price point
|
||||
- Medium-length names (5-7 characters): Moderate pricing
|
||||
- Long names (8+ characters): Nearly free, accessible to all
|
||||
- **Payment**:
|
||||
- Paid in [TFP Points](./tfp.md) through the mutual credit system
|
||||
- TFP flow from name registrants to the TF COOP
|
||||
|
||||
## Comparison to Traditional DNS
|
||||
|
||||
| Aspect | Traditional DNS | Mycelium Names |
|
||||
|--------|----------------|---------------|
|
||||
| **Control** | Centralized (ICANN, registrars) | Decentralized (community) |
|
||||
| **Pricing** | Often arbitrary, high margins | Fair, based on name length |
|
||||
| **Revenue Use** | Profit for registrars | 100% for community benefit |
|
||||
| **Geographic Awareness** | Limited (CDNs as add-ons) | Built-in geo-awareness |
|
||||
| **Load Balancing** | Requires additional services | Native functionality |
|
||||
| **Subdomain Management** | Often requires technical knowledge | Frictionless, user-friendly |
|
||||
|
||||
## Benefits for Users
|
||||
|
||||
- **Affordability**: Everyone can access a name they can afford
|
||||
- **Sovereignty**: Control over your own namespace
|
||||
- **Performance**: Geo-aware resolution improves speed
|
||||
- **Reliability**: Replicated across the network for high availability
|
||||
- **Simplicity**: Easy management of domains and subdomains
|
||||
- **Fairness**: Transparent pricing based on objective criteria
|
||||
|
||||
## Integration with TF Grid
|
||||
|
||||
- Seamlessly works with Mycelium Gateways for web access
|
||||
- Integrates with all other TF Grid services
|
||||
- Essential component of the mutual credit [TFP](./tfp.md) system
|
||||
- Enables discovery of services and resources across the grid
|
||||
|
||||
40
specs/points.md
Normal file
40
specs/points.md
Normal file
@@ -0,0 +1,40 @@
|
||||
# ThreeFold Points (TFP) System
|
||||
|
||||
The TF Marketplace operates on a [TFP](./tfp.md) system where value is exchanged between suppliers (providers) and consumers through TFP. This creates a balanced marketplace where participants can both earn and spend TFP based on their contributions and needs.
|
||||
|
||||
## Core Principles
|
||||
|
||||
- [TFP = ThreeFold Tokens](./tfp.md) represent value exchanged within the marketplace
|
||||
- Suppliers provide services/products and earn TFP
|
||||
- Consumers use services/products and spend TFP
|
||||
- The same entity can be both supplier and consumer in different contexts
|
||||
- TFP facilitate direct value exchange without traditional currency intermediaries
|
||||
|
||||
## Exchange Categories
|
||||
|
||||
The table below illustrates how TFP flow between suppliers and consumers across different service categories:
|
||||
|
||||
| Category | Supplier | Consumer | Exchange Mechanism |
|
||||
|----------|----------|----------|-------------------|
|
||||
| **Compute** | Farmers provide slices (compute resources) | Users reserve and utilize slices | Consumers pay TFP to suppliers based on slice utilization |
|
||||
| **3Nodes** | Hardware owners selling physical computing equipment | Users looking to acquire hardware (hosted or physically transferred) | Buyers pay upfront TFP to sellers based on hardware value |
|
||||
| **Mycelium Gateways (MGW)** | Gateway providers offer internet connectivity | Users access the internet through gateways | Consumers pay TFP for bandwidth consumed through the gateway |
|
||||
| **Bandwidth Providers** | Entities with significant bandwidth capacity | TF-run Mycelium Gateways | Providers paid TFP based on TB of bandwidth delivered |
|
||||
| **Mycelium Names** | TF COOP (name provider) | Users registering names | Consumers pay TFP based on name length (shorter names cost more TFP) |
|
||||
| **Human Energy** | Service providers (designers, admins, trainers, developers) | Users of professional services | Consumers pay TFP directly to service providers based on agreed rates |
|
||||
| **Application Services** | Solution providers | End users | Unique model: users provide slices to solution providers, maintaining sovereignty over deployed solutions |
|
||||
| **Money Exchange**, phase 2 | TFP sellers | TFP buyers | TFP can be bought/sold for currencies (TFT, USD, etc.) through [liquidity pools](./tfp.md) |
|
||||
|
||||
## Benefits of the TFP System
|
||||
|
||||
- **Sovereignty**: Users maintain control over their resources and deployed solutions
|
||||
- **Flexibility**: Participants can be both providers and consumers
|
||||
- **Efficiency**: Direct value exchange without intermediaries
|
||||
- **Sustainability**: System encourages balanced contribution and consumption
|
||||
- **Liquidity**: TFP can be exchanged for traditional currencies when needed through [liquidity pools](./tfp.md)
|
||||
|
||||
## Governance
|
||||
|
||||
The TFP system is governed by transparent rules and community consensus, ensuring fair exchange rates and preventing manipulation.
|
||||
|
||||
*Note: For information about the slashing mechanism for farmers who fail to meet SLAs, please refer to the [farmers.md](farmers.md) document.*
|
||||
173
specs/products.md
Normal file
173
specs/products.md
Normal file
@@ -0,0 +1,173 @@
|
||||
# TF Marketplace Products & Services
|
||||
|
||||
The TF Marketplace offers various products and services that facilitate the mutual credit [TFP Points](./tfp.md) system, enabling value exchange between suppliers (providers) and consumers. This document details these core offerings and how they integrate with the TFP marketplace.
|
||||
|
||||
## [Compute Resources = Slices](slices.md)
|
||||
|
||||
- **Definition**: The fundamental unit of compute resource
|
||||
- **Suppliers**: Farmers who register their hardware nodes
|
||||
- **Consumers**: Users who need computing resources
|
||||
- **Exchange Mechanism**:
|
||||
- Users acquire Slices through the marketplace
|
||||
- TFP = points flow from consumers to suppliers based on utilization
|
||||
- Pricing varies based on slice size and specifications
|
||||
- **Integration**:
|
||||
- Natively connected to the Mycelium network
|
||||
- Detailed specifications available in [slices.md](./slices.md)
|
||||
|
||||
## [3Nodes](3nodes.md)
|
||||
|
||||
- **Definition**: Physical computing hardware (servers, computers) that can be bought and sold
|
||||
- **Suppliers**: Hardware owners selling their equipment
|
||||
- **Consumers**: Users looking to acquire physical computing hardware
|
||||
- **Purchase Options**:
|
||||
- **Supplier-Hosted**: Hardware remains at supplier's facility but owned by buyer
|
||||
- **Physical Transfer**: Hardware physically shipped to buyer's location
|
||||
- **Exchange Mechanism**:
|
||||
- Upfront TFP payment for both hosting options
|
||||
- For physically transferred hardware: escrow system protects both parties during shipping
|
||||
- For supplier-hosted hardware: clear SLAs define uptime and performance guarantees
|
||||
- **Hardware Types**:
|
||||
- Servers
|
||||
- Desktop computers
|
||||
- Mini PCs
|
||||
- Custom builds
|
||||
- **Specifications**:
|
||||
- Detailed hardware specifications provided
|
||||
- Condition and age documented
|
||||
- Performance metrics where available
|
||||
- Power consumption data
|
||||
|
||||
## [Mycelium Gateways](mycelium_gw.md)
|
||||
|
||||
- **Definition**: Services enabling internet connectivity to the TF Marketplace
|
||||
- **Suppliers**: Gateway providers offering internet access
|
||||
- **Consumers**: Users requiring internet connectivity for their resources
|
||||
- **Exchange Mechanism**:
|
||||
- Consumers pay TFP for bandwidth consumed
|
||||
- Gateway providers earn TFP based on traffic volume
|
||||
- **Core Functionality**:
|
||||
- Traffic forwarding from a `prefix.domain_name` structure to a Mycelium address
|
||||
- Support for custom domain names or platform-acquired names
|
||||
- Integration with Mycelium-based DNS system
|
||||
- **Management**:
|
||||
- Users can create and delete web gateway configurations
|
||||
- Configure routing and access controls
|
||||
|
||||
## [Bandwidth Providers](bandwidth_providers.md)
|
||||
|
||||
- **Definition**: Specialized providers supplying bandwidth to TF-run Mycelium Gateways
|
||||
- **Suppliers**: Entities with significant bandwidth capacity
|
||||
- **Consumers**: TF-run Mycelium Gateways
|
||||
- **Exchange Mechanism**:
|
||||
- TFP paid based on TB of bandwidth delivered
|
||||
- Providers set their own price per TB
|
||||
- Regular settlement periods (typically monthly)
|
||||
- **Visibility**:
|
||||
- Not visible to all marketplace participants
|
||||
- Specialized service for qualified providers only
|
||||
- **Requirements**:
|
||||
- Significant bandwidth capacity
|
||||
- Reliable network infrastructure
|
||||
- Stable connectivity
|
||||
- Minimal latency
|
||||
|
||||
## [Mycelium Names](names.md)
|
||||
|
||||
- **Definition**: A global fair name system for domain registration and management
|
||||
- **Suppliers**: TF COOP (primary name provider)
|
||||
- **Consumers**: Users registering and managing domain names
|
||||
- **Exchange Mechanism**:
|
||||
- TFP paid based on name length (shorter names cost more TFP)
|
||||
- Registration period affects total point cost
|
||||
- **Core Functionality**:
|
||||
- Registration and management of domain names
|
||||
- Integration with Web Gateways for DNS resolution
|
||||
- Support for various domain types and structures
|
||||
|
||||
|
||||
## [Application Solutions](apps.md)
|
||||
|
||||
- **Definition**: Pre-configured, self-healing applications deployed on the platform
|
||||
- **Suppliers**: Solution providers who develop and maintain applications
|
||||
- **Consumers**: End users who utilize these applications
|
||||
- **Exchange Mechanism**:
|
||||
- Unique model: users provide slices to solution providers
|
||||
- Users maintain sovereignty over deployed solutions
|
||||
- Monthly TFP fees for management and support
|
||||
- **Examples**:
|
||||
- Gitea (Git service)
|
||||
- CRM systems
|
||||
- PostgreSQL database clusters
|
||||
- **Deployment Process**:
|
||||
- Users select Solutions from the marketplace
|
||||
- Solutions specify resource requirements
|
||||
- Platform guides users through resource acquisition if needed
|
||||
- **Management & Support**:
|
||||
- Solutions typically managed by providers
|
||||
- Users may have limited direct access during active management
|
||||
- Users can reclaim full control if they discontinue a managed Solution
|
||||
- **Interdependencies**:
|
||||
- Solutions can depend on other Solutions
|
||||
- Modular architecture allows for flexible configurations
|
||||
|
||||
## Human Energy Services
|
||||
|
||||
- **Definition**: Professional technical services and support
|
||||
- **Suppliers**: Service providers (designers, admins, trainers, developers)
|
||||
- **Consumers**: Users needing expertise and technical assistance
|
||||
- **Exchange Mechanism**:
|
||||
- Consumers pay TFP directly to service providers
|
||||
- Rates based on service tier, duration, and timing
|
||||
- **Service Tiers**:
|
||||
- Standard Support: Basic assistance
|
||||
- Expert Services: Specialized, higher-cost assistance
|
||||
- Priority Options: Expedited response/resolution
|
||||
- **Pricing Model**:
|
||||
- Volume discounts for larger purchases
|
||||
- Premium rates for urgent or off-hours service
|
||||
- **Service Providers**:
|
||||
- Initial phase: In-house TF teams
|
||||
- Future vision: Open marketplace for community providers
|
||||
- **Service Marketplace**:
|
||||
- Users can post service requests
|
||||
- Providers can bid on requests
|
||||
- Platform facilitates matching between requesters and providers
|
||||
|
||||
|
||||
## TFP Exchange
|
||||
|
||||
- **Definition**: System for trading TFP for traditional currencies through [liquidity pools](./tfp.md)
|
||||
- **Suppliers**: TFP sellers offering TFP for currency
|
||||
- **Consumers**: TFP buyers acquiring TFP with currency
|
||||
- **Exchange Mechanism**:
|
||||
- Direct exchange of TFP for currencies (TFT, USD, etc.)
|
||||
- Market-based pricing with potential platform guidance
|
||||
- **Functionality**:
|
||||
- Trading platform for TFP
|
||||
- Support for multiple currencies
|
||||
- Transaction history and reporting
|
||||
|
||||
|
||||
## Supporting Concept
|
||||
|
||||
### Mycelium Network
|
||||
|
||||
- **Definition**: A foundational, secure networking layer underpinning the platform
|
||||
- **Core Functionality**:
|
||||
- Provides inherent connectivity for all Slices
|
||||
- Web Gateways utilize Mycelium addresses for routing
|
||||
- Hosts its own internal DNS service
|
||||
- **Integration**:
|
||||
- Not offered as a standalone service
|
||||
- Integral component of the platform infrastructure
|
||||
- Enables secure communication between all TF Marketplace components
|
||||
|
||||
|
||||
### Benefits of the Product Marketplace
|
||||
|
||||
- **Sovereignty**: Users maintain control over their resources and data
|
||||
- **Interoperability**: All products designed to work seamlessly together
|
||||
- **Flexibility**: Multiple options to meet diverse needs
|
||||
- **Scalability**: Resources can grow with user requirements
|
||||
- **Security**: Built-in protection through the Mycelium network
|
||||
46
specs/readme.md
Normal file
46
specs/readme.md
Normal file
@@ -0,0 +1,46 @@
|
||||
# TF Marketplace
|
||||
|
||||
## Introduction
|
||||
|
||||
The TF Marketplace is a decentralized cloud platform that operates on a mutual credit [TFP Points](./tfp.md) system, connecting suppliers (providers) and consumers through a sovereign, efficient, and sustainable infrastructure network.
|
||||
|
||||
## Core Documentation
|
||||
|
||||
This repository contains detailed specifications for all components of the TF Marketplace:
|
||||
|
||||
- [**TF Marketplace**](./marketplace.md) - The platform for discovering and acquiring resources and services
|
||||
- [**Mutual Credit TFP System**](./points.md) - How value is exchanged between suppliers and consumers
|
||||
- [**Products & Services**](./products.md) - Overview of all offerings in the marketplace
|
||||
- [**Slices (Virtual Machines)**](./slices.md) - The fundamental compute resources of the marketplace
|
||||
- [**3Nodes**](./3nodes.md) - Physical computing hardware marketplace
|
||||
- [**Mycelium Names**](./names.md) - The global fair name system
|
||||
- [**Mycelium Gateways**](./mycelium_gw.md) - Internet connectivity services linking the marketplace to the outside world
|
||||
- [**Bandwidth Providers**](./bandwidth_providers.md) - Bandwidth supply for TF-run Mycelium Gateways
|
||||
- [**Self-Healing Applications**](./apps.md) - Managed applications that run on user-owned infrastructure
|
||||
- [**Certification**](./certified.md) - Enhanced reliability and support guarantees for farmers and solution providers
|
||||
- [**TFP = ThreeFold Tokens**](./tfp.md) = mutual credit
|
||||
|
||||
## Key Principles
|
||||
|
||||
- **Sovereignty**: Users maintain control over their resources and data
|
||||
- **Decentralization**: No central authority controls the marketplace
|
||||
- **Fairness**: Transparent pricing and value exchange
|
||||
- **Sustainability**: Balanced contribution and consumption model
|
||||
- **Efficiency**: Direct matching of suppliers and consumers
|
||||
|
||||
## Participants
|
||||
|
||||
- **Suppliers**: Provide resources and services (farmers, gateway providers, solution providers)
|
||||
- **Consumers**: Utilize resources and services (end users, developers, organizations)
|
||||
- **Dual Roles**: Participants can be both suppliers and consumers in different contexts
|
||||
|
||||
## Value Exchange
|
||||
|
||||
The marketplace operates on a mutual credit [TFP Points](./tfp.md) system where:
|
||||
|
||||
- TFP represent value exchanged within the marketplace
|
||||
- Suppliers earn TFP by providing resources and services
|
||||
- Consumers spend TFP to utilize resources and services
|
||||
- TFP can be exchanged for traditional currencies through [liquidity pools](./tfp.md) when needed
|
||||
|
||||
For detailed information on any aspect of the TF Marketplace, please refer to the specific documentation linked above.
|
||||
264
specs/service_node_provider_agreement.md
Normal file
264
specs/service_node_provider_agreement.md
Normal file
@@ -0,0 +1,264 @@
|
||||
# Service and Node Provider Agreement
|
||||
|
||||
**Version:** 1.0
|
||||
**Date:** {{CURRENT_DATE}}
|
||||
|
||||
This Service and Node Provider Agreement (hereinafter referred to as the "Agreement") is made and entered into as of the Effective Date (as defined below) by and between:
|
||||
|
||||
**ThreeFold NV**, a company incorporated in Dubai, UAE, with its principal place of business at DMCC Business Centre, Level No 1, Jewellery & Gemplex 3, Dubai, United Arab Emirates, Registration Number: DMCCXXXX (hereinafter referred to as "ThreeFold" or "Licensor"),
|
||||
|
||||
AND
|
||||
|
||||
**[Provider Name]**, a [company/individual] with its principal place of business at/residing at [Provider Address] (hereinafter referred to as the "Provider" or "Licensee").
|
||||
|
||||
ThreeFold and the Provider are hereinafter collectively referred to as the "Parties" and individually as a "Party".
|
||||
|
||||
**WHEREAS:**
|
||||
|
||||
A. ThreeFold has developed and owns or licenses certain software and a decentralized cloud platform known as the TF Grid, which includes the TF Marketplace and utilizes ThreeFold Tokens (TFP) for value exchange.
|
||||
|
||||
B. ThreeFold offers a Certification program ("ThreeFold Certification") for providers who meet specified quality, reliability, and operational standards.
|
||||
|
||||
C. The Provider wishes to offer services (such as Certified 3Nodes and/or Slices) on the TF Grid and become a ThreeFold Certified Provider.
|
||||
|
||||
D. ThreeFold is willing to grant the Provider a license to use certain ThreeFold Software and provide support under the terms and conditions set forth in this Agreement, in exchange for a license fee.
|
||||
|
||||
**NOW, THEREFORE**, in consideration of the mutual covenants and promises contained herein, the Parties agree as follows:
|
||||
|
||||
## 1. Introduction & Parties
|
||||
|
||||
This section is covered by the preamble above. The "Effective Date" shall be the date this Agreement is signed by both Parties. The initial term of this Agreement shall be one (1) year from the Effective Date, unless terminated earlier as provided herein.
|
||||
|
||||
## 2. Scope of Agreement
|
||||
|
||||
### 2.1. Services Covered by Provider
|
||||
|
||||
This Agreement applies to the Provider's offering of "Certified Services" on the TF Grid, which may include, but are not limited to:
|
||||
a. Provisioning of "Certified 3Nodes" as defined in TF Grid documentation.
|
||||
b. Provisioning of "Certified Slices" (compute resources) as defined in TF Grid documentation.
|
||||
c. Other services mutually agreed upon in writing and designated as Certified Services.
|
||||
|
||||
### 2.2. ThreeFold Software Covered by Support Guarantee
|
||||
|
||||
ThreeFold's support guarantee under this Agreement covers defects in "Covered ThreeFold Software." "Covered ThreeFold Software" is defined as:
|
||||
*All software deployed or made available by ThreeFold via the official TF Grid marketplace and utilized by the Provider in their provision of Certified Services.*
|
||||
This includes, but is not limited to, core components such as Zero-OS (ZOS) and Mycelium networking software, as well as any applications or solutions directly provided and managed by ThreeFold on the marketplace. An indicative list of Covered ThreeFold Software may be provided in Appendix A and updated by ThreeFold from time to time.
|
||||
|
||||
## 3. Certification Requirements
|
||||
|
||||
3.1. The Provider agrees to apply for, achieve, and maintain ThreeFold Certification status for all Certified Services offered under this Agreement.
|
||||
|
||||
3.2. The process, standards, technical and operational requirements, verification procedures, and maintenance obligations for ThreeFold Certification are detailed in the official ThreeFold Certification Program documentation.
|
||||
|
||||
3.3. Failure to achieve or maintain ThreeFold Certification may be grounds for termination of this Agreement by ThreeFold.
|
||||
|
||||
## 4. Provider Obligations
|
||||
|
||||
The Provider shall:
|
||||
4.1. Define, publish, and adhere to its own Service Level Agreements (SLAs) for its end-customers of Certified Services. These SLAs must be transparently communicated to end-customers using the Marketplace Portal.
|
||||
|
||||
4.2. Comply at all times with the then-current ThreeFold Certification standards, policies, and operational guidelines.
|
||||
|
||||
4.3. Accurately and timely report to ThreeFold its Gross TFP Revenue (as defined in Section 7) derived from the compute and storage rental of its Certified Services, in accordance with the reporting procedures outlined herein.
|
||||
|
||||
4.4. Cooperate fully and in a timely manner with ThreeFold's support personnel and processes, including providing all necessary information, logs, and access (where appropriate and secure) required for ThreeFold to diagnose and resolve defects in Covered ThreeFold Software.
|
||||
|
||||
4.5. Use the Covered ThreeFold Software only in accordance with this Agreement and any accompanying documentation.
|
||||
|
||||
4.6. Be responsible for all aspects of its service delivery to its end-customers, including customer support, billing, and contract management.
|
||||
|
||||
4.7. Comply with all applicable laws and regulations in its provision of Certified Services.
|
||||
|
||||
## 5. ThreeFold Obligations & Support Guarantee
|
||||
|
||||
|
||||
ThreeFold shall:
|
||||
5.1. Grant the Provider a non-exclusive, non-transferable (except as provided herein), revocable (pursuant to the terms of this Agreement) license to use the Covered ThreeFold Software solely in connection with the Provider's offering of Certified Services during the term of this Agreement.
|
||||
|
||||
5.2. Provide defect support ("Support Services") for Covered ThreeFold Software to the Provider, as per the severity levels, response times, and resolution targets detailed in Section 6 of this Agreement.
|
||||
|
||||
5.3. Maintain defined support channels (e.g., dedicated portal, email address) for Certified Providers to submit support requests. These channels will be communicated to the Provider upon certification.
|
||||
|
||||
5.4. Use commercially reasonable efforts to correct verified defects in the Covered ThreeFold Software.
|
||||
|
||||
## 6. Defect Support: Severity Levels, Response & Resolution Targets
|
||||
|
||||
### 6.1. Severity Level Definitions
|
||||
The Provider shall, when reporting an issue, reasonably self-assess the severity level. ThreeFold may re-classify the severity level based on its assessment of the impact.
|
||||
|
||||
| Severity Level | Definition | Examples |
|
||||
|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| **Severity 1 (Critical)** | A defect in Covered ThreeFold Software causing a complete loss of essential service or functionality for multiple end-users of the Provider's Certified Service, or a critical security vulnerability, with no workaround available. | *Certified 3Node(s) unbootable due to a ZOS bug; critical Mycelium network failure originating from Covered ThreeFold Software affecting multiple Certified Services; a severe, exploitable security flaw in Covered ThreeFold Software.* |
|
||||
| **Severity 2 (High)** | A defect in Covered ThreeFold Software causing a significant degradation of essential service or functionality, or loss of a major feature, for multiple end-users of the Provider's Certified Service, with no reasonable or only a difficult workaround available. | *Intermittent but frequent loss of network connectivity on Certified Slices due to a Mycelium software defect; a core feature of a ThreeFold-provided marketplace application (used as part of a Certified Service) malfunctioning consistently.* |
|
||||
| **Severity 3 (Medium)** | A defect in Covered ThreeFold Software causing a partial loss of non-critical functionality, minor performance degradation, or impacting a limited number of end-users of the Provider's Certified Service, where a reasonable workaround is available. | *A bug in a management interface of a ThreeFold tool used by the Provider; cosmetic issues in a TF-provided application that do not impede core functionality; minor, non-critical performance issues.* |
|
||||
| **Severity 4 (Low)** | A minor issue, documentation error, request for information, or a cosmetic defect in Covered ThreeFold Software with minimal or no impact on the Provider's or end-users' use of the Certified Service. | *Typographical error in documentation; inquiry about a feature's behavior.* |
|
||||
|
||||
### 6.2. Support Hours & Response/Resolution Targets
|
||||
The following targets are applicable to Support Services provided by ThreeFold to the Provider:
|
||||
|
||||
| Severity Level | Support Request Availability | Target Initial Response Time | Target Resolution/Workaround Time | Notes |
|
||||
|-------------------------|-------------------------------------------|----------------------------------------------|---------------------------------------------------------------------------------------------------|----------------------------------------------------------|
|
||||
| **Severity 1 (Critical)** | 24x7x365 | **1 hour** (from validated S1 submission) | **4-8 hours** | ThreeFold will provide ongoing status updates every [e.g., 2 hours]. |
|
||||
| **Severity 2 (High)** | During Business Hours (as defined below) | **4 business hours** (from validated S2 submission) | **2 business days** | |
|
||||
| **Severity 3 (Medium)** | During Business Hours | **1 business day** (from validated S3 submission) | **5 business days** | |
|
||||
| **Severity 4 (Low)** | During Business Hours | **2 business days** | As resources permit, potentially addressed in a future software release or documentation update. | |
|
||||
|
||||
"**Business Hours**" for ThreeFold support shall mean [e.g., 9:00 AM to 5:00 PM CET/CEST, Monday through Friday, excluding ThreeFold recognized public holidays in Belgium].
|
||||
"**Initial Response Time**" is the time from ThreeFold's acknowledgment of receipt of a properly submitted support request to the time ThreeFold assigns resources to begin addressing the issue.
|
||||
"**Resolution/Workaround Time**" is the time from ThreeFold's acknowledgment to when ThreeFold provides a fix, a patch, a documented workaround, or determines that the issue is not a defect in Covered ThreeFold Software. Resolution may be a permanent fix or a temporary workaround that restores essential functionality.
|
||||
|
||||
### 6.3. Escalation Procedures
|
||||
[To be defined: This section will outline the process for the Provider to escalate an issue if response/resolution targets are not met or if the severity of an issue changes. It will include contact points/methods for escalation.]
|
||||
|
||||
### 6.4. Provider Responsibilities for Support
|
||||
To receive Support Services, Provider must:
|
||||
a. Provide accurate and complete information regarding the issue.
|
||||
b. Make reasonable efforts to diagnose and replicate the issue.
|
||||
c. Cooperate with ThreeFold support personnel.
|
||||
d. Designate specific technical contacts authorized to interact with ThreeFold support.
|
||||
|
||||
## 7. License Fee & Payment
|
||||
|
||||
7.1. In consideration for the license to use Covered ThreeFold Software and the Support Services provided by ThreeFold, ThreeFold shall automatically deduct a recurring license fee ("License Fee") from the Provider's Gross TFP Revenue from Certified Compute and Storage (as defined below) on the TF Grid marketplace backend system.
|
||||
|
||||
7.2. The License Fee shall be **ten percent (10%)** of the Provider's "Gross TFP Revenue from Certified Compute and Storage."
|
||||
|
||||
7.3. "**Gross TFP Revenue from Certified Compute and Storage**" is defined as all ThreeFold Tokens (TFP) earned and received by the Provider from its end-customers specifically for the rental of compute (e.g., vCPU, RAM) and storage (e.g., SSD, HDD capacity) resources offered as part of its Certified Services on Certified 3Nodes or Certified Slices, before deduction of any operational costs, transaction fees, or other expenses incurred by the Provider. Revenue from other services (e.g., managed services, consulting, bandwidth charges billed separately by the provider) is excluded from this calculation unless explicitly agreed in writing.
|
||||
|
||||
7.4. **Reporting**: Within [e.g., ten (10) calendar days] after the end of each calendar month, the Provider shall submit a report to ThreeFold detailing its Gross TFP Revenue from Certified Compute and Storage for the preceding month. The report format and submission method will be specified by ThreeFold. Provider agrees to maintain accurate records to support these reports and allow for auditing by ThreeFold or its designated agent upon reasonable notice.
|
||||
|
||||
7.5. **Payment**: The License Fee for each month will be automatically deducted in TFP from the Provider's Gross TFP Revenue on the TF Grid marketplace backend system at the time the revenue is registered. No direct payment of the License Fee is required from the Provider to ThreeFold.
|
||||
|
||||
7.6. As the License Fee is automatically deducted, provisions for late payments are not applicable to the License Fee itself.
|
||||
|
||||
## 8. SLAs, Staking, and Slashing (Provider to TF Grid Ecosystem)
|
||||
|
||||
8.1. The Provider acknowledges its independent obligations to the TF Grid ecosystem as a farmer or node operator. These obligations include, but are not limited to:
|
||||
a. Meeting any TFP staking requirements mandated by the TF Grid for participation as a node provider/farmer.
|
||||
b. Adhering to any revenue lock-in periods for TFP earned, as defined by TF Grid policies.
|
||||
c. Being subject to the TF Grid's "slashing" mechanisms (potential loss of staked or locked TFP) if the Provider fails to meet its self-defined and published SLAs to its end-customers, or fails to meet other TF Grid operational requirements (e.g., node uptime, resource availability as per `slices.md` and `tfp.md`).
|
||||
|
||||
8.2. This Agreement and the Support Services provided by ThreeFold are intended to assist the Provider in maintaining high-quality Certified Services and meeting its commitments. However, ThreeFold is not responsible for the Provider's failure to meet its independent obligations to its customers or the TF Grid ecosystem. The Provider remains solely responsible for penalties or slashing imposed by the TF Grid.
|
||||
|
||||
## 9. Intellectual Property
|
||||
|
||||
9.1. **ThreeFold IP**: ThreeFold retains all right, title, and interest in and to the Covered ThreeFold Software, the TF Grid, the TF Marketplace, TFP, Mycelium, Zero-OS, and all associated intellectual property rights, including patents, copyrights, trademarks, and trade secrets ("ThreeFold IP").
|
||||
|
||||
9.2. **License Grant**: Subject to the terms of this Agreement, ThreeFold grants Provider a limited, non-exclusive, non-sublicensable, non-transferable, revocable license during the Term to use the ThreeFold IP solely as necessary to offer the Certified Services.
|
||||
|
||||
9.3. **Restrictions**: Provider shall not (and shall not permit any third party to): (a) decompile, reverse engineer, disassemble, or otherwise attempt to derive the source code of any Covered ThreeFold Software (except to the extent such restrictions are prohibited by applicable law); (b) modify, adapt, or create derivative works of any ThreeFold IP; (c) remove, alter, or obscure any proprietary notices on ThreeFold IP; (d) use ThreeFold IP for any purpose not expressly permitted herein.
|
||||
|
||||
9.4. **Provider IP**: Provider retains all right, title, and interest in and to its own intellectual property developed independently of this Agreement ("Provider IP").
|
||||
|
||||
## 10. Confidentiality
|
||||
|
||||
10.1. "Confidential Information" means any non-public information disclosed by one Party to the other, whether orally or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. ThreeFold's Confidential Information includes the Covered ThreeFold Software (in source code form, if accessed), and non-public technical or business information. Provider's Confidential Information includes its non-public customer data and business plans.
|
||||
|
||||
10.2. Each Party agrees to: (a) use Confidential Information of the other Party solely for the purposes of this Agreement; (b) not disclose such Confidential Information to any third party without the other Party's prior written consent, except to employees, agents, or contractors who have a need to know and are bound by confidentiality obligations at least as restrictive as those herein; and (c) protect such Confidential Information from unauthorized use or disclosure using the same degree of care it uses for its own similar information, but not less than reasonable care.
|
||||
|
||||
10.3. Exclusions: Confidential Information does not include information that: (a) is or becomes publicly known through no wrongful act of the receiving Party; (b) was in the receiving Party's possession prior to disclosure by the disclosing Party; (c) is independently developed by the receiving Party without use of or reference to the disclosing Party's Confidential Information; or (d) is rightfully received from a third party without restriction.
|
||||
|
||||
10.4. Compelled Disclosure: If a Party is compelled by law to disclose Confidential Information of the other Party, it shall provide prompt written notice to the other Party (if legally permitted) to enable the other Party to seek a protective order.
|
||||
|
||||
## 11. Term and Termination
|
||||
|
||||
11.1. **Term**: The initial term of this Agreement shall be one (1) year, commencing on the Effective Date. This Agreement shall automatically renew for successive one (1) year periods unless either Party provides written notice of non-renewal to the other Party at least [e.g., sixty (60) days] prior to the end of the then-current term.
|
||||
|
||||
11.2. **Termination for Cause**: Either Party may terminate this Agreement immediately upon written notice if the other Party:
|
||||
a. Materially breaches any provision of this Agreement and fails to cure such breach within [e.g., thirty (30) days] of receiving written notice thereof;
|
||||
b. Becomes insolvent, makes an assignment for the benefit of creditors, or if a receiver or trustee is appointed for it or its assets.
|
||||
|
||||
11.3. **Termination by ThreeFold**: ThreeFold may terminate this Agreement immediately upon written notice if the Provider fails to maintain its ThreeFold Certification status, or fails to pay License Fees when due and does not cure such non-payment within [e.g., ten (10) days] of notice.
|
||||
|
||||
11.4. **Effect of Termination**: Upon termination or expiration of this Agreement:
|
||||
a. All licenses granted hereunder shall immediately terminate.
|
||||
b. Provider shall cease all use of Covered ThreeFold Software and ThreeFold IP.
|
||||
c. Provider shall promptly pay any outstanding License Fees accrued up to the date of termination.
|
||||
d. Each Party shall return or destroy (at the other Party's option) all Confidential Information of the other Party in its possession.
|
||||
e. Sections 7 (for accrued fees), 9, 10, 12, 13, 14, and any other provisions that by their nature should survive, shall survive termination.
|
||||
|
||||
## 12. Limitation of Liability & Disclaimers
|
||||
|
||||
12.1. **Disclaimer of Warranties**: EXCEPT AS EXPRESSLY STATED IN THIS AGREEMENT, THE COVERED THREEFOLD SOFTWARE AND SUPPORT SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE." THREEFOLD MAKES NO OTHER WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. THREEFOLD DOES NOT WARRANT THAT THE COVERED THREEFOLD SOFTWARE WILL BE ERROR-FREE, UNINTERRUPTED, OR SECURE.
|
||||
|
||||
12.2. **Limitation of Liability**:
|
||||
a. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER PARTY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES (INCLUDING LOSS OF PROFITS, DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES) ARISING OUT OF OR RELATING TO THIS AGREEMENT, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STATUTE, OR ANY OTHER LEGAL THEORY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
|
||||
b. TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY'S TOTAL AGGREGATE LIABILITY TO THE OTHER PARTY ARISING OUT OF OR RELATING TO THIS AGREEMENT SHALL NOT EXCEED THE TOTAL LICENSE FEES PAID OR PAYABLE BY PROVIDER TO THREEFOLD DURING THE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.
|
||||
|
||||
12.3. **Exclusions**: The limitations in Section 12.2 shall not apply to: (a) a Party's indemnification obligations (if any are separately agreed); (b) a Party's breach of its confidentiality obligations under Section 10; (c) a Party's infringement or misappropriation of the other Party's intellectual property rights; or (d) liability for fraud, gross negligence, or willful misconduct.
|
||||
|
||||
## 13. Dispute Resolution
|
||||
|
||||
13.1. **Negotiation**: In the event of any dispute, claim, question, or disagreement arising from or relating to this Agreement, the Parties shall first use their best efforts to settle the dispute through good faith negotiations between designated representatives who have authority to settle the controversy.
|
||||
|
||||
13.2. **Mediation**: If negotiations do not resolve the dispute within [e.g., thirty (30) days], the Parties agree to endeavor to settle the dispute by mediation administered by [Specify Mediation Body, e.g., a mutually agreed mediator or an organization like JAMS/ICC] before resorting to arbitration or litigation.
|
||||
|
||||
13.3. **Governing Law & Jurisdiction**: This Agreement shall be governed by and construed in accordance with the laws of Dubai, United Arab Emirates, without regard to its conflict of laws principles. The Parties irrevocably submit to the exclusive jurisdiction of the courts of Dubai, United Arab Emirates for any legal action arising out of this Agreement that is not resolved by negotiation or mediation. The United Nations Convention on Contracts for the International Sale of Goods shall not apply to this Agreement.
|
||||
|
||||
## 14. General Provisions
|
||||
|
||||
14.1. **Notices**: All notices, requests, consents, claims, demands, waivers, and other communications hereunder shall be in writing and addressed to the Parties at the addresses set forth on the first page of this Agreement (or to such other address that may be designated by the receiving Party from time to time). Notices shall be deemed effectively given: (a) when received, if delivered by hand; (b) when received, if sent by a nationally recognized overnight courier (receipt requested); (c) on the date sent by email (with confirmation of transmission), if sent during normal business hours of the recipient, and on the next business day, if sent after normal business hours of the recipient.
|
||||
|
||||
14.2. **Assignment**: Neither Party may assign or transfer any of its rights or delegate any of its obligations hereunder, in whole or in part, by operation of law or otherwise, without the prior written consent of the other Party, which consent shall not be unreasonably withheld or delayed. Notwithstanding the foregoing, ThreeFold may assign this Agreement in its entirety, without consent of the Provider, in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets.
|
||||
|
||||
14.3. **Force Majeure**: Neither Party shall be liable or responsible to the other Party, nor be deemed to have defaulted under or breached this Agreement, for any failure or delay in fulfilling or performing any term of this Agreement (except for any obligations to make payments), when and to the extent such failure or delay is caused by or results from acts beyond the impacted Party's reasonable control, including, without limitation: acts of God; flood, fire, earthquake, or explosion; war, invasion, hostilities, terrorist threats or acts, riot, or other civil unrest; actions, embargoes, or blockades in effect on or after the date of this Agreement; national or regional emergency; strikes, labor stoppages or slowdowns, or other industrial disturbances; or shortage of adequate power or telecommunications.
|
||||
|
||||
14.4. **Entire Agreement**: This Agreement, including all Appendices attached hereto, constitutes the sole and entire agreement of the Parties with respect to the subject matter contained herein, and supersedes all prior and contemporaneous understandings, agreements, representations, and warranties, both written and oral, with respect to such subject matter.
|
||||
|
||||
14.5. **Severability**: If any term or provision of this Agreement is invalid, illegal, or unenforceable in any jurisdiction, such invalidity, illegality, or unenforceability shall not affect any other term or provision of this Agreement or invalidate or render unenforceable such term or provision in any other jurisdiction.
|
||||
|
||||
14.6. **Amendments & Waivers**: No amendment to or waiver of any provision of this Agreement shall be effective unless in writing and signed by both Parties. No waiver by any Party of any of the provisions hereof shall be effective unless explicitly set forth in writing and signed by the Party so waiving.
|
||||
|
||||
14.7. **Relationship of the Parties**: The relationship between the Parties is that of independent contractors. Nothing contained in this Agreement shall be construed as creating any agency, partnership, joint venture, or other form of joint enterprise, employment, or fiduciary relationship between the Parties.
|
||||
|
||||
## 15. Appendix A: Covered ThreeFold Software (Indicative List)
|
||||
|
||||
* As defined in Section 2.2: "All software deployed or made available by ThreeFold via the official TF Grid marketplace and utilized by the Provider in their provision of Certified Services."
|
||||
* Key examples include (but are not limited to):
|
||||
* Zero-OS (ZOS) - All versions officially supported by ThreeFold.
|
||||
* Mycelium Core Networking Components - All versions officially supported by ThreeFold.
|
||||
* Official TF Grid Marketplace Platform Software (components directly managed by ThreeFold).
|
||||
* and other software as used in TF Grid
|
||||
* This list may be updated by ThreeFold upon reasonable notice to the Provider, typically coinciding with new software releases or deprecations.
|
||||
|
||||
## 16. Appendix B: Support Contact Information & Escalation Matrix
|
||||
|
||||
**ThreeFold Support Contact for Certified Providers:**
|
||||
|
||||
* Primary Support Portal/Email: [e.g., support.certified@threefold.io or TBD link to portal]
|
||||
|
||||
**ThreeFold Escalation Matrix:**
|
||||
|
||||
* **Level 1:** Standard Support Request via Portal/Email.
|
||||
* **Level 2:** If S1/S2 response/resolution targets are missed, or for critical concerns:
|
||||
* Escalation Contact Name/Role: see TBD link
|
||||
* Escalation Email: see TBD link
|
||||
* Escalation Phone: see TBD link
|
||||
* **Level 3:** For unresolved critical issues after Level 2 escalation:
|
||||
* Escalation Contact Name/Role: [e.g., VP of Engineering/Operations]
|
||||
* Escalation Email: [e.g., exec-escalation@threefold.io]
|
||||
|
||||
(This Appendix will be populated with specific, current contact details by ThreeFold upon execution of the Agreement.)
|
||||
|
||||
---
|
||||
**IN WITNESS WHEREOF**, the Parties hereto have executed this Service and Node Provider Agreement as of the Effective Date.
|
||||
|
||||
**ThreeFold NV**
|
||||
|
||||
By: _________________________
|
||||
|
||||
Name: _________________________
|
||||
|
||||
Title: _________________________
|
||||
|
||||
Date: _________________________
|
||||
|
||||
**[Provider Name]**
|
||||
|
||||
By: _________________________
|
||||
|
||||
Name: _________________________
|
||||
|
||||
Title: _________________________
|
||||
|
||||
Date: _________________________
|
||||
118
specs/slices.md
Normal file
118
specs/slices.md
Normal file
@@ -0,0 +1,118 @@
|
||||
# Slices
|
||||
|
||||
The fundamental unit of compute resource in the TF Marketplace
|
||||
|
||||
Each slice has
|
||||
|
||||
- compute e.g. 1 vcpu
|
||||
- memory (typically a multitude of 4 GB)
|
||||
- ssd storage capacity e.g. (200 GB)
|
||||
- min uptime (guaranteed by the provider, will lose TFP points if not achieved)
|
||||
- min bandiwdth (guaranteed by the provider)
|
||||
- passmark
|
||||
- reputation (as build up over time and measured by the ThreeFold system)
|
||||
- optional: public IP address (v6 or v4)
|
||||
- optional: certification flag (indicates the slice is provided by a [certified](./certified.md) farmer with ThreeFold support)
|
||||
- pricing in [TFP](./tfp.md) per hour/day/month/year (farmer can change the price)
|
||||
|
||||
The farmer has lot of freedom to define these oaraneters
|
||||
|
||||
## Farmers (Resource Providers)
|
||||
|
||||
* **Responsibilities:**
|
||||
* Register their hardware nodes (computers) with the platform.
|
||||
* Set pricing for their available capacity (Slices), guided by platform recommendations or within defined price bands.
|
||||
* Define and commit to Service Level Agreements (SLAs) for bandwidth and uptime.
|
||||
* **Compensation:** Earn TFP based on the utilization of their registered capacity.
|
||||
* **Monitoring:** Access to a UI to view their node status, earnings, and utilization metrics.
|
||||
* **Risk:** Subject to "slashing" (loss of accrued TFP) if their nodes fail to meet committed SLAs.
|
||||
|
||||
## Famer defines the slices
|
||||
|
||||
The TF Marketplace
|
||||
|
||||
- Users acquire slices through the [Marketplace](marketplace.md)
|
||||
- Slices are derived from physical nodes registered by "Farmers"
|
||||
- Example a node with
|
||||
- 25,000 passmark
|
||||
- 16 vcores
|
||||
- 32GB RAM total capacity
|
||||
- 2 * 1 GB SSD capacity
|
||||
- no pub ip addresses
|
||||
- can deliver following slices
|
||||
- 32 GB with 16 cores, 2 TB, 25.000 passmark
|
||||
- 2 x 16 GB with 8 cores and 1 TB, 12500 passmark
|
||||
- 4 x 8 GB with 4 cores and 0.5 TB
|
||||
- 8 x 4GB with 2 cores and 0.25 TB per slice (8 slices)
|
||||
- farmer defined SLA
|
||||
- 99.8%
|
||||
- min 1 Mbit/sec
|
||||
- farmer defines price
|
||||
- e.g. hour price is 2x monthly price is 2x yearly price and is 10 TFP
|
||||
- The platform dynamically recalculates available slices on a node post-reservation
|
||||
- e.g. a user buys 16 GB slice, means now only 1x 16 GB left, or 2x 8GB or 4x 4GB ...
|
||||
|
||||
## Management Features
|
||||
|
||||
The user can do the following with a slice:
|
||||
|
||||
- **Lifecycle Management**:
|
||||
- OS deployment support for standard operating systems (Ubuntu, Alpine Linux, etc.)
|
||||
- Start, stop, reboot capabilities
|
||||
- **Data Operations**:
|
||||
- Backup functionality
|
||||
- Restore capabilities
|
||||
- **Portability**:
|
||||
- Export & import functionality e.g. to S3 or TF Quantum Safe Storage System
|
||||
- **Ownership & co-administration rights**:
|
||||
- Transferable between users
|
||||
- Can be shared among multiple users
|
||||
|
||||
## Marketplace Dynamics
|
||||
|
||||
- **Pricing**:
|
||||
- Farmers set prices for their node capacity/slices
|
||||
- Pricing may follow platform-defined min/max brackets
|
||||
- Platform may provide pricing recommendations
|
||||
- **Discovery**:
|
||||
- Users browse available slices using filters:
|
||||
- Geographic location
|
||||
- Node reputation
|
||||
- Uptime statistics
|
||||
- Bandwidth availability
|
||||
- Price ranges
|
||||
- Certification status (see [Certified](./certified.md))
|
||||
- **Billing Models**:
|
||||
- Flexible terms available:
|
||||
- Per hour usage
|
||||
- Per month subscription
|
||||
- Per year commitment
|
||||
- Discounts available for longer-term commitments
|
||||
- **Order System** (Future Enhancement):
|
||||
- Buy/sell order book
|
||||
- Users can place bids for VMs meeting specific criteria:
|
||||
- Target price
|
||||
- Preferred location
|
||||
- Minimum reputation score
|
||||
|
||||
## Networking
|
||||
|
||||
- All slices are natively integrated with the "Mycelium" network
|
||||
- Connected to the broader TF Marketplace
|
||||
|
||||
## Access States
|
||||
|
||||
- **Full Access**:
|
||||
- User has complete control over the slice
|
||||
- Direct management of all aspects
|
||||
- **Managed Access**:
|
||||
- User owns the slice
|
||||
- Direct access might be restricted if a platform-managed "Solution" is running on it
|
||||
|
||||
## Primary Use Cases
|
||||
|
||||
- Running general-purpose VMs
|
||||
- Running AI workloads
|
||||
- Hosting specialized executors (e.g., "Heroscript executor" - planned for Phase 2)
|
||||
- Serving as the underlying infrastructure for "Solutions"
|
||||
- Supporting serverless functions
|
||||
56
specs/tfp.md
Normal file
56
specs/tfp.md
Normal file
@@ -0,0 +1,56 @@
|
||||
# TFP
|
||||
|
||||
- TFP = TFPoint
|
||||
- TFT = ThreeFold Token
|
||||
- PEAQ = the DePIN token from the Peaq Network System
|
||||
|
||||
## TFP Price and Value
|
||||
|
||||
- 1 TFP = 0.1 USD (fixed price)
|
||||
- TFP serves as a stable medium of exchange within the ThreeFold ecosystem
|
||||
|
||||
## Liquidity Pools
|
||||
|
||||
The following liquidity pools enable exchange between TFP and other currencies:
|
||||
|
||||
### Fiat - TFP Pool
|
||||
- Users can purchase TFP with fiat currency (USD, EUR, etc.)
|
||||
- The exchange rate is fixed at 0.1 USD per TFP
|
||||
- Provides direct entry into the ThreeFold ecosystem for new users
|
||||
|
||||
### TFP - TFT Pool
|
||||
- Allows exchange between TFP and ThreeFold Tokens (TFT)
|
||||
- Enables token holders to utilize the marketplace
|
||||
- Exchange rates will follow market dynamics
|
||||
|
||||
### TFP - PEAQ Pool
|
||||
- Facilitates exchange between TFP and PEAQ tokens
|
||||
- Connects the Peaq Network ecosystem with ThreeFold
|
||||
- Exchange rates will follow market dynamics
|
||||
|
||||
|
||||
## revenue split & locks
|
||||
|
||||
- revenue gets split between validators / threefold & the provider
|
||||
- the provider part gets locked in for 3 months, slashing will happen on those 3 months if SLA not achieved.
|
||||
|
||||
## Staking
|
||||
|
||||
- new farmers will have to stake TFP, this will be shows when users select a node
|
||||
- existing farmers can optionally stake TFP
|
||||
|
||||
## Slashing
|
||||
|
||||
- if Service providers don't live up to the SLA they loose all or part of their Staked/Locked TFP see above
|
||||
|
||||
## Discount System
|
||||
|
||||
- Users can lock TFP for a chosen period (X months)
|
||||
- The amount of locked TFP determines the user's discount level
|
||||
- Higher amounts of locked TFP result in greater discounts
|
||||
- The service provider (e.g. farmer) defines discount tiers based on locked TFP amounts
|
||||
- Typical discount tiers:
|
||||
- 100-500 TFP: 5% discount
|
||||
- 501-1000 TFP: 10% discount
|
||||
- 1001-5000 TFP: 15% discount
|
||||
- 5001+ TFP: 20% discount
|
||||
Reference in New Issue
Block a user