humanity protocol
  • Introduction
    • Overview
    • How Humanity Protocol Works
    • Palm Scanner
  • Getting Started
    • Network Configuration
    • Important Links
  • Testnet Info
    • Onboarding Tutorial
    • Testnet Rewards
    • Testnet FAQ
  • Build on Humanity
    • API
      • Issue Credentials (VCs)
      • Verify Credentials (VCs)
      • Revoke Credentials (VCs)
      • List Client Credentials (VCs)
    • Contracts
      • VC contract
      • Rewards contract
    • Contract Integrations Guide
    • Examples
      • Fairdrops
      • Social Media VCs
  • Glossary
  • Community/Support
Powered by GitBook
On this page
  1. Build on Humanity
  2. Examples

Social Media VCs

PreviousFairdropsNextGlossary

Last updated 3 months ago

Social VCs in Humanity Protocol

Humanity Protocol internally leverages Verifiable Credentials (VCs) to authenticate users' social media connections in a privacy-preserving way. This enables trustless verification while ensuring no personal data is exposed on-chain.

How Social VCs Work

  • Users can connect their social media accounts (e.g., Telegram, Gmail) to their Human ID.

  • Human Institute issues a Verifiable Credential (VC) confirming the connection, which is stored off-chain. The VC indicates that the user does have a social media account.

  • A VC is then published on-chain, allowing third parties to verify the credential without revealing sensitive user data.

  • The only on-chain data stored is a flag indicating whether a DID has an active social media connection (e.g., "Has linked Google: True").

  • Humanity Protocol does not store email addresses, usernames, or any other private identifiers on-chain.

This implementation demonstrates the power of verifiable credentials and allows for secure, private, and decentralized identity verification while maintaining full compliance with Web3 principles. By using VCs and ZK proofs, Humanity Protocol ensures:

  • User Privacy: No sensitive information is exposed.

  • Trustless Verification: The system can validate a connection without needing to trust a centralized entity.

  • Interoperability: Other dApps or Web3 projects can adopt a similar approach to verify social media presence without compromising privacy.

Sample use case: Rewarding Users for Social Media Connections

To encourage participation, Humanity Protocol rewards users for linking their social accounts:

  • Each connected account grants an extra 10% daily reward (e.g., linking Telegram and Gmail provides a 20% boost).

  • If a user disconnects an account, they lose the associated reward increase.

  • A single social media account can only be linked to one Human ID to prevent abuse.

By integrating Verifiable Credentials in a decentralized and privacy-first manner, we demonstrate how any project can use VCs for secure, user-friendly identity verification while maintaining privacy and on-chain integrity.

Social VCs - social login incentives on humanity protocol