Permanent On-Chain Data

True Immutability

When you send a message on Obsidian, it becomes part of the blockchain itself. Not stored in a database. Not pinned to IPFS. Not held by a service provider. In the chain.

Your message → Block 12345 → Every node → Forever

What "Permanent" Actually Means

Obsidian identifies two types of finality:

Finality Type	Guarantee
Inclusion Finality	The lane header is in a finalized block. Message ordering is permanent.
Availability Finality	The availability certificate proves data was retrievable at inclusion time.

Properties

Property	Guarantee
Immutable	Cannot be edited after inclusion
Undeletable	No admin can remove it
Replicated	Copied across validators and archives
Verified	Consensus validates every message
Queryable	Retrievable via standard RPC

Comparison

Platform	Deletable?	Editable?	Survives Company Death?
Twitter/X	Yes	Yes	No
Facebook	Yes	Yes	No
AWS S3	Yes	Yes	No
IPFS	If unpinned	No	Maybe
Obsidian	No	No	Yes

Arweave Integration: Obsidian works alongside Arweave rather than competing with it. Use Arweave for large permanent file storage (images, videos, documents), then reference those Arweave URLs in Obsidian messages. This gives you the best of both: Arweave's cost-effective large file permanence plus Obsidian's EVM-native messaging with smart contract integration and free/priority tiers.

How It Works

1. Signed by you: Cryptographic proof of authorship

2. Included in block: Validator commits to message

3. Propagated: All nodes receive the block

4. Finalized: Casper FFG makes it irreversible

5. Stored forever: Part of canonical chain history

Use Cases

• Whistleblowing: Publish evidence that can't be suppressed

• Legal records: Timestamped, immutable documents

• Social permanence: Posts that outlive platforms

• Attestations: Proofs that can't be revoked

Your data. Your signature. Forever.