You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: applications/fundation.md
+73-2Lines changed: 73 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,22 @@ The primary goal of Fundation is to simplify dApp development on top of Asset Hu
20
20
**Team's Motivation:**
21
21
While building my first dApp on Polkadot, Stake2Build, over a year and a half ago, I realized how far behind the ecosystem was in front-end and web developer tooling. Although many improvements have been made since then, I believe this tool will still be of great benefit to the community by addressing these ongoing challenges, lowering entry barriers for indie devs, hackathon teams, and startups.
22
22
23
+
24
+
- What your project is *not* or will *not* provide or implement
25
+
This funding covers the base module only. It provides fast full‑stack dApp scaffolding limited to:
- Blockchain connectivity and chain management via polkadot‑api
29
+
- Reusable UI components and utilities to accelerate dApp development
30
+
31
+
What this does NOT include:
32
+
33
+
- Prebuilt showcase dApps, full application templates, or production end‑user apps
34
+
- Application‑specific components, custom integrations, or business logic required to implement particular dApps
35
+
- Hosting, third‑party paid services, or deployment/maintenance of end‑user applications
36
+
37
+
In short: the deliverable is a developer‑focused toolkit to jumpstart dApp development. Teams will still need to build, adapt, and deploy their own complete applications on top of the base module; additional funding would be needed to deliver full showcase apps or bespoke integrations.
38
+
23
39
### Project Details
24
40
25
41
**Technology Stack:**
@@ -72,6 +88,20 @@ Experience gained from building the dApp Stake2Build and leading the BuildOnDot
If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying.: no code to show
98
+
99
+
- links to improvement proposals or [RFPs](https://grants.web3.foundation/docs/rfps) (requests for proposal),
100
+
- academic publications relevant to the problem,
101
+
- links to your research diary, blog posts, articles, forum discussions or open GitHub issues,
102
+
- references to conversations you might have had related to this project with anyone from the Web3 Foundation,
103
+
- previous interface iterations, such as mock-ups and wireframes.
104
+
75
105
## Development Roadmap :nut_and_bolt:
76
106
77
107
### Overview
@@ -99,7 +129,7 @@ Experience gained from building the dApp Stake2Build and leading the BuildOnDot
@@ -126,4 +156,45 @@ Sustainability will be sought through optional donations and partnerships with P
126
156
Release v1.0 and promote via the **BuildOnDot** community. Enhance based on early user feedback, adding more modules for DeFi and governance.
127
157
128
158
**Team's long-term plans:**
129
-
My long-term vision is to accelerate Polkadot adoption by enabling the rapid creation of high-quality dApps. I aim to develop a comprehensive suite of tools and products that empower developers, lower technical barriers, and foster a thriving ecosystem—ultimately driving mainstream adoption of Polkadot technology.
159
+
My long-term vision is to accelerate Polkadot adoption by enabling the rapid creation of high-quality dApps. I aim to develop a comprehensive suite of tools and products that empower developers, lower technical barriers, and foster a thriving ecosystem—ultimately driving mainstream adoption of Polkadot technology.
160
+
161
+
162
+
Master Plan
163
+
164
+
## Master Plan
165
+
166
+
### Phase One: Fundation
167
+
Current funding request will establish the foundation framework and core modules.
168
+
169
+
### Phase Two: DAppaggedon
170
+
Development of showcase dApps targeting key Polkadot ecosystem needs:
171
+
- Gaming
172
+
- DeFi
173
+
- Social
174
+
- OpenGov
175
+
These applications will demonstrate Polkadot's capabilities and potential.
176
+
177
+
### Phase Three: Clone Wars & Case Studies
178
+
- Create Web3 versions of popular Web2 applications
179
+
- Document migration challenges and solutions
180
+
- Develop detailed case studies for enterprise adoption
181
+
- Focus on e-commerce migration to Web3 architecture
182
+
183
+
### Phase Four — Omnipass Lightwallet
184
+
- Embedded light wallet delivered as an NPM package.
185
+
- Intended for single relying-party use: the wallet instance is created and usable only on the site/app where it was instantiated.
186
+
- Goals: easy integration, minimal footprint, secure local key storage, and fast onboarding for dApp developers.
187
+
188
+
### Phase Five — Omnipass Browser Extension & Mobile App
189
+
- Browser extension wallet
190
+
- Cross-site passkey use: allows a single passkey to authenticate across multiple dApps without creating a new light wallet for each site.
191
+
- Standard extension features: secure key storage, permissioned site access, connect/disconnect flows, and background sync.
192
+
- Mobile app
193
+
- Mirrors extension functionality on mobile: stores the wallet, provides deep links/universal links for in-browser flows, and supports mobile-to-dapp communication.
194
+
- Use cases: mobile-first dApps, seamless auth between mobile browser and native app, and push/QR flows for transaction approval.
195
+
196
+
### Phase Six — Omni Protocol
197
+
- Omni ID: a wallet naming protocol for human-readable addresses (e.g., swen@dot).
198
+
- Features: name resolution, chain-aware addressing, lookup/fallback to raw addresses, and a registry model (on-chain or decentralized) to map names to account identifiers.
199
+
- Goals: simplify fund transfers and UX by enabling username+chain transfers while preserving security and ownership controls.
200
+
- Considerations: name collision handling, ownership verification, and privacy/resolution performance.
0 commit comments