Keeping tabs on #IO @ionet's latest developments after the attack:
After the attack on April 25, the team rushed to address the situation and basically wrapped it up the same day, so it won’t affect the worker airdrop.
1. Currently, the workers are running with an additional layer of #oauth verification, requiring a #token to operate, which helps solve the #id leak that led to the attack;
2. Regarding the #fake GPU hardware (virtualized or otherwise), the official report mentioned using #pow for checks, which is a solid approach, but we’ll have to see if it becomes the final solution;
3. This incident serves as a wake-up call for other projects, reminding us that #security should always come first; respect the market and respect crypto.
After the attack on April 25, the team rushed to address the situation and basically wrapped it up the same day, so it won’t affect the worker airdrop.
1. Currently, the workers are running with an additional layer of #oauth verification, requiring a #token to operate, which helps solve the #id leak that led to the attack;
2. Regarding the #fake GPU hardware (virtualized or otherwise), the official report mentioned using #pow for checks, which is a solid approach, but we’ll have to see if it becomes the final solution;
3. This incident serves as a wake-up call for other projects, reminding us that #security should always come first; respect the market and respect crypto.