The goal of this page is to provide an overview of the open-source Polkadot/Kusama Tech Stack.
This is a living document and we are relying on our community to contribute to it and help maintain it. Please feel free to make edits and additions via pull requests. We apologize if we missed your project!
The Polkadot Tech Stack is a subset of the Web 3.0 Tech Stack, which consists of the open-source technologies contributing to and relying on Polkadot, Kusama and Substrate. It is meant to be used for decentralized application (Dapp) development within numerous verticals including DeFi, Gaming, Provenance and many others not pictured below.
|------|--------|------------|
| DeFi | Gaming | Provenance |
|______|________|____________|
Dapps
|--------------------------/-|
| Explorers, Wallets / |
|------------------------/---|
| Tools, Apis, Languages/ |
|----------------------/-----|
| 2nd layer protocols / |
|--------------------/-------|
| Chains / other |
|------------------/--- --|
| *Polkadot* | tech |
|------------------\---------|
| P2P, Crypto, Wasm \ |
|--------------------\-------|
The Web3 Foundation's Grants Program is focused on funding development work to build out all layers of the Polkadot Tech Stack.
To get a better understanding of the projects we consider most relevant, you can explore a detailed breakdown of the various layers of the stack below. We divide each of the layers into the various components which we feel are most important. We then highlight some of the exisiting projects that address these components as well as some potentially interesting projects that we would like to fund.
We typically like to fund more than one project for each component. So, if you see a component with 1 or 0 exisiting projects, it's likely that we would consider an application in this area. In order to consider funding a proposal that addresses a component with many existing projects, we would need to be persuaded that yours brings unique value to the ecosystem. Such value could come in many forms including but not limited to differentiated functionality, better user experience, the attraction of new users to the ecosystem or a high likelihood that the technology would be maintained for a long period of time.
By describing our areas of priority in detail, we do not wish to preclude grant applications that address different areas that we may not have thought of. We would like to fund all projects that bring value to the ecosystem. If you are considering applying for a project and are not sure if it falls within our areas of interest, please get in touch with us to discuss it.
In the below sections you can find a list of different layers of the Polkadot Stack.
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| Desktop Wallets | AirGap, Sakura | User-friendly Wallet based on the Recovery Pallet, Web wallets focused on user-onboarding (e.g. using localStorage) |
| Browser Extensions | Polkadot{.js}, Doter, Enzyme, Speckle OS | Sign-in with your polkadot, kusama, etc. account. |
| Mobile Wallets | Lunie, Polkawallet, Parity Signer, imToken, Fearless Wallet Android, Fearless Wallet iOS, Stylo | |
| Burner Wallets/Faucet | KodaDot | Faucet (a sybil-resistant way to receive free tokens) |
| CLI Wallet | Subwallet, Proxy-hot-wallet | |
| Multisignature Wallets | Subscan Multisig UI - React, Subscan Multisig UI | |
| Hardware Wallets | Ledger Polkadot, Ledger Kusama, NGRAVE | Trezor |
| Block Explorers | Polkascan, Polkastats, Subscan | Mempool focused explorer (including parachain transaction) |
| Validator Dashboards | Polkacube, YieldScan, Hubble | |
| Node Explorers | Polkadot Node Explorer | |
| NFT Explorer | NFT Explorer for Kusama & Polkadot | |
| Governance Dashboards | Polkassembly, dotreasury, Bright Treasury | UI for the kusama and/or polkadot treasury (see bounty module), UI for Parachain Lease Offering (PLO) |
| Staking Rewards | Staking Rewards Collector, Staking Rewards Viewer, Polkadot Staking Site | |
| Bridge UI | Parity Bridges UI, Donut Interface (Steem <> Dot) | |
| Parachain/Crowdloan | Parachains.Network | |
| Other | PolkadotWebIdenticon | Portfolio Viewer like Zapper or Zerion |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| DeFi | Vera, Nsure Insurance, Everlasting Cash, Coinversation, zenlink-dex-contract, AlgoCash | New seigniorage-style stable coins |
| Gaming | NewOmega |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| Rust | Substrate, Cumulus | |
| C++ | Kagome | |
| Go | Gossamer | |
| AssemblyScript |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| Secure validator setup | Trutzone-based HSM, W3F Polkadot Validator Setup | |
| High availability setup | Archipel, Polkadot Failover Mechanism, Open Node Framework | |
| Load Balanced Endpoints | terragrunt-polkadot | |
| Deployment Tools | Polkadot Package Manager, PolkaHub, Avado, Polkadot Deployer | |
| Validator monitoring | P.A.N.I.C., Polkalert, B-Harvest, nmonpolkadot, Polkadot-K8s-Monitor, Polkadot-Watcher | |
| Validator payout management | Substrate validator auto payout, Polkadot Payouts, staking-payouts CLI, Payctl, crunch |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| SR25519 | rust (contains partial bindings for C, JavaScript, and Python), .Net bindings, C (old), C (new), C/C++, C#, Go, java | |
| Distributed key generation (DKG) | keygen.rs | |
| Validator HSMs | ||
| Validator HSM-like solutions |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| PoC | Spartan | |
| PoW | PoW consensus for Substrate, RandomX, Sha3 PoW | |
| Block production | BABE, Aura | |
| Finality | GRANDPA |
| Components | Existing projects | Potentially interesting projects |
|---|---|---|
| DHT crawler | Go, Kotlin |
Pull requests, issues, or other contributions from the community are encouraged! You can not only add specific projects, but also potentially interesting fields/areas which are currently missing in the tech stack.
❗ All technologies listed above need to be open-source. Ideally, the links lead directly to the code.
Note: You will need a GitHub account to suggest changes or open issues. If you do not have one, you may sign up for free.