ionet-official/productfeedback

Any feedback, create an issue

ProductFeedbaxk

Any feedback, create an issue

productfeedback's Issues

windows的二进制文件无法下载

windows的二进制文件无法下载

Proposal to Prevent GPU Spoofing and Exploitation of Block Rewards

Proposal to Prevent GPU Spoofing and Exploitation of Block Rewards

Introduction

To maintain the integrity and fairness of block rewards, it is crucial to implement measures that prevent bad actors from exploiting the system through the use of spoofed devices. This proposal aims to outline a strategy for minimizing such exploitation and ensuring that block rewards are distributed more equitably among genuine participants.

Objectives

1. Discourage bad actors from using spoofed devices to earn block rewards.
2. Prevent the exponential dilution of block rewards.
3. Provide transparent and actionable feedback for worker verification failures.
4. Implement a fair system for allowing additional worker nodes based on merit.

Proposed Measures

1. Limiting Initial Worker Nodes

Each account should initially be allowed to set up a limited number of worker nodes (e.g., 1-3) for block rewards. This initial restriction will help control the potential abuse of block rewards by spoofed devices.

2. Incentivizing Additional Workers and Preventing Multiple Accounts

To qualify for additional worker nodes, users must meet specific criteria, including:

• Uptime Requirement: Maintain an uptime of X% for all initial workers over a specified period (e.g., 90% uptime over 30 days).
• Proof of Ownership: Provide verifiable evidence, such as screenshots or receipts, showing ownership of additional GPU devices.
• Hashrate Proofs: Submit proof of hashrate for potential worker nodes to demonstrate their capability.
• Decentralized Proof of Uniqueness: Implement a decentralized mechanism to ensure each user can only create one account without relying on traditional identity verification. This could involve:
  • Web of Trust: Leverage a web of trust model where existing trusted users vouch for new users.
  • Blockchain-Based Verification: Utilize blockchain technology to create a tamper-proof record of user accounts and their activity, making it difficult for the same individual to create multiple accounts without detection.
• IP Address Monitoring: Monitor IP addresses used for account creation and worker node activity. Flag and review suspicious patterns, such as multiple accounts originating from the same IP address.

These conditions will help ensure that only genuine participants with legitimate hardware are allowed to add more workers while preventing users from creating multiple accounts to bypass worker node limits.

3. Detailed Verification Feedback

Provide more detailed information on why some workers fail their verification. This information can be derived from logs available at https://github.com/ionet-official/io-net-transparent-device-metric under the pow-logs URL. Key details should include:

• Insufficient hashrate
• Bad network connectivity
• Other relevant issues

This feedback should be displayed on the worker tab in io.net, helping users troubleshoot errors effectively and improve their setup.

4. Additional Measures to Prevent GPU Spoofing

• Regular Audits: Conduct periodic audits of worker nodes to detect and remove spoofed devices. The results and timing of these audits should be transparently displayed to users, fostering a sense of trust and accountability within the team.
• Hardware-Based Attestation: Implement robust verification processes using hardware-based attestation. This involves using specialized hardware to prove the integrity and identity of worker nodes, such as Trusted Platform Modules (TPM) and remote attestation protocols.

Hardware-Based Attestation

Hardware-based attestation involves using specialized hardware to prove the integrity and identity of worker nodes. This can be achieved through:

• Trusted Platform Modules (TPM): Utilize TPM chips present in modern GPUs and motherboards to attest to the hardware’s authenticity and integrity. The TPM can provide cryptographic proofs that the hardware has not been tampered with.
• Remote Attestation: Implement remote attestation protocols that allow worker nodes to prove their hardware configuration and integrity to a remote verifier. This involves:
  • Attestation Key: Each device generates a unique attestation key stored in the TPM.
  • Integrity Report: The device creates an integrity report signed with the attestation key, detailing the hardware configuration and software environment.
  • Verification: The remote verifier checks the integrity report against known good configurations to ensure the device has not been spoofed or tampered with.

5. Dedicated Reporting Page

Create a dedicated page on io.net for users to report potential spoofing of devices. This page should allow users to submit detailed reports, including:

• Description of the issue
• Evidence or screenshots supporting the claim
• Logs or data from the affected worker nodes

This reporting mechanism will help in quickly identifying and addressing spoofing attempts, ensuring the system's integrity.

Conclusion

Implementing these measures will help maintain the integrity of the block reward system by discouraging the use of spoofed devices and ensuring that rewards are distributed fairly. Providing detailed feedback on verification failures will also empower users to troubleshoot and improve their setups, fostering a more transparent and robust ecosystem.

I believe that these steps will significantly enhance the security and fairness of the block reward system. Thank you for considering this proposal. Will be good if this proposal is incentivized if any of the feedback listed is implemented.

[Warning] Verification Failed

I have been running a worker for 11 hours and I got this (Windows laptop)

Launch Forum

We can Launch Forum For Io net

Pls open the code of worker

Any plan to open source

Can't use forgot password on auth0 (to approved token)

Last time I go to https://auth0.io.solutions/activate, I can click forget passwords, then put my email, a link to reset will be sent.

But yesterday, I try many times, nothing send to my email, please recheck your fuction

Pls release the time of rewards in detail

So many people want to know the time ,why not tell people in advance

A few questions about the WORKER on Apple M2 Pro

1. Will it utilize the GPU? I found ionet_device_cache.json and it said "usegpus":"false".
2. I have registered a worker and it shows me running on the WORKER dashboard. So I assume it is connected successfully. But does it have network problem when computing a job? When I do crypto mining, I always set socks5 proxy for a better network performance. Do we have a similar configuration? Is this necessary?
3. I received a job, in the Earnings & Rewards page, it said

   Earnings 0.00
   Job Details Failed
   Compute Hours Hired 1 Hrs 0 Mins
   Compute Hours Served 0 Hrs 17 Mins
   

   my question is why it failed? Is it my worker issue? Or maybe some network problem? In this case I can't get any earnings right?

monitor image not found in docker after started

I startup docker by command from ionet page,but monitor image not found in docker and device is always offline

Allocate to advisors and github team builder

Have submit some feedback for ecosystem ,and pls help to approve ,thx

Some PoW logs are empty

e.g. log_20240510/log_20240510_001951_hashcheck_logs-with-web-gpu-anon.csv

Idea to increase the number of AI users

Is there a way to create a sort of interface like google colab / jupyter where users can code and train their AI models easily from a web interface ? It might encourage AI users and reseachers to take advantages of IO's potential.

My discord username : anasmalki

Proposal for Compensation of Block Rewards for 3080 Cards

Introduction

The issue of the 3080 cards receiving significantly lower block rewards than expected has been resolved, with current block rewards now aligning with expectations. However, during the affected period, 3080 cards were receiving less than half of the block rewards compared to 3060 and 3070 cards. This proposal seeks to address this past discrepancy and ensure fair compensation for affected users.

Objectives

1. Fairly compensate users who were affected by the underperformance of the 3080 cards.
2. Restore trust and confidence within the community regarding the IO team's commitment to fairness and transparency.

Proposed Measures

1. Data Review

Conduct a thorough review of the block rewards data for the period when the 3080 cards were underperforming to accurately determine the shortfall in rewards.

2. Compensation Calculation

Calculate the difference between the expected and actual block rewards received by the 3080 cards during the affected period.

3. Distribution of Compensation

Distribute the calculated compensation to the affected users, possibly in the form of additional block rewards or credits.

Conclusion

Implementing these measures will help maintain the integrity of the block reward system by ensuring that users are fairly compensated for any past discrepancies. These steps will significantly enhance the security and fairness of the block reward system. A reward or acknowledgment for bringing this issue and potential solution to attention would be appreciated. Thank you for considering this proposal.

https://worker.io.net/worker/devices/{id} why do this page always crashed?

linux version don't running success

Proposal: Alert Notification for Worker Readiness Changes

Objective

Implement an alert notification system to notify users via email, Telegram bot, or desktop notification whenever a worker's readiness status changes. This aims to enhance user awareness and responsiveness to changes in the worker's operational status, ensuring timely interventions and improved cluster management.

Background

In a distributed blockchain network, maintaining the readiness of workers is crucial for optimal performance and reliability. Workers may transition through various states such as "Cluster Ready," "Not Block Reward Ready," or "Hired." Immediate awareness of these transitions allows for prompt action, reducing downtime and maintaining the integrity of the network.

Proposal

This proposal outlines the implementation of an alert notification system that will send notifications to users through predefined channels (email, Telegram bot, desktop) when a worker's readiness status changes.

Details

1. Trigger Events:

   • Cluster Ready: Indicates the worker is fully operational and part of the active cluster.
   • Not Block Reward Ready: Indicates the worker is not currently eligible for block rewards, possibly due to failing health checks or other issues.
   • Hired: Indicates the worker has been hired and is preparing to join the cluster.

2. Notification Channels:

   • Email: Notifications sent to a specified email address.
   • Telegram Bot: Notifications sent via a Telegram bot to a predefined chat.
   • Desktop Notification: Pop-up notifications on the desktop for users with the application installed.

3. Implementation Steps:

   1. Identify Readiness State Changes:

      • Implement hooks or listeners within the worker management system to detect state changes.

   2. Notification Service Integration:

      • Email: Use SMTP or a third-party email service (e.g., SendGrid) to send email notifications.
      • Telegram Bot: Create a Telegram bot using the Telegram Bot API to send messages to users.
      • Desktop Notification: Use web or desktop notification APIs/ websockets to send alerts to users' desktops.

   3. Configuration Interface:

      • Develop a configuration interface for users to manage their notification preferences (channel, contact details, etc.).

   4. Message Templates:

      • Create customizable message templates for each type of readiness state change, including relevant details such as worker ID, timestamp, and new state.

4. Security and Privacy:

   • Ensure secure handling of contact information and secure transmission of notifications.
   • Provide an option for users to opt-in and opt-out of notifications.

5. Testing and Validation:

   • Thoroughly test the notification system to ensure reliability and accuracy of alerts.
   • Conduct user acceptance testing with a subset of users before full deployment.

Benefits

• Improved Monitoring: Real-time notifications enable users to monitor worker readiness effectively.
• Prompt Response: Immediate alerts facilitate quick responses to issues, minimizing downtime.
• Enhanced Communication: Multiple notification channels ensure users receive alerts through their preferred medium.

Conclusion

Implementing an alert notification system for worker readiness changes will significantly enhance the ability to manage and maintain the blockchain network's health and performance. This proposal seeks approval to develop and deploy this notification system, ensuring timely and efficient handling of readiness state changes.

Reward Rates

m2 pro and m3 pro has same rates how ? (both 0.5)