TEA Hosting Nodes: “Dynamic” IPFS Gateways

TApps Are Fundamentally IPFS CIDs

In the TEA Project, the TAppStore stores a registry of all TApps running on the network via their content IDs (CIDs). For a refresher on how the end-user finds the location of the TAppStore to load in their browser, the details can be found in the following article:

Static IPFS Gateways vs Dynamic TEA Hosting Nodes

IPFS provides gateways to CIDs through URLs that are structured like

TEA Project TApps Are Truly Dynamic DApps

The front end of a TApp is actually loaded inside the user’s browser from an IPFS CID. If it’s a front-end to a dynamic TApp, it’ll start utilizing hosting nodes in order to execute the functions to process the dynamic content. This layer that processes the business logic is usually called the backend in traditional cloud computing.

TEA Project’s Decentralized Serverless Backend

In current smart contract-based dApps, the lambda layer is missing. That’s exactly the role that hosting nodes in the TEA Project play.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store