01Obsidian

On-chainMessaging

A blockchain with a native messaging layer. Store data directly on the blockchain. No smart contracts, no gas fees, no complexity. Just sign and send.
02Section 02

The problemWith data today

Centralized platforms

  • Twitter / X can delete your posts.
  • Facebook can ban your account.
  • Cloud providers can shut down your storage.
  • Companies can go bankrupt, taking your data.

The Ethereum gap

  • Gas costs make storing data prohibitively expensive.
  • State bloat concerns limit what can be stored.
  • Smart contracts add complexity for simple data needs.
  • No dedicated messaging protocol. Everything goes through EVM.

What if you just want to publish a message with finalized ordering and archive-backed retrieval, without deploying a contract or paying per-byte gas fees?

03Section 03

The obsidianSolution

Obsidian extends Ethereum with a dedicated messaging layer that operates alongside the traditional transaction system. Messages bypass the EVM entirely, reducing overhead and enabling on-demand data publishing.

Silica protocol.

Messages stored in the blockchain itself, not hash references.

Feeless standard lane.

Zero gas fees for basic messages using VDF (Verifiable Delay Function).

Archive-backed history.

On-chain commitments plus archive retrieval, verified by consensus.

EVM compatible.

Use MetaMask, Hardhat, ethers.js. All your favorite tools.

04Section 04

How on-chainMessaging works

The traditional way (Ethereum)

// Deploy a contract first
contract MessageBoard {
  event Message(address sender,
                string content);

  function post(string content) {
    // Costs gas for every byte!
    emit Message(msg.sender, content);
  }
}

Requires Solidity knowledge, contract deployment, and gas fees for every message.

The Obsidian way

// Just send a message
await provider.send(
  "eth_sendMessageBlob",
  [{
    from: myAddress,
    data: "0x" + toHex("Hello"),
    signature: sig,
    nonce: nonceHex,
    chainId: "0x1a5"
  }]
);

No contract needed. No deployment. No gas fees for standard messages.

Lifecycle Message lifecycle

Step 01

Create and sign.

App creates payload, wallet signs with chainId and nonce.

Step 02

Submit.

Send via eth_sendMessageBlob RPC to any node.

Step 03

Route and include.

Routes to PM (paid) or SM (feeless), assigned to lanes.

Step 04

Finalize and archive.

Added via Silica Protocol, finalized on-chain and retrievable through archive nodes.

05Section 05

On-chain vsOff-chain

PlatformDeletableEditableSurvives company death
Twitter / XYesYesNo
AWS S3YesYesNo
IPFSIf unpinnedNoMaybe
ObsidianNoNoYes
06Section 06

Use cases forOn-chain messaging

Social protocols.

Build decentralized social apps where users truly own their content. Posts, comments, and profiles gain finalized on-chain ordering with archive-backed retrieval.

Attestations and proofs.

Issue verifiable credentials, certificates, and attestations that can never be revoked or tampered with.

Audit trails.

Create immutable logs for compliance, legal records, and enterprise audit requirements.

Content publishing.

Publish articles, journalism, and creative work that can never be censored or taken down.

IoT data logging.

Store sensor data, device telemetry, and machine logs with cryptographic proof of origin.

Decentralized identity.

Anchor identity claims, reputation scores, and profile data to an immutable record.

Start building with on-chain messaging.

Deploy your first message in minutes. No smart contracts required.