173 lines
6.9 KiB
Markdown
173 lines
6.9 KiB
Markdown
# 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)
|
|
|
|
## [Mycelium Nodes](mycelium_nodes.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
|
|
|
|
|
|
## [Agentic Apps](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 |