DID, IPFS, Arweave: Web3 That Doesn't Talk About Price

When you hear "Web3," what comes to mind?

Bitcoin price? NFT jpegs? Rug pulls?

I used to think the same. Until I realized: the most useful parts of Web3 have nothing to do with price.

This is about three technologies I actually use in production - not for trading, but for solving real problems.

---

DID: Identity You Own, Not Borrow

Right now, your internet "identity" belongs to Google, Facebook, or Apple. You "login with Google" - but Google can revoke your access anytime. You own nothing.

DID (Decentralized Identifier) gives ownership back to you.

It works simply:

1. You generate a key pair (public + private) - that's your identity
2. You publish a DID document to a blockchain or decentralized network
3. Every time you log in, you sign a challenge with your private key
4. The service verifies the signature with your public key - no Google needed

Example DID Document
{
"id": "did:example:123abc",
"publicKey": [
{
"id": "did:example:123abc#keys-1",
"type": "EcdsaSecp256k1VerificationKey2019",
"publicKeyHex": "04b12c8..."
}
],
"service": [
{
"type": "LinkedDomains",
"serviceEndpoint": "https://msncode.dev"
}
]
}

I use DID to sign articles on this blog. Every article is signed - readers can verify that I actually wrote it, not an impersonator.

No Google. No passwords. No KYC.

---

IPFS: Files That Can't Be Taken Down

You upload an image to your server. Tomorrow, your server goes down. Image gone.

You upload to Imgur. Tomorrow, Imgur changes their ToS. Image gone.

You upload to IPFS. Tomorrow - and 10 years from now - the image is still there.

IPFS (InterPlanetary File System) isn't a server. It's a P2P network where files are accessed by their *content*, not their *location*.

HTTP: https://server.com/image.jpg → "get file from this server"
IPFS: ipfs://QmX4eT4e... → "get file with this hash"

The difference: if the server dies, HTTP breaks. But IPFS - as long as one node in the world has the file with that hash, the file is accessible.

I use IPFS for article backups. If the main server goes down, readers can access the same content through any IPFS gateway.

The killer combo: IPFS + Blockchain = permanent content addressing. Store the IPFS hash on a blockchain - that hash can't be changed. As long as the blockchain exists, the hash is valid.

---

Arweave: Pay Once, Store Forever

IPFS needs hosting - either you run your own node or use a pinning service (Filebase, Pinata, etc.). If you stop paying, the file disappears.

Arweave is different. You pay once - up front - and your data stays as long as the Arweave network exists. Estimated: 200+ years.

Arweave's model: you pay storage costs upfront, the money goes into an endowment fund. The fund's interest covers storage costs forever.

Arweave vs IPFS vs Regular Server
Regular server: pay monthly, data gone if you stop paying
IPFS: free (but needs pinning service ~$5/month)
Arweave: pay once (~$5-50 depending on size), data forever

I use Arweave to store important article metadata - author signatures, timestamps, content hashes. If this blog disappears tomorrow, that data can still be verified on Arweave.

---

Why This Matters for Developers

Financial Web3 (trading, DeFi, NFTs) gets attention because there's money involved. But non-financial Web3 is what actually changes how we build:

1. DID → build login systems without a user database - no passwords to handle, no data breach worries
2. IPFS → distribution without servers - just generate a hash, the network handles the rest
3. Arweave → permanent storage for audit logs, certificates, legal documents - nobody can delete them

These aren't future technologies. They're tools you can use today - through simple APIs.

---

Where to Start

DID - use did-jwt (Node.js)
npm install did-jwt

IPFS - use ipfs-http-client
npm install ipfs-http-client

Arweave - use arweave SDK
npm install arweave

Each SDK takes 3-4 lines of code to get started. No blockchain expertise required.

*Think about it: what feature in your app could benefit from decentralized identity or permanent storage? Start small - like signing API responses with a DID, or backing up critical data to Arweave. You don't need to migrate everything. Just one feature.*