All Collections
FAQs and Troubleshooting
How To Stay Safe In Web 3.0
How To Stay Safe In Web 3.0
Marcus Kelly avatar
Written by Marcus Kelly
Updated over a week ago

While transitioning to Web 3.0 can be a difficult learning curve, it's easy to forget how important security is since we have multiple safeguards in Web 2.0.

This article will teach you some ways on how to protect yourself when you are in full custody of your assets.

1. Consider encrypting your hard drive

2. Keep your Operating System and applications up to date by applying all patches and updates in a timely manner

3. Use antivirus and keep its signatures up to date

4. Use KeePassXC to safely store all your passwords, and keep an updated copy of your KeePass database file in a pen drive that you keep in a safe place

5. Protect all your online accounts with strong passwords, and set up multi-factor authentication wherever possible

Strong password: minimum of 10 characters, including lower-case, upper-case, digits, and symbols

Idea: use three words that are not related to each other, but are easy to remember. Use a special character as a separator and add at least a number

Example: Topic3-Starfish5-Commander1

6. Do not reuse passwords across different accounts

7. Use Brave as your default web browser and install the following security-related add-ons:

8. Always check that all websites you visit use HTTPS with a valid certificate. Never accept warning alerts when accessing HTTPS websites with an invalid certificate.

An example is shown below:

9. Disconnect wallets you use such as MetaMask from all dapps after use

10. Do not mix work-related accounts with personal accounts

11. Do not click on any suspicious links sent by email. Always confirm the sender, and also consider confirming the target link by placing the mouse over the target link, without clicking it, as shown below:

Please remember that you are in full custody of your assets in web 3.0.
Relying on third parties such as Centralised exchanges is not advised as they can suffer their own strings of issues.

Did this answer your question?