LogoLogo
DownloadsBlock ExplorerSupport
  • πŸ’‘Introduction to Oxen
  • πŸ“Downloads
  • πŸ†˜Support
  • About the Oxen blockchain
    • πŸ—ΊοΈOverview
    • πŸ“ŠToken economics
      • πŸ”₯Token burning
    • πŸ–₯️Oxen Service Nodes
    • πŸ’“Pulse: PoS on Oxen
      • 🀿Pulse: Deep dive
    • πŸ‘οΈBlink: Instant transactions
  • Using the Oxen Blockchain
    • πŸ“Overview
    • πŸ’°Oxen Wallet & Guides
      • Preparing for GUI Wallet setup (Windows)
      • GUI Wallet setup
      • GUI Wallet Quickstart
      • GUI Wallet Staking
      • Oxen Mobile Wallet Quickstart
      • Mobile Wallet Staking Guide
      • Exporting a CSV of your wallet transaction history
      • CLI Wallet setup (macOS)
      • Oxen Ledger Wallet setup: GUI Wallet
      • Oxen Ledger Wallet setup: CLI Wallet
      • CLI Wallet commands
      • Restoring an Oxen CLI Wallet from seed
      • Restoring an Oxen CLI Wallet from keys
    • πŸ–₯️Service Node guides
      • 🏎️Express service node setup guide
      • 🍺Full service node setup guide
      • πŸ’ΈStaking to a shared Oxen Service Node
      • πŸ›‘Service Node deregistration
      • πŸ› οΈService node tools and upkeep
    • ⛴️Migrating to the new Session Network
      • βœ…Migration Checklist
      • ❓Migration FAQ
      • πŸ”—Connecting to an Arbitrum One RPC Endpoint
      • πŸ”€How to set up an oxend L2 proxy
    • πŸ”‘Using Oxen Name System (ONS)
    • πŸ€“Advanced
      • Service node πŸ“ž RPC calls
      • Daemon πŸ“ž RPC calls
      • Wallet πŸ“ž RPC calls
  • Products built on Oxen
    • πŸ”’Session
      • πŸ“šGuides
        • 🐧Installing on Linux (Debian based distros)
        • πŸ—£οΈSession Open Group Server Setup
          • πŸ“—Read Only Room Setup
      • πŸ”€Oxen Name Service for Session
      • πŸ—οΈNetwork infrastructure
      • πŸ“¨Message routing
      • πŸ“ŽAttachments
    • 🌐Lokinet
      • πŸ“šGuides
        • 🐧Installing on Linux (CLI)
        • 🐧Installing on Linux (GUI)
        • 🐧Linux troubleshooting
        • 🍎Installing on macOS
        • πŸͺŸInstalling on Windows
        • 🍎macOS troubleshooting
        • πŸ“žRun a secure Mumble server over Lokinet
      • πŸ‘‹Exit nodes
      • πŸ§‘β€πŸ’»πŸ§‘πŸ’» SNApps
        • πŸš€Accessing SNApps
        • πŸ–₯️Hosting SNApps
        • πŸ—ΊοΈDomain Names For Lokinet (ONS)
        • ⏺️Configuring SRV Records
Powered by GitBook
On this page
  • Proof of Stake: How does it work?
  • Security benefits of Proof of Stake

Was this helpful?

Edit on GitHub
Export as PDF
  1. About the Oxen blockchain

Pulse: PoS on Oxen

Pulse is Oxen's Proof of Stake consensus mechanism

PreviousOxen Service NodesNextPulse: Deep dive

Last updated 2 years ago

Was this helpful?

Fundamentally, every blockchain β€” including Oxen β€” is exactly what it says in the name: a chain of blocks. One 'block' in the Oxen blockchain is made up of a set of $OXEN transactions which have been deemed valid by the network. But when the network consists of thousands of computers all over the world, how does it come to consensus about the state of the blockchain?

That's where Pulse comes in.

Pulse is Oxen's implementation of the 'Proof of Stake' consensus mechanism, and it forms the foundation of the Oxen Service Node network. Let's dive into how it works and why we use it.

Proof of Stake: How does it work?

In our Proof of Stake (PoS) consensus system, active Oxen Service Nodes are randomly selected to create and publish new blocks of transactions to the blockchain approximately every 2 minutes, with each node being rewarded for doing so.

Once a service node has been selected to create a block, a set of other nodes (the validators) are chosen to validate the new block β€” checking to ensure it doesn't contain duplicate transactions or any other potentially malicious activity. Once these validator nodes have verified the block’s legitimacy, the block is published to the blockchain.

Security benefits of Proof of Stake

In a PoS-based blockchain, an attacker would need to control more than 50% of the total supply of staked or stakeable cryptocurrency tokens in order to carry out a 51% attack (allowing them to publish fake or invalid transactions, re-order the blockchain, etc.).

Acquiring this much of the total supply can be extremely expensive β€” and in some PoS-based blockchains, it be nearly (or completely) impossible. When crypto tokens are staked into nodes, they are locked for a pre-determined amount of time. This means they're removed from the marketplace and can't be bought. If more than 50% of the total cryptocurrency supply for a given blockchain network is staked, a 51% attack becomes extremely unlikely, because for an external attacker (i.e. someone not already invested in the network), buying up or otherwise being able to control enough tokens to control more than half the nodes on the network becomes almost impossible. And there's a second layer of security here, too: if someone does buy up such a huge amount of tokens that they could gain control of the network, they would then be disincentivised from wanting to attack the network simply because attacking the network would harm the value of their tokens β€” once they're invested, they're simply better off acting in good faith, so their tokens gain value rather than losing value.

πŸ’“