01

BLOCKCHAINMESSAGING

Messages with finalized on-chain ordering. When you send a message on Obsidian, it becomes part of canonical chain history with archive-backed retrieval rather than a database entry or an IPFS pin.
02

FINALIZED
HISTORY

Your message → Block 12345 → Archive nodes → Long-term retrieval

When you send a message on Obsidian Chain, it doesn't go to a server that might shut down. It doesn't get stored on a service that might cancel your account. Your message becomes an immutable part of the blockchain's history.

1

Signed by You

Cryptographic proof of authorship that cannot be forged or falsely attributed.

2

Included in Block

Validators commit your message to canonical chain history through the lane-header path.

3

Finalized History

Casper FFG makes ordering irreversible, while archive nodes keep message data retrievable over time.

03

BLOCKCHAIN
GUARANTEES

Immutable

Cannot be edited after inclusion

Undeletable

No admin can remove it

Available

Lane committees attest availability; archives keep long-term history

Verified

Consensus validates every message

Queryable

Retrievable via standard RPC

What Makes This Different from IPFS?

IPFS relies on pinning—someone must actively keep your data available. If the node goes offline, the provider shuts down, or payments stop, your data can disappear. On Obsidian, message ordering and commitments are part of the blockchain itself. Validators verify availability during the serve window, and archive nodes preserve long-term history for RPC retrieval.

04

CRYPTOGRAPHIC
SECURITY

Every message on Obsidian Chain includes multiple layers of cryptographic protection to ensure authenticity, prevent replay attacks, and guarantee message integrity.

ECDSA Signature

Proves sender authenticity. Your private key signs every message, creating unforgeable proof of authorship.

Chain ID

Prevents cross-chain replay attacks. Messages are bound to Obsidian Chain and cannot be replayed on other networks.

Nonce

Prevents same-chain replay attacks. Each message has a unique nonce that can only be used once per sender per block.

Target Block

Controls intended inclusion window. Messages specify their target block for predictable timing.

All cryptographic checks are verified at multiple layers: RPC → P2P Gossip → Block Build → Consensus

05

PLATFORM
COMPARISON

PlatformDeletable?Editable?Survives Shutdown?Feeless Tier?
Twitter/XYesYesNoYes
Ethereum (calldata)NoNoYesNo (gas)
IPFSIf unpinnedNoMaybeDepends
Obsidian ChainNoNoYesYes (SM)

Obsidian works alongside Arweave—use Arweave for large historical file archives, Obsidian for EVM-native messaging with feeless and priority tiers.

Your Messages. Finalized.

Join the first blockchain built for archive-backed communication.