#
🚧 Roadmap
We are sharing the public part of our roadmap here, which includes the points we can communicate about. Some points and features are not included because it is strategically or technically too early to make shared commitments. For example, Passkey support, which would simplify onboarding and could remove the need for the 12-word backup, was discussed but deemed uncertain as it depends on the roadmaps of Android and iOS.
#
Notes on the previous 2023 Roadmap:
- The presentation of multiple badges (Shareable Profile) required the development of a new Badge Explorer to enable broader functionalities, such as the real-time synchronized sharing of badges received by users with an existing Web 2.0 site or a Discord server (see below).
- "Administration delegation" has now become "community manager delegation." For simplified professional onboarding, it will be possible to use a simpler login, such as a magic link received by email, making the use of the application optional for managers and facilitating delegation and programmed use via API.
- The digital signature demonstrator will be finalized this month.
- The demonstrator for metaverse integration for achievement badges will be finalized this month.
- The ticketing system has been improved to account for field constraints, and a first version will be finalized this month.
- Integration with an SSO portal system has been paused pending the finalization of the OPENID4VC standard, which we have chosen to support https://openid.net/sg/openid4vc/.
#
Notes on the announced features of the new 2024 Roadmap:
#
Ticketing (Q2)
The ticketing system has been modified so that the ticket presented by its owner can be verified without an Internet connection by a verifier using the myDiD application.
#
Generic Verifier (Q2)
Beyond the ticketing system, which is an optimized type of badge, it will be possible to present any certified badge or participation badge in the form of an animated QR code that can be verified by any other user of the application.
#
Zero-Wait Panel (Q2)
Uploads to IPFS and transactions with the blockchain will be performed asynchronously. For those who have tested the studio part, we will gradually eliminate all waiting times (profile creation, templates, badges) making them almost instantaneous (a significant improvement in user experience).
#
Digital Signature (Q2)
A demonstrator for digitally signing PDF documents (without a certificate) from the myDid application will be made available online.
#
Metaverse Badges (Q2)
Badges can serve as a reward system to recognize achievements of participants in a metaverse. A demonstration space will be available.
#
Magic Link & Delegation (Q3)
Certain community managers prefer not to manage their keys directly (e.g., backing up the 12 words) and wish to manage their community collaboratively with different access rights. A custody system will be implemented to facilitate login to the studio via “simple” magic-links sent by email.
#
Social Networks Check (Q3)
An additional badge system will allow for the verification of real links between a myDid community and social networks (Twitter/X, Discord, etc.).
#
Public Communities (Q3)
myDid communities will be able to become public in an explorable directory on the application and the web. These communities will later have the opportunity to be highlighted and publish offers (see below).
#
Multi-Badge Checker (Q3)
The capability to obtain a web link to display and share an obtained badge (currently called “badge checker” internally) will be enhanced to represent multiple badges simultaneously, allowing users to create and share one or more publicly shareable profiles.
#
Manager Dashboard/Stats (Q3)
Users interacting with communities and badges will be able to send anonymous statistical information back to the community manager (such as community joined, badge receipt and sending, etc.). The manager will have a summarized version of the activity of their members.
#
Communities Members List (Q3)
Certain managers may request pseudonyms or nostr identifiers from users who join their community. These member lists could subsequently be shared among users to create more traditional social network-like channels and facilitate interaction between members of the same community.
#
App On-Boarding (Q3)
When a user joins a community, the manager can set up an automatic request for additional information to grant the user a special status badge (e.g., verified user). These details are directly requested within the myDid application (such as document uploads, photos, etc.). This type of decentralized initial registration (on-boarding) can potentially be synchronized with a Web 2.0 system.
#
Web 2.0 View Synchronization (Q3)
To bridge the gap with Web 2.0, recognizing the existence of community websites where members are already registered, an open-source web service will be made available to display synchronized views of certain badges received on the myDid wallet on the community website.
#
Badges Creation Wizards (Q3)
Managing a community by offering various types of badges is not always easy, and the studio should provide better guidance in proposing the best badges for your sector and community. This support will extend to suggesting visuals (using AI) during the badge creation process.
#
On-Demand Survey (Q3)
Community managers will be able to create questionnaires and surveys to:
- Obtain better statistical but anonymous knowledge of their members (requesting additional information)
- Ask their community for input to make informed decisions
- Offer surveys to individuals outside their community
Access to some of these features will be paid for managers and rewardable with SYL tokens for users. This functionality aims to provide more ethical and privacy-respecting intelligent solutions for surveying and advertising within decentralized communities (code name Cortex).
#
Manager API (Q3)
Advanced features reserved for community managers are available through the web interface of the "studio" dedicated to them. For various use cases and at different stages, these actions need to be performed via a web service that allows for automation and integration with other web services, whether centralized or decentralized. The API will enable the automatic creation of communities and the programmable distribution of badges.
#
Discord View Synchronization (Q3)
To bridge the gap with existing community management tools like Discord, which is already widely used (including in Web 3.0 communities) and where many members are already registered, a "Discord bot" will be made available. This bot will enable the synchronized display of certain badges received on the myDid wallet within Discord, allowing for the public highlighting of the most active and well-rewarded members.
#
Manager HSM (Q4)
The authentication of certain managers outside the myDid application, whether for delegation purposes or to facilitate automation via the "Manager API," requires the retention of certain keys linked to their identity. Maximum security for these keys will be ensured via a secure server equipped with an HSM (Hardware Secure Module).
#
IA Community Copilot (Q4)
Beyond badge creation suggestions, and with the gradual transformation of the myDid wallet into a comprehensive communication tool centered around a decentralized social network with messaging, new interactions are possible for users and managers (chatbot, guidance, advice).
#
Advertisement & Offers (Q4)
Community managers will be able to highlight their communities in the lists of proposed communities on the online explorer and in the "Explore" section of the application. Offers (commercial or otherwise) can be displayed within the myDid application, both inside and outside communities, without the need for centralized tracking. Access to some of these features will be paid for managers and rewardable with SYL tokens for users. This functionality aims to provide more ethical and privacy-respecting intelligent solutions for surveying and advertising within decentralized communities (code name Cortex).
#
Nostr Messaging (Q4)
Users of the myDid application will be able to send messages directly to each other. Connecting with other users can be simplified through the use of public member lists within a community. This messaging system can also be used by community managers to communicate with their members. Each community member has the freedom to break a communication channel to avoid misuse (e.g., spam from a user or a manager) without disrupting other communication channels.
#
BTC & XRPL Support (Q4)
Supporting these two public blockchains, each created with different foundational philosophies, will demonstrate the technical neutrality of our solutions. Community managers will have the option to choose between Bitcoin, Gnosischain, and XRP Ledger for the creation of their profiles.
#
NFC Companion Card (Q4)
- Certain badges can be stored on an optional NFC card to facilitate specific uses (e.g., ticketing, occasional use without a mobile device, usage in aquatic environments) and can also be presented via NFC for verification.