Urgent.News

What's breaking now, across thousands of outlets.

Tech

BitMessage: What If Communication Could Become a Source of Decentralized Participation?

BitMessage is an experimental protocol proposal built around Proof-of-Presence-and-Meaning (PoPM), a participation mechanism designed to connect everyday communication with cryptographically verifiable protocol events, distributed infrastructure, and a native economic system. This manifesto describes the architecture, threat model, tokenomics, privacy model, and research requirements behind the…

BitMessage is an experimental protocol that explores the idea of decentralized communication as a means for network participation. This manifesto outlines the architecture, security considerations, token economics, privacy features, and research needs for the BitMessage ecosystem. The protocol is not claimed to be secure or fully implemented, but rather a proposal to be evaluated, challenged, tested, and refined by the community.

Modern consensus mechanisms, such as Proof-of-Work and Proof-of-Stake, rely on scarce resources like computation and capital to organize participation. These models, while not inherently flawed, raise questions about what resource should determine access to economic opportunities in a decentralized communication network. BitMessage suggests that the communication activity itself should play a central role in establishing participation rights.

The protocol introduces Proof-of-Presence-and-Meaning (PoPM) as a novel participation mechanism. PoPM connects everyday communication with cryptographically verifiable protocol events and a native economic system. It separates the participation and reward mechanism from the finality mechanism of the ledger, allowing users to engage in the network's economy without needing to become industrial miners or large capital holders.

PoPM is built on several key components, each serving a distinct purpose. Behavioral entropy is introduced as a means of simulating human-like interaction without relying on surveillance techniques. Epoch challenges are generated to discourage the replaying of prepared data. Each component contributes to the overall security and robustness of the protocol.

Behavioral entropy is used to create a unique commitment for each participant, tying their participation to the local entropy without revealing the underlying interaction data.

Protocol activity is divided into discrete epochs, each with its own fresh network challenge derived from the finalized network state and a protocol randomness source. This ensures that previously prepared participation data becomes unsuitable for new epochs, preventing potential attacks. The challenge is not controlled by any individual participant, as it is derived from the network state and randomness, rather than being a mining nonce or static input.

In summary, BitMessage proposes an innovative approach to decentralized communication by integrating participation and economic incentives directly into the protocol. By leveraging behavioral entropy, epoch challenges, and a well-defined participation mechanism, BitMessage aims to create a more equitable and secure network for everyday communication.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The EDI 810, Decoded: What an Invoice Actually Looks Like on the Wire

Every EDI series I write eventually gets to the invoice, because the 810 is where integrations stop being an IT project and start being a money project.

  • The 810 invoice links to 850 PO and 856 ASN, forming order-to-cash sequence
  • IT1 loop contains line item details, prone to matching issues
  • TDS segment represents invoice total in implied-decimal cents, error-prone

The gap limit is a compatibility contract, not a scanner setting

An HD wallet scanner quits twenty unused addresses after the last one that received money. An address handed out past that window still belongs to your key, your own indexer will watch it happily, and…

  • Gap limit is a compatibility contract, not a scanner setting
  • Unused addresses after gap limit belong to keyholder
  • BIP44 standard sets gap limit at twenty unused addresses

More from Sunday 4 October →