Platform Roles
The ZopToken platform primarily involves four types of roles.
Platform Operator
The platform operator is responsible for building and maintaining ZopToken's core systems, including:
- Device management
- Task scheduling
- Key management
- Status monitoring
- Revenue recording
- Withdrawal and settlement processes
- Console and API
- Security and risk control mechanisms
The core responsibility of the platform operator is to enable device resources to be stably onboarded, reasonably scheduled, and continuously monitored.
Device Provider
Device providers can be individual users, studios, or small teams with available devices.
They provide Mac or GPU devices and connect them to the ZopToken network through platform-designated methods.
Device providers typically need to:
- Keep devices online
- Keep the client running normally
- Comply with platform onboarding rules
- Monitor task execution status
- Address device anomalies promptly
After a device completes valid tasks, the provider may receive corresponding revenue according to platform settlement rules.
Service Provider / Data Center
Service providers or data centers typically have bulk devices, stable network connectivity, and hardware maintenance capabilities.
They can connect to the platform in a cluster manner, providing more stable computing resources.
Capabilities suitable for service providers or data centers include:
- Bulk device management
- Unified network and power maintenance
- Cluster monitoring
- Device fault handling
- Onboarding testing with the platform
- Enterprise-level settlement and support processes
Task Requester
Task requesters are the side that needs AI computing resources, which may include internal platform business, enterprise customers, developers, or third-party systems.
They submit or connect AI workloads through the platform, with ZopToken handling resource scheduling and execution management.
Whether task requesters are open, the scope of openness, and API capabilities are subject to the platform's current stage.