1. Voluntary participation and authority #
Enroll only equipment you own or are expressly authorized to administer and contribute. Check employer, landlord, hosting, cloud, insurer, electricity, network and software-license restrictions. You are responsible for permissions from anyone whose equipment, connection or account is used. Enrollment does not create employment, a partnership, an agency relationship or a right to compensation.
Keep nodes private unless you deliberately enable eligible shared participation. A private node does not make the host immune to compromise. Published participation controls, capability restrictions and local storage boundaries determine what the agent may do; enabling a capability authorizes its corresponding operations.
2. Hardware safety and operating limits #
GPU workloads can cause sustained high utilization, heat, power draw, fan noise, accelerated component wear and storage writes. Failures can include thermal shutdown, component damage, electrical faults, data loss, loss of warranty coverage and, with unsafe equipment or conditions, fire or physical injury.
The node owner is responsible for installation, adequate cooling and ventilation, safe power delivery, maintenance, manufacturer limits, thermal and power controls, monitoring, backups, insurance decisions and timely intervention. Set conservative limits and stop participation whenever the equipment or environment is unsafe. Scheduling limits and agent telemetry are not a certified hardware safety system, and EIZO does not guarantee temperature control or prevention of equipment failure.
Participating node owners bear ordinary participation costs and hardware wear and losses attributable to their own configuration, maintenance or unsafe operation. This allocation does not excuse misconduct or liabilities the operator cannot lawfully exclude.
3. No authority to charge EIZO #
Unless the operator expressly agrees otherwise in a separate written agreement with an authorized signatory, the owner bears all electricity, cooling, bandwidth, ISP, cloud or GPU rental, storage, licensing, repair, replacement, insurance and tax costs incurred by participation. EIZO does not order these services on the owner’s behalf or promise to reimburse them.
Owners cannot bind EIZO to a purchase, subscription or other obligation; issue charges to EIZO; represent themselves as its purchasing agents; or treat CRED, a workload assignment or an enrollment acknowledgment as an agreement to pay an invoice. Cloud auto-scaling, metered connections and third-party billing must be limited and monitored by the owner.
4. Remote execution, updates and files #
Enabled agent capabilities can inspect system and model inventory, transfer files over approved paths, invoke ComfyUI workflows, manage allowed files, and perform supported maintenance or updates. File deletion and some updates can be irreversible. The owner must configure permitted directories, storage budgets and credentials before enabling operations, and maintain recoverable backups.
Run workloads with dedicated accounts, least privilege and appropriate isolation. Keep unrelated personal data, credentials and sensitive workloads off contributed environments. Models, custom nodes and dependencies can execute code and introduce supply-chain risks. Signed updates help authenticate releases but do not guarantee bug-free software. Application quotas are not a substitute for operating-system isolation or hard disk limits.
Owners may pause or disconnect participation. Disconnection may interrupt active jobs and affect contribution credit. Pausing prevents further assignments but must not be assumed to kill an already running process or remove transferred data; check the running workload and use supported cancellation or shutdown controls.
5. Content access, confidentiality and reports #
A shared-node operator may be able to inspect inputs, prompts, outputs and associated user information for work processed on the host. This access exists for operating the node and dealing with abuse; it does not grant ownership, a publicity license or permission to copy, train on, sell or redistribute another user’s work.
Owners must protect data encountered during processing and avoid unnecessary retention. Use node review and reporting tools for suspected violations and preserve only the minimum evidence lawfully needed. Do not publish harmful material as proof, investigate by generating more of it or disclose identifying information publicly. Use appropriate emergency or statutory reporting channels when required.
Owners are responsible for lawful operation and responding appropriately to problems they encounter. These terms do not require reading every file or impose a general obligation to proactively monitor all content. Users remain responsible for their submissions; operators retain their own legal obligations.
6. Credits, withdrawal and responsibility #
Only eligible, recorded contributions earn CRED under the applicable rules. Failed, fraudulent, duplicate or unverifiable work may not qualify. No minimum volume, utilization, earnings or resale value is promised. Tax or accounting treatment of any benefit is the participant’s responsibility under applicable law.
Before withdrawing, pause new work, resolve or cancel active tasks, complete authorized transfers where feasible, revoke credentials and remove service data according to applicable retention obligations. The Terms liability carve-outs apply here. Participation is not a blanket waiver of claims against EIZO for its own legally actionable conduct.
EIZO