fundation Build dApps Faster

[swenthebuilder]

Project Abstract

Build dApps Faster Than Ever. Accelerate Your Polkadot Projects with Fundation's Polkadot API Management, Robust Auth, and Modular Toolkit.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (fundation.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

[diogo-w3f]

@swenthebuilder Thanks for the grant application. Could you take a look at our new grant guidelines [here] and help us understand how your project fits into them? I feel that your project might be a better fit for the Polkadot Open Source Bounty. Could you please take a look and share your thoughts?

[swenthebuilder]

@diogo-w3f Thanks for the review—I've followed the updated guidelines from day one and still see strong alignment for Fundation.
Polkadot serves devs, users, and businesses. This grant targets small/Web2 devs to fill ecosystem gaps with more dApps, boosting user options, transactions, and DOT demand. It lowers barriers , attracts everyday users via user-friendly apps, and counters the "empty chain" vibe between big launches.
Useful for W3F/Parity quick setups too. As an open-source base layer (showcase at fundation.dev), it's built for community growth post-grant. Fits your Web2-Web3 bridges vertical perfectly—handles auth/components/chain mgmt like Web2 packages.
I've exhausted other paths (fast grant denial, open-source closure, OpenGov redirect) over 5 months. Dev funnels have leaks—happy to chat privately.
User journey: Web2 dev spots Fundation, skips wheel-reinventing, focuses on unique dApp magic → Polkadot wins.

[swenthebuilder]

long version
@diogo-w3f Thank you for reviewing my grant application. I've read the updated guidelines since they were first released by W3F and still believe Fundation fits well within them. To make the case clearer, let's frame it around Polkadot's core users: developers, end users, and businesses. This grant specifically targets small devs—especially those transitioning from Web2—to create a second-order effect. By filling the ecosystem with more dApps, it provides greater options for end users to explore Polkadot, driving transactions and real token usage that benefits the entire network and DOT economy.

Fundation is designed with Web2 developers in mind, making it easier for them to transition into building dApps on Polkadot without the steep learning curve of blockchain specifics. This creates another second-order effect: by empowering these devs to create user-friendly applications, we attract more everyday users to the ecosystem. It's not just about the tech—it's about solving real pain points for devs who want to innovate but are deterred by complexity. By lowering barriers to entry, Fundation encourages more dApps to be built on Polkadot. More dApps mean more users, which in turn drives more transactions and network activity. Right now, attention is skewed toward big projects, creating an "empty chain" feeling during quieter periods. Fundation targets smaller devs to fill those gaps, fostering sustainable growth and hype through consistent, grassroots development rather than relying solely on major releases.

As for use cases, there's no reason this tool wouldn't be useful for W3F or Parity if you need to set up a dApp quickly—but the primary focus will be on onboarding Web2 devs.
this is the starting point, not the destination—like any robust open-source project, its value comes from what gets built on top. It won't be sustainable in isolation, but as a base layer, it enables future projects to thrive. I've already planned a showcase at fundation.dev with example dApps to demonstrate its potential, and I have a clear path to community-driven maintenance post-grant. Fundation fits squarely into one of your exciting verticals: Web2 to Web3 bridges. It brings familiar Web2 experiences (large package ecosystems for auth, components, etc.) directly to Polkadot, allowing devs to focus on their unique ideas rather than reinventing blockchain basics.

I've tried all the other grant options available (fast grant, open-source grant, OpenGov proposal), but unfortunately, they didn't work out due to denials, closures, and redirects. If you'd like to talk about it more, we can discuss in private. I believe Polkadot's dev funnels have some big holes in them that are leaking potential devs.

To wrap up, let's consider the user journey for a Web2 dev: They have a dApp idea and seek the easiest platform. They discover Fundation, which handles Web2-equivalent tasks (auth, components) plus blockchain hassles like chain management. This lets them skip reinventing the wheel and focus on what makes their dApp special—ultimately benefiting Polkadot's ecosystem.

[diogo-w3f]

@swenthebuilder Thanks for the explanation. Here are some requests regarding the format of the application:

• Clarify the USDC payment details (chain/asset/address format).
• Remove any leftover placeholder lines.
• Add measurable acceptance criteria to each milestone.
• Link directly to the code repository for the MVP/demo.
• Standardize naming (e.g., polkadot-api).
• Explain the “DOT % 85%”, are you aware that they are vested?

Additionally, after reading the proposal, the scope still feels a bit vague. Could you provide a concrete example of what a developer would be able to bootstrap with your project, including the architecture, components, etc.? Is it possible to share an example or mockup of what an application might look like after bootstrapping with your project?

I still think your project is a better fit for the Polkadot Open Source Bounty. I noticed your previous application there wasn’t evaluated, You opened it, and then you closed it (see here). If you want, it would it be possible to reopen there.

[swenthebuilder]

Hey @diogo-w3f, I'll fix the proposal soon.

When all is said and done, what you get when you install Foundation is a fully functional, customizable foundation to build a multichain Polkadot dApp.

It acts as a seamless, plug-and-play building block. Think of it like WordPress: providing a core CMS base that users can extend with plug-ins and themes to quickly build any site, store, or community. While these individual steps may seem minor, they address significant challenges for new developers transitioning from Web2. The core goal is not to build the next "big thing," but to enable a multitude of smaller things—if pump.fun made launching a meme coin easy, I want to make building a multichain dApp just as easy.

The architecture deployed will depend on how much or how little you use, but the base stack relies on Next.js and the Polkadot-API. If developers choose to enable features like Passkeys or magic links, they will require a database. I am currently using SQLite for the reference implementation, but any standard database should work.

Yes, I can create some mockups, but they won't visually demonstrate the core value; the point is seamless integration. What I am offering is the reliable connection of separate pieces to create a unified whole.

[swenthebuilder]

Yes, I am well aware of the vesting—I have no problem with it, but thank you for bringing it up. the funding should be 85% DOT and 15% stablecoin.

The goal of this grant is not to function as a typical freelance payment based strictly on completed work, but rather as a reward and incentive metric. The hope is that the more impactful my work is, the more the value of Polkadot increases, which benefits the entire ecosystem. I simply wish to be properly rewarded for contributing to that positive effect.

[swenthebuilder]

Yes, I have no problem going back to the Polkadot Open Source Bounty. My priority is simply to build and contribute, and I am open to whichever mechanism will get me there the fastest.

[diogo-w3f]

@swenthebuilder I think this fits more in the open-source bounty. If you can close this PR here and open a new PR there that would be nice.

Furthermore, please note that the “all-in-one to develop on Polkadot” narrative has several alternatives in the market. Please do the proper research and provide a comparison with existing solutions. Did you have the chance to take a look at LunoKit ? We’re very open to supporting tooling in the ecosystem, but in a way that complements what already exists. So, it’s fundamental to clearly answer the question: What is novel about my proposal for the ecosystem?

[swenthebuilder]

Hey @diogo-w3f,

I’m aware of the LunoKit, as well as Kitdot (the SDK for building Web2-like apps on Polkadot with easy onboarding via social logins). They both made posts on the Polkadot Forum, but I hadn’t seen the LunoKit grant proposal before—that’s new to me. After reading through it, I can definitely see some overlap. I originally thought LunoKit was just a Web3 account connection library, as that’s how they describe themselves on their website. I see they’re doing something with Dedot versus polkadot-api, but I’ll need to look into it deeper to understand the differences.

[swenthebuilder]

Hey @diogo-w3f,

I’ve fully read the LunoKit grant proposal, and at the end of the day, we both share the same goal — we’re just targeting different developers and approaching it slightly differently. My decision to go all-in on polkadot-api instead of dedot, along with my aim to keep dependencies light, sets a different path.

It’s ultimately up to W3F to decide whether there’s room for multiple “all-in-one” solutions for building on Polkadot or if one is sufficient. I’ll admit that the novelty of this idea has faded since I first proposed it, as there’s now much more competition. Still, I believe Fundation can offer unique onboarding focused on Web2 developers — but I’ll leave that decision to W3F.