Impervious releases fully decentralized browser

Impervious will release its fully decentralized browser publicly on April 7 during Bitcoin Week 2022, the platform tweeted. It’s billed as “google without google, zoom without zoom, and identity without the state.”

Impervious API is a programmatic layer that sits on top of the Bitcoin Lightning Network, i.e. “Layer 3.” Developers can leverage the Impervious API to easily build secure p2p data transmissions and payments into their applications and services.

Features and functions

Are you looking for fast-news, hot-tips and market analysis?

Sign-up for the Invezz newsletter, today.

Among the browser’s features and functions are:

• Truly peer-to-peer
• Default encryption
• Censorship and surveillance resistance
• Inbuilt payments

A panacea for privacy

Circumventing digital intermediaries and establishing p2p data transmissions is a panacea for consumer privacy, data security, censorship resistance, and countering surveillance.

The goal of the Impervious Node is to enable developers to easily build robust applications which take advantage of the Lightning Network, without having to learn or worry about the deep technicals of Lighting payment systems.

Impervious Nodes are a framework for developers to create their own networks, applications, APIs and other creative architectural structures.

About Impervious architecture

• At layer one, there exists the Bitcoin network – money, deep storage, global root trust.
• At layer two, there exists the Lightning Network – cash, fluid payments, peer to peer trust.
• At layer three, there exists the Impervious Network – applications, streaming micro payments, and node federation.

The Impervious Node offers three web developer friendly interfaces for communications.

• GRPC input
• HTTP RESTful input
• HTTP Websocket output

Both GRPC/REST interfaces provide an input and a message ID on the response. This message ID allows for a developer to track and coordinate message synchronization.

The websocket output is a stream of messages, with the above message ID, or a far end message ID. The websocket is used for asynchronous/random reception of messages. For some API endpoints, the response is via the websocket because there could be a long wait state for the Lightning Network to forward the messages.

In the Impervious design, these GRPC/REST interfaces generate a message ID, fire off the message into the Lightning Network, and then immediately respond to the developer with the message ID. The developer then monitors the websocket for that message ID to return.