IncentiVerse Product Strategy

  • Home /
  • IncentiVerse product strategy

Vision

IncentiVerse aims to become the foundational protocol for managing work experience, education, marketing credentials, and networking. It enables builders to create decentralized applications that redefine professional interactions while prioritizing user ownership, privacy, and interoperability.

To enhance interoperability and showcase IncentiVerse’s potential, the protocol will support federated social media integration. This will start with application-level implementation of BlueSky’s AT Protocol, followed by the abstraction of this functionality into a dedicated decentralized layer. This “federation protocol” will act as a bridge between IncentiVerse and federated systems, much like the Lightning Network complements Bitcoin.

Core design principles

  • Protocol-centric: IncentiVerse is primarily a protocol, providing building blocks for builders. It is not a direct competitor to any existing platform but an enabler for creating decentralized professional networks and related applications.
  • Modular and Scalable: The protocol is designed for flexibility, allowing integration with other ecosystems and evolving as the Web3 landscape grows.
  • User Empowerment: IncentiVerse ensures users maintain control over their data, credentials, and identity.

Build-in-public strategy

Initial focus

To establish a strong foundation, the IncentiVerse protocol will prioritize education and work experience credentials. These are critical pillars for professional networks and demonstrate the protocol’s core capabilities. The marketing credentials feature will be added in subsequent phases to ensure focus and refinement in the early stages.

Benefits of build-in-public

  • Transparency: Engages the community by showcasing development progress and challenges.
  • Early feedback: Allows builders and potential users to provide input, improving the protocol’s usability and adoption potential.
  • Community building: Establishes trust and loyalty among early adopters and contributors.

Implementation roadmap

By prioritizing education and work experience credentials, IncentiVerse ensures a focused and impactful launch while laying the groundwork for long-term innovation and adoption.

Phase 1: Education and work experience credentials

  • Continue the work and milestones that have already been accomplished during our participation in the Polkadot hackathon and accelerator by Encode club.
  • Design and deploy foundational features for managing and verifying education and work experience credentials.
  • Enable interoperability with Web3 identity systems and decentralized storage solutions.
  • Share progress and gather feedback through regular updates, hackathons, and open forums.

Phase 2: Professional networking challenger application

  • Develop a flagship application on top of IncentiVerse, showcasing its potential to builders and users.
  • Integrate with federated social media protocols (starting with the AT Protocol) at the application level.

Phase 3: Marketing credentials

  • Expand the protocol to include marketing credentials, ensuring seamless integration with the existing features.
  • Leverage learnings from the initial phases to enhance scalability and user experience.

Next Steps

Finalize technical requirements:

  • Define the scope and architecture for the initial implementation of education and work experience credentials.
  • Define the impact of JAM and agile coretime on the current design. JAM/agile coretime might offer a better solution than becoming a parachain.
  • Refine key milestones and resource needs for development.

Engage stakeholders:

  • Initiate discussions with early adopters and builders to align the protocol’s direction with user needs.
  • Start collaborating with complementing protocols and ecosystems to offer a high value to builders and users.

Launch and iterate:

  • Deploy the foundational protocol features and build momentum with the community.
  • Use insights from the education and work experience phases to guide the addition of marketing credentials and federated integrations.