IO Best Practices & Security Tips

Summary

This article covers the essential best practices and security guidelines for participating in co-staking on io.net. Following these recommendations can help you protect your assets, avoid scams, and maximize staking rewards.


1️⃣ Use Official Channels Only

To protect your assets and ensure you're interacting with the legitimate io.net platform:

  • Always access io.net through the official website.

  • Type the URL manually or use a bookmark to avoid phishing attempts.

  • Never rely on links from third-party websites, social media, or emails unless verified.



Phishing sites often imitate real platforms. Double-check the URL before entering sensitive information.

2️⃣ Verify Smart Contract Addresses

When staking or unstaking, you’re interacting directly with smart contracts. To stay safe:

  • Confirm smart contract addresses through io.net’s official documentation.

  • Use a blockchain explorer (e.g., Solscan) to verify the contract address before approving any transaction.

  • Be cautious of apps or extensions that prompt you to sign transactions without clear context.


3️⃣ Avoid Unsolicited Offers and Messages

Scammers often impersonate team members on social platforms. Remember:

  • The io.net team will never send you a direct message with staking offers or ask for transfers.

  • Ignore any "exclusive" deals or offers sent via social media or messaging platforms.

  • All legitimate staking activity happens through the official platform.


4️⃣ Secure Your Wallet

A secure crypto wallet is your first line of defense. 


Best practices include:

  • Use a reputable, trusted wallet with strong community reviews.

  • Enable all security features (e.g., password protection, biometric login, two-factor authentication).

  • Keep your recovery phrase and private keys offline and private.

  • Never share your keys or seed phrase—not even with io.net support.


5️⃣ Choose Co-Staking Offers Wisely

Evaluate co-staking offers carefully to reduce risk and improve returns:

  • Consider devices with high Device Reliability Scores.

  • Balance potential rewards with the risk level of the device.

  • Use the io.net Explorer to track real-time device performance and reliability.

Avoid devices with poor uptime or signs of instability—they may result in slashing or loss of rewards.


6️⃣ Monitor Your Co-Staking Positions

Stay informed about the status of your staked devices:

  • Use the Staking Dashboard on the Explorer to track device status and rewards.

  • Enable notifications or set manual reminders to review your stake periodically.

Active monitoring helps you react quickly to issues and maintain earning potential.


7️⃣ Plan Ahead for Unstaking Delays

Unstaking isn’t instant—there are built-in delays for security and system stability:

  • Plan ahead if you need access to your $IO tokens.

  • Expect a 7-day wait after initiating an unstake, followed by a 14-day cooldown.

    • Do note, that due to the way contracts function - it may realistically take up to 16 days.

  • You will not earn rewards during the cooldown period.


8️⃣ Stay Informed Through Official Updates

io.net is an evolving platform. To make the most of your co-staking experience:

  • Follow official io.net channels (e.g., Twitter, Discord, website).

  • Join community discussions for tips and insights from other stakers.

  • Always verify updates through official sources before acting on them.


9️⃣ Recognize and Avoid Phishing Scams

Phishing and impersonation scams are common in crypto communities:

  • Be wary of messages or links that seem too good to be true.

  • Never provide your wallet information to unofficial sources. 

  • Only contact io.net support through official channels (e.g., website ticketing system or verified Discord moderators).

  • Report suspicious activity to help protect the community.


For the latest co-staking tools and updates, visit the official io.net website and join the community on Discord or Twitter.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article