MASQ Network
Download MASQ Nowmasqbrowser.com
  • 🌐MASQ Network
    • What is MASQ Network?
    • Official Links 🔗
    • FAQ
    • MASQ Comparison 🆚
  • 🔷MASQ Token
    • Token Economy
    • Bridge to Base
    • Contract Addresses
  • 💻MASQ Web3 Privacy Browser
    • Install Requirements
      • tMASQ Testnet Tokens
      • Using Installer files on MacOS/Linux
      • System Cleanup
    • MASQ Browser FAQs (Testnet)
    • Updating MASQ web3 Browser
      • Breaking Change Releases
      • Over-the-Air Updating
    • Providing Feedback
    • Troubleshooting
      • Checking MASQ Browser Version
      • Port 53 Problems (common to Windows)
      • Port 80 (common to Windows)
      • MacOS User Startup Issue
  • 🖱️MASQ Extension App
  • 📑Core Concepts
    • Mesh Network (dMeshVPN)
    • MASQ Neighborhoods
      • MASQ "Suburbs"
    • Gossip Protocol
    • CORES Packages
      • Life of a CORES Package
    • Encryption Methods
    • Clandestine Routing
  • 👨‍💻Advanced Use
    • MASQ Node from CLI
      • Configuration Methods
      • masq Interface
      • MASQ Daemon Commands
      • Configuring MASQ Node
      • MASQ Node CLI FAQ
    • CLI Startup Guides
      • MASQ CLI - Windows
      • MASQ CLI - Linux
    • Setting MASQ Wallets
    • Blockchain Service Endpoint
    • Port Forwarding
    • Compiling MASQ Node
    • Common Challenges
      • Firewall Exceptions
      • Port 53 Problems? (usually in Windows)
      • User permissions --real-user
  • 📦Resources
    • GitHub
    • X/Twitter
    • Telegram
    • Discord
    • Blog
  • Legal
    • Disclaimer
    • Privacy Policy
Powered by GitBook
On this page
  1. Core Concepts

CORES Packages

A CORE(s) package is a series of instructions bundled in a way that allows each node within the network to receive just enough information to make a decision on how to handle a request. CORES stands for Client-Origin-Relay-Exit-Server

CORE(s) packages contain layers of requests that inform nodes how to perform one of three actions.

  1. Create the request

  2. Pass the request along

  3. Process the request.

Each Node that handles a CORES package plays a specific role in the life-cycle of the package route:

  • Client: This is the device that is initializing the request such as a browser, or a video game.

  • Originator: The identity of the originating request node.

  • Relay: Identifies Nodes that will be used to hop along routes to get to its destination.

  • Exit: The exit node will make the true web request on behalf of the originator and send it back along the route stack.

  • Server: Information about the server that is hosting the requested information.

PreviousGossip ProtocolNextLife of a CORES Package

Last updated 1 year ago

📑