When you send a message on Obsidian Chain, it does not go to a server that might shut down. It does not get stored on a service that might cancel your account. Your message becomes an immutable part of the blockchain's history.
Cryptographic proof of authorship that cannot be forged or falsely attributed.
Validators commit your message to canonical chain history through the lane-header path.
Casper FFG makes ordering irreversible, while archive nodes keep message data retrievable over time.
Cannot be edited after inclusion.
No admin can remove it.
Lane committees attest availability; archives keep long-term history.
Consensus validates every message.
Retrievable via standard RPC.
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.
Every message on Obsidian Chain includes multiple layers of cryptographic protection to ensure authenticity, prevent replay attacks, and guarantee message integrity.
Proves sender authenticity. Your private key signs every message, creating unforgeable proof of authorship.
Prevents cross-chain replay attacks. Messages are bound to Obsidian Chain and cannot be replayed on other networks.
Prevents same-chain replay attacks. Each message has a unique nonce that can only be used once per sender per 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
| Platform | Deletable | Editable | Survives shutdown | Feeless tier |
|---|---|---|---|---|
| Twitter / X | Yes | Yes | No | Yes |
| Ethereum (calldata) | No | No | Yes | No (gas) |
| IPFS | If unpinned | No | Maybe | Depends |
| Obsidian Chain | No | No | Yes | Yes (SM) |
Obsidian works alongside Arweave. Use Arweave for large historical file archives, Obsidian for EVM-native messaging with feeless and priority tiers.
Build on a chain designed from day one for archive-backed communication.
