UIs encompass all on-screen controls that support user interactions. As a framework, Substrate comes with an array of UI tools that facilitate designing for a wide range of users’ needs. Let’s examine some of them.
APIs are light-weight software that run between applications and are designed to help them consume data. In this article, we consider how Substrate-based APIs establish a robust programming layer for DApps that persists on top of recurring runtime upgrades.
Pallets operate as building blocks within the Substrate Framework: they determine the kind of DApps that can be built and deployed on a Substrate blockchain. In this article, we consider how Pallets are used to generate back-end services for a wide range of DApps.
DApps are programmes that run on blockchains but often underperform due to limited on-chain resources. Substrate establishes new models to enhance DApps functionalities and execution within a multi-chain ecosystem.
In this article, we explore how Substrate uses the FRAME framework to facilitate blockchain development.
This post presents some essential front-end components that are used to interact with a Substrate blockchain node.
In this article, we look into the back-end operations needed to configure a Substrate blockchain node.
Substrate is a framework for developing blockchain-based automated protocols within a modular environment. However, as cutting-edge as this might sound, Substrate doesn’t operate out of the box or in isolation. Let’s examine the Substrate environment from a web 2.0 developer’s perspective.
From the Web 1.0 of the 90s to the Web 2.0 of the 2010s, users and developers alike seem to be in a perpetual race to catch up with digital technologies that forever elude them. But this doesn’t have to be the case. This series of articles gives an overview of Web 3.0 development with the Substrate Framework for Polkadot and Kusama.
Consensus, Governance and Voting are at the heart of processes that affect people beyond everyday operations and policies. But this illusion of equality only exists in principles and protocols, never in practice. Let’s have a go at mapping the requirements of a trustless Web 3.0.