• IO will serve as a governance token (the unit that affects the decisions made by the project management). With these tokens, token holders will have the opportunity to determine the future direction of the project and share their creative ideas about the project by creating new proposals. Additionally, the IO token will also be given as a reward specifically to AI developers to encourage them to create AI-related content relevant to IO.net.
• After TGE, it is aimed to establish more partnerships and increase token distribution. In this way, workers will be incentivized to keep their nodes on the network without losing their connection.
• Rewards will be determined by the TFLOPS a card can achieve. (TFLOPS is basically a measurement system that indicates the computational capacity of the GPU/CPU. This capacity also reflects the real-world performance of these cards in the AI workloads that will be needed in the future.), Bandwidth and TFLOPS will be very important factors. Additionally, the availability of these resources will be extremely important. This means that rewards will be distributed according to the TFLOPS they provide, rather than GPU/CPU models and brands.
• A World Coin-style whitepaper, intended to be highly transparent, will be shared on April 15 by hushky. The targeted payback period of the investments made is expected to be less than 1.5 years (CRAZY PAYBACK TIME). These payback terms are valid if the node is IDLE and available for the entire period. (worst possible scenario for the machine) . If you get the job, you will receive even more rewards and this will shorten the payback period significantly. The sole purpose of the airdrop is to test the io.net network, conduct stress tests and familiarize users with the reward system. So current payout scheme is irrelevant to the one planned after TGE.
• End-to-end encryption is applied to prevent data leaks and all data passing through GPUs is encrypted, making all transfers meaningless to 3rd parties. IO.net does not intend to collect, store or use any data from customers. All data provided during the hiring process will always be transmitted through the established secure protocols.
• Regarding the recent “fake worker” incident, the team found a workaround to catch bad actors. Fast and heavy workloads are directed to workers that are detected to be fake. Since there is no processing power attached to these fake workers, they are quickly banned from the system and marked as fake because they cannot complete the job.
• There are some frontend restrictions due to the recent migration to DigitalOcean.
• Many packages are outdated and need to be updated, and efforts are ongoing to resolve this issue during TGE. It was determined that one problematic container assigned work to some workers even though it did not receive the job. All these problems will be solved after the TGE, which is expected to take place at the end of April.
• API access will not be shared with users yet, but for now one person has received API access for a technical project he is developing for IO.net.
• News about the LLM bounty and award will be announced soon, it will be for one person only and the award will be $1000.
• Level 5 and above members will have the privilege of sending any links in chats. This decision was made to prevent scammers from sending malicious links to chats.