GoPlus Security
  • 🚀Overview
  • 💚Get Started
  • 📡User Security Network
    • Architecture Overview
    • Security Data Layer
      • Types of Risk Data
      • Token Risk Classification
    • Security Compute Layer
      • AVS Operator Guide
    • SecWare Protocol
  • 🤖GoPLus Intelligence
    • GoPlus Intelligence
  • GoPlus SafeToken Protocol
    • GoPlus SafeToken Protocol
  • 🔐Security Module - Chain Native Security Layer
    • Architecture Overview
    • Core Features
    • User Security Life Cycle
    • On-chain Firewall
      • Security RPC
        • GoPlus BNB RPC
        • GoPlus ETH RPC
  • 🟢Ecosystem Role
    • GoPlus Security Governance
    • Data Contributor
    • AVS Operator
    • SecWare Developer
    • Users
    • 🍏Tokenomics
  • 🔎GoPlus Open Research
    • Automated Security Testing
    • Fuzzing Testing
    • Phishing Site Detection
    • Phishing Address Detection
  • 💻API & SDK Integration Guide
  • 🗺️Roadmap
  • 🫶Community & Support
    • Community
  • 📘Glossary
Powered by GitBook
On this page
  1. Security Module - Chain Native Security Layer

User Security Life Cycle

PreviousCore FeaturesNextOn-chain Firewall

Last updated 12 months ago

To address the pressing security concerns in the Web3 space and guide users towards adopting optimal security practices, we have introduced the Web3 User Security Life Cycle (USLC). This framework outlines the necessary steps users should take to protect themselves before, during, and after interacting with Web3 applications and services.

• Pre-Event Phase:

At this initial stage, the focus is on equipping users with the knowledge they need to navigate the Web3 space safely. Before engaging with any Web3 applications or services, such as a Data Website, dAPP, or Dex, users should be presented with up-to-date and accurate security information and risk assessments. Ensuring users are informed about potential threats and equipped with best security practices is crucial. This preventative measure lays the foundation for a secure interaction with Web3 platforms.

• During-Event Phase

As the user progresses to actively engage with Web3 services, they generate and sign transactions in their wallet. After the signing, the security measures are actively at play, with on-chain firewalls and rigorous security protocols operating in real-time to shield the user's assets. This protection extends as the transaction is sent through RPC nodes to the mempool (Step 4), where it's validated in mempool or by validators (Step 5) before ultimately being broadcasted and recorded on the ledger.

• Post-Event Phase

Once the transaction has been broadcast and the ledger is updated (Step 6), post-event security becomes paramount. This phase tackles the risks that linger after the interaction has taken place. It involves steps such as revoking unneeded permissions, conducting ongoing monitoring for anomalous activity, and ensuring that robust recovery solutions are in place to respond swiftly in the event of a security breach. This ensures that even after the transaction is completed, the user's security posture remains strong and resilient against latent threats.

The USLC emphasizes that securing a user’s journey in Web3 is not a one-off event but a cyclical and ongoing process. By diligently addressing the unique challenges inherent at each phase, the GoPlus ecosystem aims to cultivate a safer and more reliable Web3 experience for all users.

🔐
User Security Life Cycle