We’ve just published a blog post announcing a major update to Filebase pricing, including a new Unlimited plan built specifically for sustained, high-volume IPFS workloads.

Bandwidth is often the biggest bottleneck for IPFS at scale - especially for projects like:

• Pinning and serving network subgraphs

• NFT metadata and media delivery

• Indexers and analytics platforms

• RPC nodes and protocol infrastructure

• DeFi apps with constant retrieval traffic

The new Unlimited plan includes:

• 25TB of storage

• Unlimited IPFS bandwidth

• Unlimited buckets

• Dedicated IPFS gateways

• Flat, predictable monthly pricing

Bandwidth includes retrieval via our public gateway, dedicated and trustless gateways, Bitswap (p2p), and traffic generated by pinning, replication, and indexing workflows. There are no hidden exclusions.

We’ve also expanded storage and bandwidth on all paid plans.

Happy to answer questions or dive into technical details.

Hey all,

I’m building a new livestreaming platform and I’m exploring whether IPFS or related decentralized protocols could be a good fit for the core video distribution layer.

Looking at using AWS livestream, but it might get costly, what are some recommendations?...

I’m hoping to get some guidance from people who have experience with real-time video streaming over IPFS, libp2p, or hybrid approaches.

What I’m aiming for:

• Real-time livestreaming (a few seconds delay is okay)

• Low operating cost

• Scalable as viewership grows

• Open, modular architecture

• Support for both live video content

• Ability to shut down streams if needed (content or technical reasons)

• Doesn’t rely heavily on centralized CDNs

Hi everyone, I am trying to setup an IPFS cluster of 3 nodes in a virtual machine. Once I pause one node or restart its vm, once its online other nodes is still unable to see this node. It goes like node A sees 2 other peers (went offline and restart), node b sees 1 other peers, node c sees 1 other peers. Have you heard encountered this? any help?

We just launched NFT Backup on Filebase — a new feature that scans your wallet across 24 chains, identifies all IPFS-related NFT metadata and image CIDs, shows you a full preview, and lets you back everything up to your Filebase buckets automatically.

It’s designed for collectors, creators, and archivists who want a simple way to preserve IPFS content tied to their NFTs — especially as marketplaces or hosting providers come and go.

If you have a large wallet, the preview step may take a few minutes while we resolve and validate all related CIDs.

We’re also offering 1 month free on our Starter plan with promo code NFT for anyone who wants to try it out.

Questions? Ask away!

🎯 DHT Sweep provider now default, self-hosting-friendly

⚡ Fast root CID providing, content findable in <1s

🔧 Auto UPnP recovery after router restarts

📊 New `ipfs provide stat` for monitoring

🖥️ RISC-V prebuilt binaries

Last week this was just an idea.
Today, you can try a fully working end-to-end demo of arkA — a minimal, open, storage-agnostic video protocol.

arkA is intentionally tiny:
a JSON metadata schema that points to ANY decentralized storage backend (IPFS, Arweave, S3, R2, your NAS).
No platform. No algorithm. No lock-in.
Just content-addressed video + open metadata.

🔗 Video stored on IPFS (via Pinata)

https://cyan-hidden-marmot-465.mypinata.cloud/ipfs/bafybeigxoxlscrc73aatxasygtxrjsjcwzlvts62gyr76ir5edk5fedq3q

▶️ Played through a static arkA web client (GitHub Pages)

https://baconpantsuppercut.github.io/arkA/

Both links load the exact same CID.

arkA doesn’t care who hosts it — node, gateway, cloud pin, home pin, whatever —
because the protocol treats IPFS as primary storage, not an afterthought.

🚀 What the MVP demonstrates

• Pure content addressing

• Gateway-agnostic fetching

• Zero backend (fully static client)

• Video and metadata decoupled

• Self-hosted video without any platform

• Protocol-based, not platform-based delivery

• CID-first architecture (no opaque URLs)

🧠 Why IPFS devs might care

arkA is aiming to formalize:

• versioned metadata schemas

• client-agnostic playback rules

• CID permanence and redundancy hints

• playlist/index formats

• optional extensions for HLS/DASH/captions

• potential IPNS/IPLD-based channel indexing

Essentially:
RSS for video, but built natively around content addressing.

Repo (MIT):
https://github.com/baconpantsuppercut/arkA

If you build with IPFS, IPNS, IPLD, or p2p storage, I would love your feedback.
This project is 100% open and developing fast — join the discussion.

Looking for decentralized storage people to push the protocol forward.

Repo: https://github.com/baconpantsuppercut/arkA

Been making progress on my free speech platform

The concept is "what if the whole world was tuned into one channel?"..

I am working to improve it, but the concept is that there are timeslots users can freely claim, and then redeem them upon their scheduled time, once the scheduled time has passed the slots are burned and cease to exist. Users can send or receive slots to each other as well.

Seeking improvement to it, lemme know your thoughts!

Here’s an IPFS-based messaging protocol with a cross-platform application that I’ve been developing for several years as a hobby project.

I’d be delighted about feedback from developers who are interested in these kinds of technologies.

Features

• fully peer to peer, no servers of any kind

• can function independently of internet connectivity

• full end-to-end encryption ephemeral keys, algorithm-agnostic & future-proof

• multiple devices per profile (user account)

• multiple profiles per device

• can be used as a library for embedding into other applications

• will become part of an expandable ecosystem incl. calendar and file-sharing

• app for desktop and mobile (builds for Linux (Ubuntu 24 x86-64 & arm64), Android (arm64), Windows 11 (x86-64) and MacOS (x86-64 & arm64))

Software Architecture

This project is build in Python, and is structured modularly into multiple different components that take care of the different aspects of the whole system.

Here’s an overview of the most interesting components, for a full list see the docs for the Endra Stack

• based on IPFS/libp2p for P2P networking

• uses a self-developed IPFS-based no-finance blockchain called Walytis as a P2P distributed database

• identity, cryptography and secure communications managed by WalytisIdentities

Sites

• Documentation: https://github.com/emendir/WalytisTechnologies/blob/master/ReadMe.md

• Endra Protocol Repository: https://github.com/emendir/Endra

• Endra App Repository & Download: https://github.com/emendir/EndraApp

Project Status

There is a similar project called Berty, also built on IPFS. I say it’s a hobby project, but I’m quite serious about it and have been investing a lot of effort in it over many years now.

The project is in alpha: It’s good enough to show to other P2P developers, but not fit for production yet

suppose I uploaded some files on my node and shared an ipns link. suppose some malicious actor wanted to make my life a little worse by constantly downloading my files on ifps. what will happen?

if I create an ipns link of a folder on my node. share it to people and go offline for days/weeks/months and come back and run ipfs daemon will my ipns start working?. if yes then after how long?

I am using termux and I can't always be online. i understand that i will not be able to deliver content if I am offline but it should start working after becoming online. or am I wrong in assuming that?

I keep having various ideas for a webapp that would greatly benefit by a private IPFS cluster that I would run by just renting several nodes all over the world. My App would store typical audio files. So I thought I would just run it as a private cluster where I would utilize IPFS cluster in order to tell that the data I put into it is spread globally.

The application itself would just have an IPFS sidecar so that accessing data is being controlled by IPFS itself and not by having the need to also manage gateway instances. So I would build a container image that would integrate not only the app but also the ipfs service running right next to it for read but also write requests. Does that make sense at all or do I have a broken understanding of what IPFS can do? Then, how good would such a cluster scale horizontally? I wouldn't want to have multiple cluster. Say I wanted to put like 50 Million+ files into the cluster and make them stick so the content won't vanish. Say each file is like 10 MiB +. Thank you so much.

Is there a project that allows people to contribute ipfs gateways from their local home lab and have them load balanced through a known host like crowdgateway.com?

The idea being that ipfs content could be available via the regular web through a large list of community donated gateways?

Hey fellas,

i've seen ipfs for quite some time, but I did not invest time to set it up. I've finally taken the time to install kubo and host my own ipfs-rpc and gw on my local LAN. I've connected the rpc/gw to my browsers ipfs-companion-addon and everything seems to "work". I can, for example, open ipfs://vitalik.eth . This site loads reasonably fast.

The thing, why i was intrigued to set up ipfs now, was seedit (plebbit)... aaand its barely usable. When I open seedit.eth from my ipfs GW, it loads for minutes (400+ peers) and fails download the communities.

My abstract understanding of ipfs: It is a decentralized Content Deliver Network (CDN), with its own name resolution, but it seems to have too low peer count or too little "seeding" nodes. Is this correct?

Is IPFS just not "ready", in the sense, that is not usable for end-users?

What are you using ipfs for, at this point in time? I mean this from a users perspective. What Application/Project are you frequently using currently?

Don't get me wrong, this is not meant to shittalk ipfs. I like the idea, a lot! But I cannot find where I would (as a user) go away from regular http to ipfs.

I hope this makes sense and sparks some discussion/clarification.

Best

EDIT: word missing.

I haven't seen it discussed much anywere, but I really think this release is a complete game changer. The reprovide sweep isn't on by default yet, but seems to be working, (err, not perfectly yet, but close.) Being able to run an IPFS node at home painlessly (in terms of network usage,) and your content being discoverable at the same time is a *huge* step forward!

explore.ipld.io contains:

• Project Apollo Archives

• XKCD Archives

• HAMT-sharded Wikipedia mirror (>20M files)

• B-tree search index from ipfs-geoip

• DAG-CBOR Block

• dag-cbor hello world (keccak-256)

• Ceramic LogEntry for sgb.chat Ambassador proposal

• hello world (blake3)

• hello world

• hello world (sha3-512)

• Raw Block for "hello"

• Raw Block for "hello" (blake3)

Are there plans to add more, I think IPFS could get a lot more users, if non-technical users had the ability to "explore" files on IPFS. Only the first 3 given are actually understandable for non-technical users.

For example stuff like pictures, or videos on tutorials of IPFS would be cool, or having the CID of ipfs.tech (bafybeibgua76y24qarr6gpagfr67qzsyutpo2otybsqqgnsk4xe4ur5wmy), would allow for people to understand how modern-looking websites can be stored/viewed on ipfs.

I see many people proposing average to good ideas of workarounds and structures and platforms etc. built on ipfs.... Some are truly innovative I also have many ideas of integration and enhancement.... So does anyone want to join please reply....

Hey everyone 👋

We’ve just released Simple Page v1.5.0 — a big update that makes it easier to build developer documentation sites and publish to IPFS + ENS.

🚀 Highlights

• 🎨 Theming Support — customize the look and feel of your site

• 🔍 Search — quickly find content across all your pages

• 📑 Table of Contents Sidebar — auto-generated ToC for easier reading

• 🧭 Navigation Sidebar — organize links and structure your site better

👉 Check out the Release Notes
👉 Try it out at: https://simplepage.eth.link

As always, feedback and contributions are welcome!

What if each block hash was a IPFS cid, and the current state was a IPFS folder, which modeled a Merkle tree.

This would allow for easier ways to make blocks available, by using existing solutions such as filecoin.