After the official launch of dappKit, we decided to organize an AMA so that the community could clarify all doubts about the web3 SDK. Thanks to everyone that joined in and submitted questions, we had a blast!
For those that weren’t able to attend last week’s AMA session, here’s the full transcript of the questions and answers.
Mário Alves: That’s an awesome question. Usually, people ask me what's the point of doing an open-source product and how do we use it to scale to something else. First, this is a product for the community and also by the community.
This means that by being open-source, the community can develop an even better version of dappKit and everyone profits from it. It’s also related to our vision because, as you know, we’ve been doing hackathons and bounties and those companies and projects are in a more mature stage.
The overall vision is to start with dappKit for people that want to launch their project in the market. Once you build an MVP, you can use bounties to outsource highly skilled developers, and then, when you’ve matured and want to get more ideas and concepts, you launch a hackathon. This is the roadmap of the vision that we want to fulfill and truly become a developer economy in this space.
Mosh: Since dappKit is a complete rewrite of bepro.js, it made sense to rebrand and launch an entirely new product. dappKit is the next version of bepro.js, and both supersedes technically and logically, given it was written to be used as an extensible base to be worked upon, unlike the former bepro.js.
But it’s light away from all of these, both in the easiness of use and technical offerings. So much so that it currently backs the next version of the Bepro Network, and our test flight app (an inside app to test solidity contracts on a website, much like remix-UI).
Mário: When people think of web3 projects, they think it’s just for folks already involved and experienced in web3. We believe that mass adoption can only happen if there are bridges between web2 and web3.
Enabling these bridges will allow startups to create web3 projects, as also traditional web2 companies and corporations that want to explore web3, but don’t have the know-how or resources to do so.
Mário: At the moment we have a potential client in the financial sector and it’s going to be an interesting journey for them given they want to create a collection of NFTs for their clients.
But it doesn’t stop there. We are also in talks with other clients about dappKit. Rodrigo can you share a little bit more?
Rodrigo: Yes, that’s true. Right now we can’t tell you who the client is, but we are talking with incubators to use dappKit in their process to select web3 companies. An interesting insight we have is that people see dappKit as a great tool to bridge web2 with web3, so we are on the right track. We’ll share more details about these clients in the near future!
Mário: The reason why we’ve made it free to use is that we believe for new projects that don’t have resources in the development of their MVP, it doesn’t make sense to put a price on it. If we want mass adoption, we should put our money where our mouth is and that’s what we’re doing right now.
More than free for all, it’s an enabler and tool to accelerate the process. That’s our goal and why we believe dappKit will have a huge success, being an evolution of bepro.js (which we already had great companies using it), so we’re on the path of making this transformation happen faster than we could ask for.
Mosh: The project template section on our landing page works just as a helper for lazy coders to try out the dappKit (laughs). Without having to code much, they can see a running project.
We don’t have any plans to evolve it to community templates in the future, but it’s something we’re open to.
Mosh: We are finalizing an update to include gambling/betting contracts to the dappKit, which we count on having live very soon.
Mosh: For the moment we’re focusing on dappKit and V2 of Bepro Network.
Mosh: As we said in the previous answer, we are focused on finishing Bepro Network’s v2. It’s something we’d like to have, but can’t commit to right now.
Mário: Let me just jump in real quick to add something important.
We are focusing on 90% of the market. Everyone is using Ethereum standard in terms of tokens and NFTs, so we’re focusing on what the majority of the market is doing. However, that doesn’t necessarily mean that we’re just going to focus on Ethereum. Cardano, Near, and Avalanche are examples of a few chains we can pursue and understand if dappKit can work in them.
But as Mosh mentioned, for now, it’s still early to discuss it. (Then again, it’s an open-source project. Anyone can fork it and create its own version for Cardano, so it’s possible (laughs).
Mosh: New features developed by the community for dappKit will be built via bounties on the Bepro Network, so it will follow the normal flow of today. Our new features should enter normally, too.
Mário: Also, as you mentioned in one of your videos, there is the possibility to request funds to develop a specific product, kind of a reverse bounty. That will also be possible and a way for the community to propose something to be developed for the Bepro Network.
Mosh: Currently, our gitbook and documentation have general guides and we try to do that for each contract we have in place. This way, developers will be able to mimic the functionality of every contract.
Mário: We’re also planning to have webinars and interview people that have used dappKit to show other people that is not complex to use dappKit.
Mosh: It doesn’t quite work that way. The white-label network always receives the same updates that the Bepro Network receives. You can think of it as Bepro Network being an umbrella, and every network under it receives the update.
If networks want to add a specific feature, they will have to go to the Bepro Network, open a bounty to have someone develop the feature, and have it implemented.
Join a builder community, stay up-to-date with the developer economy and everything related to the ecosystem!