📖
Mel docs
HomeOld docs
  • A post-blockchain Web3
  • Conceptual wiki
    • Data model
    • Consensus
    • MEL: trustless sound money
    • Governance-free neutrality
    • Covenants
    • Light clients
    • Network architecture
    • Melnet: the P2P layer
    • What belongs on-chain?
  • Developer guides
    • Overview
    • 🛠️Gibbername: your first off-chain composable protocol
      • melprot: a quick intro
      • Design
      • Implement
      • Use
      • Next steps
    • 💰Wallets
      • Setup and installation
      • Sending money
      • Swapping tokens
    • 🪙Getting tokens
      • Melmint overview
      • Using melminter
      • Melmint arbitrage
    • 🤖Run a full node
      • Melnode quick start
      • Basic replica node
      • Setting up a local simnet
  • 🌉Szaldi guide
    • Bridge your coins
    • Architectural overview
  • Resources
    • Yellow Paper
    • Frequently asked questions
    • MelVM spec
Powered by GitBook
On this page
Edit on GitHub
  1. Conceptual wiki

Network architecture

PreviousLight clientsNextMelnet: the P2P layer

Last updated 2 years ago

In Mel, participants in the network can be divided into three roles:

  • Staker nodes are full nodes directly participate in the proof-of-stake . They have stake, denominated in SYM, locked up on-chain, and receive consensus voting power in exchange.

  • Replica nodes are full nodes that do not have SYM stake, but replicate and validate the output of the staker consensus. They not only provide a “CDN” for the blockchain, but more importantly by using a , they shut the network down if a quorum of stakers produces invalid results.

  • Light clients, also known as "clients", merely consume the security enforced by the stakers and replicas. They do not replicate the blockchain, but trust consensus proofs provided by the stakers that commit to a particular blockchain state. As long as the network as a whole is working correctly, light clients cannot be fooled. , embedded into apps as libraries (like ), are the cornerstone of Mel's off-chain composable vision.

Note: "stakers" are called "validators" in most other blockchains. We intentionally use a different word because:

  • Staker normalizes self-staking rather than pooled staking, and makes it clear that delegating stake to a staker is similar in trust to giving them a loan.

  • Validator is highly misleading, since the main purpose of consensus is not to "validate" blocks, but to produce and decide on them. In fact, "validation" describes the job of normal full nodes much better!

The staker and replica nodes form a P2P gossip network using the ; light clients can also talk the same protocol to query these nodes.

HTTP-based melnet protocol
consensus
Trustless light clients
melprot
nuking procedure