-
Notifications
You must be signed in to change notification settings - Fork 90
DotPassport application #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
updating the deliverables as received feedback.
Hi @SachinCoder1 thank you for your application! With DotPassport being something that can easily be integrated to any dApp, do you plan on delivering an MVP that would demonstrate its usage ? This would be useful to bring beta users to DotPassport for once you completed the work in these milestones. |
Hi @sacha-l, great question! Yes, the MVP will be delivered as part of the milestones outlined in the application. Once DotPassport is live, I plan to participate in hackathons to demonstrate its potential and encourage developers and projects to integrate it. I’ll also be reaching out directly to potential users and ecosystem teams to onboard early adopters and gather feedback based on real-world use. As I move forward, I’ll be exploring multiple strategies to drive adoption — including user/developer outreach, collaboration with dApps and wallets, and more. Once I’ve validated the product through beta testing and iterated based on feedback, I intend to bring on a growth expert to help scale adoption further. If you have any suggestions around marketing or attracting users/projects, I’d love to hear them! I’m actively learning in that area and open to new ideas. |
I supposes the top of mind question for this MVP is what will the trust scores be composed of concretely and how do you envision they might be meaningful to potential users? An initial target user and plan to attract them would clarify these points. |
Hi @sacha-l , thanks for clarifying your question! The trust scores in DotPassport will be primarily composed of concrete, verifiable on-chain activities, including:
These components combine to generate a meaningful reputation profile, reflecting genuine, long-term ecosystem engagement rather than superficial metrics. These scores enable users to build verifiable reputations, unlocking personalized rewards, gated experiences, and recognition within the Polkadot ecosystem For the initial MVP, my primary target users will be active Polkadot ecosystem participants who frequently engage in governance, staking, and NFT communities. I plan to attract these early adopters through:
Once initial adoption is established, the insights from these early users will guide further refinement and ensure the trust scores remain accurate, relevant, and valuable for both users and integrating dApps. Let me know if you have further questions or suggestions! |
💪 Project Abstract
DotPassport is a Polkadot-native identity and reputation protocol that aggregates on-chain activity across staking, governance, NFTs, DAOs, and more to issue verifiable badges and trust scores. It enables users to build portable, user-owned profiles that reflect their ecosystem contributions, while providing dApps and parachains with a plug-and-play SDK and API to integrate reputation-based features like gating, rewards, and personalization.
Unlike credential-focused systems like KILT, DotPassport emphasizes usage-based reputation and trust signals that are native to Polkadot’s ecosystem. It leverages Substrate, the identity pallet, and XCM for cross-chain functionality. The grant will fund the development of the reputation engine, user-facing profile interface, SDK/API integration layer, and wallet plugins — laying the foundation for a unified identity layer across the Polkadot ecosystem.
✅ Application Checklist
project_name.md
).