1. Who are Dataswyft’s competitors?
   1. In the verified credentials space, our competitors include ID.me, Onfido, Veriff, and Dock — while in the empowered tech space, we align with players like Inrupt, Prifina, Meeco and World Data Exchange who also focus on user-owned data and personal data ecosystems.”
2. How is the Dataswyft Wallet different from other digital or “self-sovereign identity” (SSI) wallets already in the market?
   • Most SSI wallets manage static credentials such as ID documents or certifications. The Dataswyft Wallet goes further by enabling verified credentials to be applied onto a “badge”, a carrier of proof and portability that can be validated by anyone and can also receive data. So Dataswyft Wallet isn’t a tech solution, it is also a network.
   • Built on the Smart Data Scheme framework, the Dataswyft Wallet is interoperable across applications, ecosystems, and jurisdictions.
3. How can you guarantee the accuracy and authenticity of the smart data generated by the MSMEs?
   1. We don’t guarantee. We digitize an existing trust system and enable the existing trust system to make their trusted data portable. For example, Kuza is already trusted by their service providers and agripreneurs. We merely provide the rails for all parties to use, share and receive data between one another without needing an intermediary.
4. How do you prevent fraud or gaming of the system by MSMEs or badge issuers?
   1. Dataswyft Wallet enable the signing of data by a trust anchor to be used for proof and portability / data sharing. It is merely the rails for the use of information within and between HAT Microservers.
5. What safeguards exist on the Dataswyft Wallet to ensure MSMEs’ privacy and data protection?
   1. The Dataswyft Wallet decouples verified credentials from the proof and portability layer — represented by badges. Issuers create badge templates and define the rules, while MSMEs use their own data / credentials to claim them. This design enables issuers to track badge activity without revealing identities, and data / credentials providers to provide data without knowing where or how it’s used — ensuring privacy, trust, and seamless interoperability.
   2. The Dataswyft Wallet doesn’t store any data belonging to users. It acts as a centralised meta-data catalog of what data is in HAT Microservers and enable the matching and discovery of available data through badges.
6. Who issues or governs these digital credentials, and how do you prevent their abuse? What and where are the guardrails?
   1. Theses digital credentials are created by the trust anchor. Dataswyft merely enable their portability. Guard rails are in the form of the smart data scheme where all parties agree to the rules of the scheme including what data / credentials are used by what badges and who is allowed to authenticate, validate or receive data.
7. How do you ensure interoperability with existing financial and identity systems?
   1. Every Dataswyft Wallet is attached to a HAT Microserver that is legally owned by the user — whether that user is an individual or a person acting with the authority of a business. This structure ensures that all data exchanges occur through the user’s own legal data container. A data receiver first receives data into the user’s HAT, and can then egress it under agreed rules. This separation between ownership, access, and transfer creates a standardized interface for data exchange, enabling full interoperability with existing financial and identity systems.
8. How will lenders or investors actually use these badges in practice?
   1. They join the network by signing up to the smart data scheme, get a Dataswyft Wallet on any app that has a Dataswyft Wallet, claim a “Dataswyft Merchant” badge in their wallet, fill in a form for KYB and choose the badge they wish to transact on. Once they are in the network, they can scan the QR code of the badge and receive the data into their when the badge holder chooses to share it. They can choose to download the data or egress it with standard data connectors.
9. How do you make sure MSMEs understand and trust the system?
   1. They are already trusting and using the trust anchor system. The Dataswyft Wallet enable that trust, signed by the ecosystem orchestrator, to be portable to service and finance providers for all parties sides to discover and interact with one another digitally.
10. What happens if a partner organization (like a lender) leaves the ecosystem?
    1. Their badge would expire and they no longer can use it as proofs nor can they share or receive data.
11. Does the Dataswyft Wallet infrastructure align with any global digital public infrastructure (DPI) or policy frameworks?
    1. Yes. The Dataswyft Wallet infrastructure aligns with emerging Global Digital Public Infrastructure (DPI) and policy frameworks that promote interoperability, trust, and user-centric data governance — including the principles behind the EU Data Act, OECD Data Governance Framework, and India’s Digital Public Infrastructure model. Each Dataswyft Wallet is attached to a HAT Microserver legally owned by the user, ensuring self-sovereign data custody and license-based sharing. This design supports the core DPI principles of open standards, user control, and data portability, making the Dataswyft Network interoperable with both public and private digital ecosystems.

Navigation

HATLAB Studio (Resources)

‣ (members only)

V0.1