VOOZH about

URL: https://blog.logrocket.com/p2p-protocol-acceptance-state-modern-browsers/

⇱ The state of P2P protocol acceptance in modern browsers - LogRocket Blog


2021-11-30
1201
#web3
Alex Merced
80187
👁 Image

See how LogRocket's Galileo AI surfaces the most severe issues for you

No signup required

Check it out

Web 3.0 is an umbrella term for technologies in the webspace that offer decentralized applications and don’t rely on central servers, improving user autonomy and privacy. While many developers focus on Web 3.0 applications that use distributed ledgers called blockchains to manage data, other applications use methods like torrents or browser storage to offer decentralization.

👁 State p2p Acceptance Modern Browsers

In this article, we’ll review some of the different technologies in this space, discussing their current state and future plans. Let’s get started!

Popular web protocols

Onion Router

Onion Routing is the key technology of the Onion Router (TOR), created in 2002. TOR
disguises the source of internet traffic through layers of servers and encryption.

With the TOR Browser, you can create .Onion domain names that provide your website with source anonymity in what many refer to as the deep web. The deep web contains sites only accessible through the onion protocol on the TOR browser.

TOR and the Brave browser both support the Onion Protocol. The makers of TOR have also created a browser for iOS called the Onion Browser.

Gemini

The Gemini Protocol, created in 2019, is an internet protocol that aims to fall somewhere in between the Gopher Protocol and HTTP. Gemini offers improvements like domain-based virtual hosting, redirects to prevent broken links, and identification of binary content using MIME types.

Gemini distributes sites using a lightweight markup language called gemtext, which removes many of the advanced media features of HTML, keeping pages small so they load quickly. gemtext looks a lot like markdown, so a heading with a bulleted list would use the following structure:

# This is my Heading
* item
* item
* item

Generally, pages are text based with some color changing, meaning content loads quickly and is responsive to the viewport. To add external media, you can simply use links. If content moves to another location, you can easily create redirects.

You can access a list of Gemini clients on the homepage. At the time of writing, there is no major browser support for Gemini, but there are traditional HTTP sites that can act as a proxy to access Gemini content from any modern browser, like Mozz.

IPFS

The Interplanetary File System, or IPFS, is an internet protocol created in 2015 that aims to decentralize the location of content on the web. Instead of hosting content on a static server, content is distributed via peers who seed content in a way similar to torrents.

As long as one IPFS node has its content under a particular IPFS content ID, the content will remain accessible. Content is immutable, so any updates will result in a new content ID. At the time of writing, the Brave and Opera browsers both have native support for IPFS, and you can download extensions to add IPFS support to Chrome and Firefox. Additionally, databases like OrbitDB and AvionDB are built on top of IPFS.

Blockchain-based protocols

Stacks

Stacks is a blockchain-based protocol that settles transactions through Bitcoin transactions on the blockstack network. Apps built on the blockstack network can’t be taken down. Additionally, data is controlled by the user and is portable between apps. App builders can also issue their own tokens with the security of the Bitcoin network.

A popular example of a Stacks app is the blogging application Sigle. First, you’d get a secret key from the Stacks network, then you can log in to Sigle or other apps using the key. Data will be bound to the key instead of the app.

You can build the frontend of these apps with standard HTTP websites, so you don’t need any unique browser. The application itself handles creating and fetching the data. The data on the network is deployed to the blockchain, then paired with a standard web interface.

At the time of writing, another blockchain network Algorand is working with Stacks to develop the Clarity language, which is used to build apps on Stacks.

BigchainDB

BigchainDB is a database that any web, desktop, or mobile application can use to distribute data over the Bigchain network. Data on BigchainDB is organized into assets that can either be created or transformed, instead of records or collections.

Assets are especially useful for applications aiming to create records of ownership. Imagine you create an asset for buying and selling goods between users. When a user registers a good they would like to sell, they’d first CREATE that asset on the Bigchain network that they own. When the user sells the asset, the application would create a TRANSFER transaction to transfer the asset to a different user or address on the chain.

The application that creates the data doesn’t own the data, but instead, it is distributed over the blockchain, preserving the integrity of the users’ assets. These assets work in the database you’d use in your application, so you don’t need any special browser. The user interface for the app would be your standard web, desktop, or mobile application.

Other decentralized technologies

ActivityPub

ActivityPub is a specification for creating application servers that can talk to each other and create federated applications. An application that implements the ActivityPub specification can talk to other applications that implement the specification. One example of this is the microblogging network, Mastodon.

When you sign up as a Mastodon user, you sign up on one of the many independently run Mastodon servers available. Although each server is independently run and follows its own rules, you can follow users on other servers as long as the server you’re on allows you to federate with that server. A server can block federating or communicating with certain servers.

ActivityPub’s server specification protects your privacy. For example, if you want to own your information, you can start your own individual server and interact with the greater network.

On other networks, you must either follow the rules or lose all access to the network, however, on ActivityPub, there is no all-or-nothing gatekeeping in this sense. Because each server is independently run, you’re sure to find a server that allows or restricts your desired specifications.


Over 200k developers use LogRocket to create better digital experiences

👁 Image
Learn more →

GUNDB

GUNDB is a database that truly gives a user ownership of their data. The GUN database stores information on a user’s computer through the localStorage API. For example, imagine a social network or chat app that makes your data inaccessible when you log out, prioritizing your privacy even when you’re not logged in.

The localStorage API really opens the door to giving users greater control over privacy and scalability.  Every user holds their own data, and data is passed via WebRTC. For example, think of how Zoom and other video calling apps pass data directly between users, providing great speed for viewing data.

Conclusion

With so many protocols available for decentralizing the web and protecting privacy and autonomy, it can be difficult to keep track of them all. In this tutorial, we covered a few of the most popular Web 3.0 protocols, looking specifically at protocols that use a blockchain-based approach.

If you’re looking for a good resource to keep track of all these technologies, be sure to check out the following GitHub Gist. Also, if you want to connect, be sure to follow me on Mastodon. Thanks for reading and happy coding!

Join organizations like Bitso and Coinsquare that use LogRocket to proactively monitor their Web3 apps

Client-side issues that impact users’ ability to activate and transact in your apps can drastically affect your bottom line. If you’re interested in monitoring UX issues, automatically surfacing JavaScript errors, and tracking slow network requests and component load time, try LogRocket.

👁 LogRocket Dashboard Free Trial Banner

LogRocket lets you replay user sessions, eliminating guesswork around why bugs happen by showing exactly what users experienced. It captures console logs, errors, network requests, and pixel-perfect DOM recordings — compatible with all frameworks.

LogRocket's Galileo AI watches sessions for you, instantly identifying and explaining user struggles with automated monitoring of your entire product experience.

Modernize how you debug web and mobile apps — start monitoring for free.

👁 Image
👁 Image
👁 Image

Stop guessing about your digital experience with LogRocket

Get started for free

Recent posts:

I let React Compiler handle memoization: Here’s what actually broke

Enabled React Compiler v1.0 on a production Next.js app. Here’s every warning, breakage, and silent opt-out I documented — and what actually worked.

👁 Image
Isaac Okoro
Jun 29, 2026 ⋅ 7 min read

TanStack Start RSC vs. Next.js RSC: Performance, DX, and production readiness

We built the same app in TanStack Start RSC and Next.js RSC. TanStack shipped 40% less JS and built 4x faster — but Next.js is still the safer production bet.

👁 Image
Chizaram Ken
Jun 25, 2026 ⋅ 7 min read

Frontend Wrapped H1 2026: The nine biggest storylines so far

From RSC vulnerabilities and the Vercel breach to TypeScript 7.0 Beta and AI agents — the nine frontend storylines that defined H1 2026, ranked.

👁 Image
Chizaram Ken
Jun 23, 2026 ⋅ 9 min read

I shipped AI-generated React code: 4 bugs I fixed

AI tools generate working React code fast, but miss race conditions, empty states, debouncing, and accessibility. Here’s how to catch bugs before production.

👁 Image
Temitope Oyedele
Jun 22, 2026 ⋅ 10 min read
View all posts

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now