# Demos Global

One Solution. Infinite Possibilities Unlock a world of secure, user-centric experiences


# Demos Overview

The integrity of the Demos enrollment system is paramount. The OnlyMeID protocol has undergone extensive User Acceptance Testing (UAT) to ensure its integrity, reliability, and seamless enrollment performance. We fortify our commitment to security by integrating cutting-edge global security innovations and establishing a world-class, on-chain security solution that protects personal and sensitive data.

 

As part of our robust security framework, Demos reserves the right to refuse access to the system at our discretion. Demos do not require justification for any refusal, ensuring an efficient and secure enrollment experience for all users while maintaining the highest data protection standards.

 

Our top priority is the security of our protocol, and we continue to monitor and update our systems to meet evolving global security standards.


# Introduction

DEMOS enhances Web3 security with intuitive and robust Sybil Resistance solutions, promoting human integrity, innovation and fairness across the digital landscape.

Central to our ecosystem is OnlyMeID, our flagship product, designed to provide frictionless and privacy-preserving identity verification, ensuring that every user is uniquely and securely authenticated seamlessly.

Our mission at DEMOS is to set a new standard in Sybil Resistance, streamlining user verification through a browser-based signup process with OnlyMeID, and eliminating the need for traditional KYC, documentation, or additional sign-ups.

The DEMOS and OnlyMeID suite extends beyond traditional boundaries with multi-chain capabilities, enabling unified and secure user verification across various blockchain platforms. 

Our solutions cater to a diverse range of applications and ecosystems across web3:\ <br>

* One-per-person NFT mints&#x20;
* Equitable token launches
* Democratic governance&#x20;
* Secure gaming&#x20;
* Bot and spam-free social media environments
* And more

Through this approach, DEMOS and OnlyMeID enhance the security and accessibility of Web3 interactions and pave the way for a more inclusive, equitable, and interconnected digital future.

### <mark style="color:yellow;">DEMOS Vision</mark>

DEMOS is dedicated to empowering users in web3, striving to offer a secure, intuitive, and accessible environment for crypto engagement. We aim to simplify access and foster participation in various projects, promoting fairness and creating meaningful experiences. By emphasizing privacy, user empowerment, and smooth onboarding, DEMOS enables users to engage confidently and securely. Our commitment lies in transferring control back to users, ensuring their interactions are private, secure, and user-driven.

We aim to set the standard for security within the blockchain, leading the charge for new ventures into this innovative landscape. DEMOS envisions establishing a universal benchmark that prioritizes human values, champions sustainability, and provides unparalleled security, setting a new precedent for web3.&#x20;

\
Our approach places humans at the forefront, fostering innovation and collaboration that empowers businesses to develop new and exciting products, services, and ecosystems with a strong emphasis on human interests and privacy. We strive to be the go-to partner for organizations looking to utilize blockchain and cryptocurrency technology, ensuring a smooth transition that upholds human safety, privacy, and equity. Our goal is to redefine security standards, enabling businesses to excel in the evolving digital environment.

<br>


# Understanding Sybil Attacks and the Need for Robust Sybil Resistance

Sybil Attacks Explained

Sybil attacks represent a significant threat in both the digital and crypto spaces. They occur when an individual or entity creates multiple accounts or identities to manipulate a network or system. This deceptive strategy can severely undermine the integrity and fairness of any online ecosystem.

These attacks' growing frequency and sophistication highlight the urgent need for innovative solutions to combat Sybil Attacks and protect the integrity of both Web2 and Web3 platforms. By addressing these issues, we can foster a more secure, transparent, and user-centric digital environment, enabling users to engage confidently and securely in the world of Web3.

#### <mark style="color:yellow;">**Why Sybil Resistance is Critical:**</mark>

* Open, Permissionless Access: The crypto space thrives on inclusivity, allowing anyone worldwide to participate. However, this also lowers barriers for malicious actors to perform Sybil attacks.
* Financialized Interactions: In crypto, every action can carry economic weight, providing direct incentives for individuals to exploit systems through Sybil attacks.

<mark style="color:yellow;">**Real-Life Consequences of Sybil Attacks**</mark>**:**

* Astroturfing: Sophisticated actors have repeatedly been observed to infiltrate major social media platforms like Reddit, Twitter, and Facebook. These actors utilize numerous accounts, driving engagement and activity to influence public opinion over politics and social issues.
* Phishing networks: Scammers utilize automated accounts to comment and message Social Media users with nefarious links, which can lead to unassuming individuals being hacked or scammed.
* Distribution Denial of Service (DDoS) Attacks: Attackers simultaneously overwhelm a target web server by spamming activity from numerous entities. DDoS attacks are widespread and routinely lead to website or application downtime.

#### <mark style="color:yellow;">**Web3's Vulnerability: Airdrop Sybil Attacks:**</mark>

* [Aptos Airdrop](https://medium.com/@l1ghtik/how-much-money-did-sybils-get-from-last-airdrop-events-a5c969b36395): Sybil accounts manipulated token distribution, leading to a significant market impact and questioning the airdrop's integrity.
* [Arbitrum Airdrop](https://crypto.news/arbitrum-airdrop-marred-by-sybil-attacks/): Sybil accounts amassed a large portion of the total token supply, highlighting the need for better distribution fairness.

[Celestia Airdrop](https://mirror.xyz/x-explore.eth/LLEhX4OEOMiB2v8ToJZK3iFBFCyANa1Sv6rv4OPXFYo): Although addressed by the team, the presence of Sybil accounts affected community trust and token distribution.


# Biometric Proof of Personhood

DEMOS' strategy in combating Sybil attacks is encapsulated within the innovative framework of OnlyMeID, positioning our solution in the specialized niche of "Biometric Proof of Personhood" (PoP). This concept is pivotal in distinguishing genuine human participants from automated bots within digital and blockchain environments.

#### <mark style="color:yellow;">**Understanding Proof of Personhood (PoP):**</mark>

Proof of Personhood refers to methodologies that allow individuals to validate specific attributes or characteristics, affirming their existence and authenticity online and within blockchain networks. This sector includes:

* Social Oracles: Systems enabling users to authenticate off-chain credentials in an on-chain context, enhancing trust and security in digital interactions.
* On-Chain Identity: Mechanisms that compile a user's blockchain activities to build a credible on-chain reputation or credit history, fostering a transparent and accountable digital ecosystem.

#### <mark style="color:yellow;">**The Role of Biometric Proof of Personhood:**</mark>

Within the PoP landscape, Biometric Proof of Personhood stands out by leveraging unique biological data to confirm an individual's identity. This approach involves:

* Utilizing biometric inputs, such as facial recognition or fingerprints, to establish a user's personhood, ensuring that each participant in the network is a natural, unique human being.
* They enhance security and privacy by ensuring that biometric data is handled with the utmost care, aligning with DEMOS' commitment to user privacy and data protection.
* They provide a scalable and accessible solution that maintains the ethos of open, permissionless access while effectively thwarting Sybil attacks.

By integrating specific aspects from biometric Proof of Personhood, DEMOS and OnlyMeID address the critical challenge of Sybil attacks and contribute to a safer, more equitable, and transparent Web3 ecosystem. Our approach ensures that every user is authenticated discreetly and securely, paving the way for a future where digital interactions are trustworthy and user-centric.

<br>

<br>


# Token and Community


# Leaderboard and Community Engagement


# Demos Leaderboard

DEMOS introduces an innovative community engagement program through its dynamic leaderboard system. This mechanism gamifies engagement by rewarding users for various activities that enhance their involvement and loyalty to the DEMOS ecosystem.

Activities eligible for points include:

* Promoting DEMOS by referring new user sign-ups and project integrations.
* Voting in DAO governance.
* Contributing micro-work for the DAO.
* Participating in partner events and promotions.
* Engaging in special DEMOS activities and offerings.
* Holding veDEM membership NFTs, which further gamify engagement, allowing members to focus on token holdings or active project involvement.

### Leaderboard Mechanics

User activities are meticulously tracked via the DEMOS leaderboard, serving as a meta-aggregator for both internal and external campaigns within the DEMOS ecosystem:

* Internal Campaigns: These include DAO activities like app testing, community participation, and governance, created and managed by DEMOS itself.
* External Campaigns: DEMOS partners with leading questing providers and engagement platforms such as Postmint, GalXE, and Polygon. These external campaigns operate over defined "Sprints," including activities like affiliate/referral programs and social media engagements, broadening the scope and impact of user participation

### <mark style="color:yellow;">**Reward Structures and Criteria**</mark>

#### Engaged User Contributions

* User contributions are scored based on timing, volume, and quality. For instance, points can be earned for being the first to test a Demos app, generating the most OnlyMeID referrals, or creating high-quality social media posts. Successful participants earn badges after campaign conclusions, translating into points and future leaderboard benefits.

<mark style="color:yellow;">**Seasonal Competitions and Incentives**</mark>

Campaigns are grouped into Seasons, with points accrued translating into unique rewards and DEMOS Leaderboard points at each season's end. As users climb the leaderboard, they unlock increasing incentives, including:

* First-party and partner perks like whitelist spots.
* Physical rewards such as conference tickets and DEMOS merchandise.
* Monetary rewards including $DEM payouts and airdrops.
* Exclusive DAO “Executive” Status.
* Revenue sharing opportunities are reserved for the top-tier participants as the most significant reward.

By integrating these mechanics, Demos not only fortifies its ecosystem against Sybil attacks but also fosters a robust, engaged community that contributes to the project's success and resilience.

### &#x20;<mark style="color:yellow;">Leaderboard Incentives</mark>

<mark style="color:yellow;">**Progressive Rewards System**</mark>

As members of the DEMOS community accumulate points on the leaderboard, they unlock access to increasingly exclusive incentives, structured as follows:

* First-Party and Partner Perks: Early access to new features and exclusive whitelist opportunities.
* Physical Rewards: Tickets to conferences, meetups, and branded Demos merchandise.
* $DEM Payouts and Airdrops: Direct monetary rewards distributed as $DEM tokens.
* DAO “Executive” Status: Special status that offers additional governance powers and exclusive insights into project developments.
* Revenue Sharing: The most prestigious reward, reserved for top-tier community members, includes a share of project revenues, emphasizing the value placed on significant contributors.

<mark style="color:yellow;">**Top-Heavy Reward Distribution**</mark>

The revenue share, designed as the ultimate incentive, is exclusively available to the highest achievers on the leaderboard. This selective distribution ensures that those who contribute most substantially—via large token holdings or influential affiliate actions—receive the greatest rewards.

By structuring incentives this way, DEMOS maximizes the return for community members who deliver the most value, thereby fostering a highly motivated and productive community.

<br>


# $DEM Token


# $DEM Overview

## **Comprehensive Token Utility**

The $DEM token represents a cornerstone of the DEMOS product ecosystem, beginning with OnlyMeID, which provides a universal solution for Web3 projects to secure their operations against Sybil attacks.

The design principles behind $DEM are aimed at achieving the following goals simultaneously:

* Broad Incentivization: Encouraging community members, irrespective of their investment capacity, to undertake valuable, clearly defined tasks that benefit both the individual and the protocol.
* Scalable Revenue Model: Supporting a robust and adaptable economic framework that aligns with the project's long-term vision.
* Protection for Passive Holders: Safeguarding the interests of supporters who are less actively involved but sustain the project with their capital and trust.
* Governance and Administration: Establishing clear roles and responsibilities for token holders from the outset, ensuring effective oversight and decision-making.

As a result, the $DEM token system is designed to thrive on community confidence and advocacy, essential for DEMOS's ongoing success and scalability.

<br>


# veDEM Membership System

### <mark style="color:yellow;">**Tokenized Commitment and Rewards**</mark>

Members of the Demos community can opt to lock $DEM tokens to activate a membership within the ecosystem. This membership, symbolized as veDEM, affords various privileges:

* Economic Incentives: Rewards for completing designated tasks within the ecosystem.
* Expanded Opportunities: Access to exclusive first-party and partner rewards and privileges.
* Enhanced Governance Participation: A stronger voice in the DAO's decision-making processes.
* Additional $DEM Rewards: Opportunities for further token earnings through active participation.

### <mark style="color:yellow;">**Active Community Engagement**</mark>

Members are expected to contribute actively by referring new users to OnlyMeID, integrating projects with OnlyMeID, and participating in meaningful DAO operations. This engagement is crucial as it directly feeds into the leaderboard system, where active members compete and collaborate to promote and expand the Demos ecosystem.

<br>


# veDEM Mechanics

### <mark style="color:yellow;">**Flexible and Transferable Membership**</mark>

The veDEM membership adheres to the "veNFT" methodology, offering a unique, tokenized form of participation:

* Lockup and Tokenization: Upon locking up $DEM tokens, users receive an NFT that represents their membership and the duration of their token lockup, which directly impacts the locked $DEM value.
* Membership Flexibility: Members can choose to increase their locked position or reset their lockup period to adjust their level of commitment.
* Early Exit Options: Members can burn their membership NFTs to retrieve their locked tokens, subject to an early exit fee starting at 75% and decreasing linearly over the lockup period.
* Market Transferability: Membership NFTs can be freely transferred and may possess a variable market value, potentially ranging between the total locked value and the amount receivable upon early exit.

By integrating these mechanics, Demos ensures a vibrant community where token holders are not only stakeholders but also key players in driving the project forward.

<br>


# DAO Governance


# Overview

### <mark style="color:yellow;">**Quadratic Consensus Model**</mark>

DEMOS utilizes a governance system powered by an OnlyMeID-gated Quadratic consensus model, intricately linked with the Membership framework. This model ensures that every member's influence in governance decisions is proportional to their commitment to the ecosystem, as represented by the size of their token lockup.

#### <mark style="color:yellow;">Key Features of the Governance Model:</mark>

* Participation Eligibility: Only members who hold OnlyMeID can participate in governance activities, ensuring that those involved are invested and active within the community.
* Weighted Voting: Voting power is determined by the lockup size, allowing a fair and proportionate influence over decision-making processes.
* Quadratic Voting Mechanism: This method calculates the consensus by considering both the depth (the amount locked up) and the breadth (the number of votes) of voting, fostering a more democratic and equitable governance environment.

#### <mark style="color:yellow;">**Enhanced Roles for Top Performers**</mark>

In addition to the standard governance mechanisms, Demos recognizes and empowers its most active and high-performing members through elevated governance roles. Members who excel on the Leaderboard can achieve "DAO Executive" status, granting them additional privileges:

* Close Collaboration with the Core Team: DAO Executives engage directly with the core team, facilitating more efficient decision-making and strategy development.
* Advanced Governance Privileges: Executives enjoy enhanced influence in governance, allowing them to steer the community towards shared goals and greater collective benefit.

Through this governance model, DEMOS ensures that leadership and decision-making are deeply integrated with community engagement and investment. This system not only aligns with democratic principles but also empowers members to actively shape the future of the ecosystem.

<br>


# OnlyMeID

This and all other sections of the Demos Gitbook is WIP and subject to change at team's discretion.


# User Privacy & Safety

At DEMOS, we prioritize a no-KYC approach to Proof of Personhood, ensuring that users' privacy, security, and autonomy remain central to our operations. OnlyMeID embodies this ethos by implementing internal procedures and practices designed to maximize user privacy and minimize potential security risks.

It's crucial for OnlyMeID users to comprehend the scope and purpose of the data they provide. This transparency fosters informed decision-making and reinforces trust in our system.

#### <mark style="color:yellow;">User Information Stored:</mark>

* User Selfie: For enrollment, a snapshot from the live session is stored to enable AI-driven uniqueness checks. This ensures each user is distinct, supporting our system's scale and accuracy.
* Blockchain Address: The connected wallet address is stored to facilitate Proof of Liveness features, linking digital identity with blockchain activities.

<br>


# Understanding User Data

It's crucial for OnlyMeID users to comprehend the scope and purpose of the data they provide. This transparency fosters informed decision-making and reinforces trust in our system. User Information St


# User Autonomy and Control

In our commitment to user privacy and autonomy, DEMOS offers a feature known as the "Permissionless Purge." This functionality empowers users with the ultimate control over their data, allowing them to delete their enrollment in OnlyMeID without needing permission from any external authority. Here's a closer look at how this process works and the safeguards we've implemented to prevent misuse while ensuring user autonomy.&#x20;

<mark style="color:yellow;">**Permissionless Purge**</mark>: Users can delete their enrollment after a minimum period (one week), ensuring the integrity of our Sybil resistance while respecting user autonomy.


# How Users Can Initiate the Purge

* **User Dashboard:** Users can initiate the purge directly from their OnlyMeID dashboard. This dashboard is accessible once they log in using their blockchain address.
* **Purge Option:** Within the dashboard, there's a clearly marked option for "Purge biometrics." Selecting this option will start the purge process.
* **Confirmation Steps:** To prevent accidental deletions, users are asked to confirm their intention through a multi-step process. This includes the user initiating their own OnlyMeID burn onchain and confirming their choice to purge their data.


# Safeguards to Prevent Misuse

* <mark style="color:yellow;">**Minimum Enrollment Time**</mark>: There's a mandatory minimum enrollment time to deter misuse of the purge feature, such as attempting to bypass Sybil protection by re-enrolling. Users must wait for this period (e.g., one week) after their initial enrollment before they can initiate a purge.
* <mark style="color:yellow;">**Verification Checks:**</mark> Before the purge is executed, users undergo additional verification checks. This step ensures that the request is legitimate and not the result of a compromised account.
* <mark style="color:yellow;">**Audit Trails:**</mark> While personal data is purged, an anonymized audit trail is maintained for a limited period. This trail is crucial for maintaining the integrity of the system and for audit purposes, ensuring that the purge process itself cannot be exploited.


# Ensuring User Autonomy

The permissionless purge feature is a testament to DEMOS' dedication to user autonomy and privacy. It reflects our belief that users should have complete control over their data, without fearing permanent data retention or misuse. By implementing this feature, we empower our users to make informed decisions about their digital identities, reinforcing trust in our platform.

This process not only aligns with our privacy-first philosophy but also sets a new standard in the digital identity space. It demonstrates our commitment to building a more secure, user-centric web3 ecosystem, where user autonomy and privacy are paramount.

<br>


# Future Direction:

DEMOS is committed to enhancing privacy and minimizing data reliance. Our roadmap includes developing a leading Zero-Knowledge Biometric Proof of Personhood solution, further reducing the need for user data and increasing trust in our platform.

By adhering to these principles and continuously improving our technology, DEMOS aims to set the standard for privacy and security in the Web3 space, ensuring users can engage confidently and securely.


# Technical Documentation


# Biometric Authentication

OnlyMeID utilizes Biometric Proof of Personhood protocol, leveraging advanced biometric indicators to authenticate users uniquely and securely. Here's a closer look at the process and its significance:

1. <mark style="color:yellow;">**Enrollment Process:**</mark> Users engage with a selfie interface, following prompts that guide them through a series of head movements. This interaction, captured via the device's camera, is processed in seconds, showcasing the efficiency and user-friendliness of the system.
2. <mark style="color:yellow;">**AI Assessment:**</mark> The core of OnlyMeID's authentication process lies in its AI's ability to analyze numerous facial indicators. This AI generates a summary output hash, providing a “score” that evaluates the user's uniqueness and authenticity.
3. <mark style="color:yellow;">**Dual Tests for Authentication:**</mark>

* Proof of Uniqueness: Confirms the user's input as genuine and distinct from any previous entries, ensuring each enrollment is tied to a unique individual.
* Proof of Liveness: Available for previously enrolled users, this test verifies ongoing authenticity by matching new input against existing records, akin to FaceID technology.
* Proof of Humanity: A simplified verification that doesn't require an account but confirms the user is not a bot, similar to CAPTCHA services.

#### <mark style="color:yellow;">**Technical Enhancements and User Privacy**</mark>

The integration of these detailed biometric authentication processes with OnlyMeID's latest technical updates significantly bolsters the platform's security and accessibility:

* <mark style="color:yellow;">**Multi-Chain Support:**</mark> Expanding OnlyMeID across various blockchain platforms enhances user experience and interoperability, allowing for seamless verification across the Web3 ecosystem.
* <mark style="color:yellow;">**Permissionless Purge:**</mark> This feature has been refined for greater user control, allowing individuals to manage their data with enhanced privacy measures.
* <mark style="color:yellow;">**Advanced Security Protocols:**</mark> The introduction of new encryption standards and data protection protocols ensures the highest level of security for user biometric data.

This comprehensive outline of OnlyMeID's biometric authentication process underscores DEMOS' commitment to innovation, security, and user empowerment, paving the way for a safer and more interconnected Web3.

<br>


# On-Chain Implementation

### **Biometric Authentication with OnlyMeID**

OnlyMeID functions as a bridge between off-chain biometric authentication and on-chain activities, acting as an identity oracle. This integration allows users to verify their identity off-chain using the OnlyMeID browser-based interface and then represent this authentication on-chain through attestation.

#### <mark style="color:yellow;">**User Interaction Flow**</mark>

1. Web3 Wallet Connection: Users must connect their preferred web3 wallet to the OnlyMeID interface.
2. Ownership Verification: Users sign a message to confirm ownership of their connected web3 account.
3. Proof Generation: After engaging with the OnlyMeID product successfully, users generate a cryptographic proof via the interface.
4. On-Chain Enrollment: This proof is then utilized to update or create their enrollment data on-chain, including:
5. * A Soulbound ERC-20 'MeID' token representing the enrollment.
   * A timestamp marking the execution of the enrollment.

#### <mark style="color:yellow;">**Proof of Liveness Verification**</mark>

When users complete a Proof of Liveness Verification, they update their on-chain enrollment with additional information:

* The timestamp of their latest verification.
* It’s crucial to note that no biometric data is linked to the on-chain enrollment, ensuring privacy and data integrity.

#### <mark style="color:yellow;">**Smart Contract Integration for Human Gating**</mark>

Projects that wish to gate their operations behind OnlyMeID authentication need to adjust their smart contracts as follows:

1. Import the IERC20 interface balanceOf() read function
2. Create a global MeID address variable set to the MeID contract address
3. Add the following line of code to any function intended to be Human Gated:

require(IERC20(MeID).balanceOf(msg.sender) == 1, "User not Authenticated!")

#### <mark style="color:yellow;">**Post-Enrollment Interaction**</mark>

The above code will enforce logic requiring any user interacting with the corresponding smart contract function to hold a MeID token. Users who are not authorized will not be able to complete the transaction.

After successful enrollment, users can immediately interact with any protected smart contract function as normal, allowing for seamless access and enhanced security measures.

<br>


# Smart Contract Parameters

Coming soon!


# UI Release notes

Summary of UI/backend changes to support MeID eco system.

### 05/12/2025 | Version 1.1.0&#x20;

Changes included

* <mark style="color:yellow;">Version Number</mark> | Version code changes added to bottom right of UI webpage to provide a verification the page isn't cached.

<figure><img src="/files/XmwxVu4ySb0u7UQLBp4P" alt=""><figcaption><p>Version will change on every code deploy</p></figcaption></figure>

* <mark style="color:yellow;">Demos Analytics Page</mark> |  <mark style="color:yellow;">"Are you Human check"</mark>\
  <https://app.demos.global/analytics>

&#x20;      The Analytics page provides the wallet's status for the Meid token and verification  on each chain.

&#x20;      <mark style="color:yellow;">Are you human</mark>?  | an option to check the status of any wallet to report on the status of a wallet.   Enter a wallet address for a result on Hemi.

<figure><img src="/files/NYTPQ2sZN0EduzafVvni" alt=""><figcaption></figcaption></figure>

* <mark style="color:yellow;">Updated Popups</mark> | Errors & Warning messages displayed at bottom right of UI instead of top right for improved visability.

<figure><img src="/files/brHacauMwWQXbTHrhKAp" alt=""><figcaption><p>Errors &#x26; Warnings popup</p></figcaption></figure>

***

### **03/05/2025 | Hemi Mainnet Release**

<mark style="color:yellow;">**Hemi Mainnet**</mark> | Demos is pleased to announce Hemi Mainnet blockchain is now available in Demos.

<mark style="color:yellow;">**Metamask Binaries Upgrade**</mark>: Enhanced Metamask binaries to resolve connectivity issues and improve overall stability.

<mark style="color:yellow;">**RPC Performance Improvements:**</mark> Optimized performance to provide a better user experience, particularly in addressing blockchain latency concerns, including issues related to ‘Request failed—TypeError’ mitigated.

<mark style="color:yellow;">UI Enhancements:</mark> Updated visual blockchain widget to display the currently connected chain and partial wallet address for improved clarity.

<figure><img src="/files/OqsMLOZXj2T9dmrKlxUw" alt=""><figcaption></figcaption></figure>

<mark style="color:yellow;">**Demos Code API optimization:**</mark>  Optimization of requests (lower the number of them to make the ui smoother)

<mark style="color:yellow;">**Expanded Enrollment Error Messaging:**</mark> Enhanced error messaging to provide clearer, more user-friendly notifications when a user encounters an enrollment or verification failure.

<mark style="color:yellow;">**Wallet Owner Rotation Automation:**</mark> Streamlined the wallet rotation process, allowing users to change wallets without being dependent on the Demos Team's support. Users can burn and delete their existing enrollment, then re-enroll with another wallet, even if it was previously flagged as duplicates. The update ensures that users can return to previously flagged wallets after purging their primary wallet, allowing for seamless re-enrollment without errors if the process is s ownership.

<figure><img src="/files/o5M6Uxu9I2udMT3VFXdc" alt="" width="433"><figcaption><p>'Enroll' button is available on a wallet which is tagged allowing users to change</p></figcaption></figure>


# Overview


# Introduction

OnlyMeID offers projects a universal, permissionless solution for Sybil Resistance. With OnlyMeID, projects and developers can protect on-chain interactions behind a "Human Gate" - guaranteeing that only wallets corresponding to unique humans may pass through.

Specifically, OnlyMeID services integrations through an offering called Biometric Proof of Personhood. Individuals may utilize their own biometric input (Selfie) to attest themselves as a unique, human operator of their associated wallet address.

It's important to differentiate this "Human Authentication" process from traditional KYC methods. KYC is a cumbersome, invasive process that requires a user verify themselves through sensitive documents like Government IDs. Although KYC can be used simply for Human Authentication, entities requiring this verification garner much more information specific to each individual, such as their citizenship, identification, name, date of birth, and so on.

Instead, OnlyMeID utilizes biometric input solely for the purpose of confirming whether or not a user wallet address is operated by a unique human. This is the *only* attestation required to achieve Sybil Resistance, and the utilization of a biometric input is the most straightforward, universal mechanism to achieve this attestation.

OnlyMeID is an on-chain mechanism that is compatible with existing user wallets. Projects that reference OnlyMeID do so on-chain, directly in the corresponding Smart Contract calls. Once a user has enrolled with OnlyMeID and minted their enrollment, they can interact with the entire universe of OnlyMeID integrations as they normally would with any other Smart Contract.

Beyond the original authentication, users may return to OnlyMeID to sign in again and "refresh" their enrollment on-chain. Projects with higher stakes needs, that want to confirm accounts are not sold or enrollments are not coerced, can require a recent refresh in addition to/in place of the original enrollment.

When users authenticate and further interact with OnlyMeID, they are granted the ability to write transactions on-chain which attest to these interactions. Users pay a small fee on top of gas when they do so, which is how Demos generates revenue.


# Functionality

OnlyMeID provides a robust framework for identity verification within Web3 environments, harnessing biometric data to ensure the uniqueness and authenticity of each user. This system facilitates secure and trustworthy user interactions by linking off-chain biometric verification with on-chain attestations, creating a seamless bridge between real-world identity and digital presence.

#### <mark style="color:yellow;">**Enrollment Process**</mark>

The enrollment process is the initial step for a user to validate their identity using OnlyMeID. It involves several critical steps designed to establish and confirm the user's unique human identity:

1. <mark style="color:yellow;">Wallet Connection and Ownership Confirmation:</mark>

* Users start by connecting their Web3 wallet to the OnlyMeID platform.
* They then sign a message to confirm ownership of the connected wallet, establishing a link between their digital wallet and their physical identity.

2. <mark style="color:yellow;">Biometric Verification:</mark>

* Users provide a live selfie during the enrollment process.
* This selfie is vetted for authenticity to ensure it is not tampered with or digitally altered.
* It is also compared against other enrollments to confirm the uniqueness of the user, preventing duplicate identities within the system.

3. <mark style="color:yellow;">On-Chain Identity Minting:</mark>

* Upon successful enrollment, users are granted permission to mint their MeID on-chain.
* This MeID token acts as a digital attestation of their enrollment and unique human identity, securely stored on the blockchain.

The enrollment process not only verifies but also affirms the 'unique human-ness' of each user, integrating their biometric data with blockchain technology to create a reliable identity marker.

#### <mark style="color:yellow;">**Verification Process**</mark>

Post-enrollment, users can engage with the OnlyMeID system to periodically verify their identity. This verification process is crucial for maintaining the integrity and currency of user identities within the system:

1. <mark style="color:yellow;">Reconnection and Identity Confirmation:</mark>

* Users reconnect their wallet associated with an existing OnlyMeID enrollment.
* This step ensures that the digital identity is still controlled by the same user.

2. <mark style="color:yellow;">Live Selfie Verification:</mark>

* Users provide a new live selfie, which is vetted for authenticity similarly to the enrollment process.
* The new selfie is compared against previous enrollment and verification records for similarity matching, confirming the user’s consistent identity over time.

3. <mark style="color:yellow;">On-Chain Verification Update:</mark>

* Following successful verification, users are allowed to update their OMeID enrollment on-chain.
* A timestamp is added to their on-chain record, attesting to the latest sign-in and verification, enhancing the security and relevance of the identity verification.

This verification process serves as a 'Proof of Liveness' attestation, crucial for high-stakes integrations where real-time identity confirmation is necessary to prevent misuse, such as through over-the-counter (OTC) account transfers.

<mark style="color:yellow;">**High-Stakes Integration**</mark>

OnlyMeID is particularly valuable for environments requiring high levels of security and identity assurance. It prevents the abuse of services by ensuring that all accounts are tied to a verified and continually updated biometric identity, safeguarding against unauthorized account transfers and enhancing overall system integrity.

<br>


# Use-Cases

OnlyMeID is a widely applicable product offering that can aid numerous on-chain use-cases. Additionally, the ability for developers to build around a confidence of "Human Gating" can enable many use-cases which do not yet exist today.

**Existing Opportunities**

Numerous offerings and interactions in crypto today are currently vulnerable to Sybil Attacks. Here are just a select few:

* Democratic voting
* Fair and bot-free token launches
* One mint per person, first mint free, and other unique NFT launches
* Airdrops without bot/multi farming
* Rewards systems that can’t be gamed
* Improved Data and Analytics
* DeFi Insurance
* DeFi Credit Scores
* P2E systems
* Live Verification
* Anonymous Chat Verification - ensure the person you are dealing with is always the same person
* Professional Gaming - ensuring the user is who they say they are
* And much more

**Future Opportunities**

The above usecases are sensitive to Sybil Attacks, but not necessarily rendered unusable. Beyond existing use-cases, there is an entire universe of currently "locked" innovation on-chain, not accessible until the future builder has a reliable and extensive Sybil Resistance. Here are som potential ideas:

* **MEV-free systems**: Token launches, P2E games, and otherwise that would be decimated by botting, and more specifically, abuse of the mempool for Miner Extract Value (MEV) purposes. This could look like massively improved and more nuanced token launches, "dynamic" or living on-chain tokens, and much more.
* **Governance Emulation**: Virtually any "real world" governance structure is impossible on-chain besides  true Plutocracy (of which all DAO governance today is). Projects could experiment with more nuanced and intricate governance structures seen in the real world today and throughout modern history.
* **Autonomous Anti-Cheat**: Games, communities, and more do not have a system to eliminate bots and malicious activity that cannot be circumvented further by perpetrators. Demos fixes this.


# Unique Selling Points

### <mark style="color:yellow;">**Ease of Use**</mark>

DEMOS streamlines the user experience with an exceptionally quick and straightforward signup process. In just about 30 seconds, users can register using their existing devices. This contrasts sharply with competitors:

* Worldcoin requires users to schedule a physical appointment, complicating the signup process.
* Idena demands users undergo routine, cumbersome verification processes to maintain their validation status.
* ..

DEMOS eliminates these barriers, offering an accessible and user-friendly entry point into secure digital identity verification.

<mark style="color:yellow;">**Simple, Permissionless Integration**</mark>

DEMOS simplifies the integration process for developers and projects within the Web3 ecosystem. It provides public, universal, on-chain "Human Verified" attestations, allowing any project to enhance their smart contracts with robust security features by adding just one line of code. This ease of integration is supported by straightforward developer documentation, enabling seamless project integration and community onboarding without the need for complex negotiations.

<mark style="color:yellow;">**Token Alignment**</mark>

The $DEM token employs a lockup membership model, which aligns token incentives with community engagement and project success. This approach not only activates the community but also supports sustainable tokenomics, ensuring that $DEM incentives are directly connected to the long-term success and stability of the project.

<mark style="color:yellow;">**Crypto-native Implementation**</mark>

Tailored specifically for the Web3 and blockchain industries, DEMOS offers a crypto-native solution that seamlessly integrates with existing blockchain operations. Users can enroll using the wallet addresses they already use for other interactions, eliminating the need for projects to invest in additional engineering resources such as SDKs, APIs, or adapters. The entire process is maintained on-chain, reflecting a deep understanding of and commitment to the blockchain ecosystem.

<mark style="color:yellow;">**On-Chain Business Model**</mark>

Unlike many competitors who may not have a sustainable business model for public services, DEMOS incorporates a robust on-chain business model from the start. By embedding costs and revenue directly into on-chain interactions, DEMOS ensures that revenue generation is aligned with actual usage. This model also allows for transparent governance and management through token mechanics, fostering a financially viable and self-sustaining ecosystem.

<mark style="color:yellow;">**Privacy and Security**</mark>

DEMOS prioritizes user privacy and security by keeping all biometric data completely off-chain. Unlike some systems that rely on opaque algorithms and store raw data that could potentially be repurposed, DEMOS ensures that biometric verification remains private and secure. Additionally, users have the option to permissionlessly purge their enrollment data, offering an unprecedented level of control and security.

<br>


# Roadmap

**Multi-Provider Landscape**

Originally, OnlyMeID authentication is supported through the biometrics provider Persona. As Demos matures, the platform is designed in a way that can support additional biometrics providers. This will better decentralized and secure the offerings, as users and projects alike can choose across various providers and assess privacy, security, and compliance practices themselves.

**Attestation Extensions**

OnlyMeID reflects a lightweight implementation of Biometrics Proof of Personhood. As the Social Identity layer matures over time, the OnlyMeID enrollment could encompass other pieces of on-chain activity to establish a mure comprehensive user profile. This could refer to a process like interfacing with on-chain reputation systems or otherwise further integrate OnlyMeID into a user's "Social Graph".

**Demos App Layer**

Demos may explore first-party applications that are built on top of and enablyed enabled by OnlyMeID itself. This will give users more intrinsic value when they enroll in OnlyMeID and take advantage of our miscellaneous offerings.

**First-Party AI**

Ultimately, Demos intends to develop its first-party biomtric AI alongside the third-party providers. The benefit of a first-party AI is the ability to design it specifically around Sybil Resistance, and adhering to policies surrounding local attestation and open-source code that could qualify Demos as the first truly Zero Knowledge Biometric Proof of Personhood Protocol.


# Appendix


# Branding Kit

### Demos Logo

<figure><img src="/files/YXsIebB6JsMlLUiLY3NS" alt="" width="188"><figcaption><p>logo.png</p></figcaption></figure>

<figure><img src="/files/KC3yVtpTRt95NzFD1piY" alt="" width="113"><figcaption><p>logo.svg</p></figcaption></figure>

{% file src="/files/PWjfI8AxRakv96afZsDG" %}
logo.ai
{% endfile %}

<figure><img src="/files/y7jk0FN3mOgjeRj1tdBe" alt="" width="188"><figcaption><p>inverted.png</p></figcaption></figure>

<figure><img src="/files/xBVlPPlxO1Kbm3mS2iqB" alt="" width="188"><figcaption><p>gold.png</p></figcaption></figure>

### Banner

<figure><img src="/files/x5gwxtHyAeWLNljf4VwK" alt="" width="375"><figcaption><p>banner.png</p></figcaption></figure>

<figure><img src="/files/HTCrgLk047I9H4arKrg2" alt=""><figcaption><p>banner.svg</p></figcaption></figure>

{% file src="/files/OV3Sd6b8oMfdQS9t9QVc" %}
banner.ai
{% endfile %}

<figure><img src="/files/dQNA14592VAINHQu7lHo" alt="" width="188"><figcaption><p>invertedbanner.png</p></figcaption></figure>

<figure><img src="/files/BzYegXBzWPMJFkd31Wib" alt="" width="375"><figcaption><p>goldbanner.png</p></figcaption></figure>

### Style Sheet

{% file src="/files/Iv5Tb39tfl9CkAiI1cCo" %}
Style Sheet
{% endfile %}


# Demos Motivation


# Demos Motivation

The Demos structure is built upon an understanding that certain responsibilities must be maintained by a centralized team, while others can and should be delegated to token holders directly.

Much of this philosophy is derived from lessons learned at Governor DAO, the predecessor to Demos and the sister project responsible for the first iteration of OnlyMeID. Governor DAO was incepted as a fair launch, community-driven “unrug” of a previous project, CoinBreeder DAO, which exit scammed in Q3 2020.

Both Governor DAO and CoinBreeder DAO, at a very high level, are built around the ethos of “helping others do decentralization better”. This abstract, wide-sweeping mission spans the ability to help others launch DAOs, tokens, and NFTs - through a combination of proprietary products and services, community evangelism, and consulting-style professional support.

While Governor DAO carries many exciting and noteworthy achievements, its limited resourcing as a fair launch DAO and form-less structure also translated to many shortfalls, most of which can be summarized as an inability of community members to perform meaningful work, properly incentivized, independent from a core team.

This imperfect relationship can be exemplified: Governor DAO offers services like token launch support (full-stack engineering, economics, DAO setup, etc.) Projects must be vetted by the service provider to ensure fair play and the potential for a working relationship. Providers and clients must negotiate on terms like pricing, timelines, concrete deliverables, etc. In pursuit of supporting the mission, community members independently engage potential clients without the expertise to vet the client or the information and skills to negotiate the service package. The team is required to backtrack to the top after a handoff from a community member and feels obligated to pursue a tangible outcome due to allegiance to the community. This process is even more cumbersome than if the team had performed every step of the equation themselves.

In practice, this translated to an increasing burden of unprioritized, non-scaling, undelegated-able TODOs on a team with decreasing size and dwindling resources. As markets deteriorated, even the successful engagements surrounding consultation could not fund the project at a great enough capacity to compensate a team and incentivized token holders.

Per the guiding points above, Demos intends to set expectations from inception so that the community and team understand exactly how the two entities work alongside one another and that the community members are properly directed + incentivized for the work they can best benefit the project by performing.

The findings with Governor DAO are consistent with DAOs as a whole. Demos intends to unlock a system that works efficiently and equitably - and in a manner that exemplifies the hypothesized good qualities unlocked in a tokenized model.

Outside the DAO space, Demos utilizes a token ownership model to improve upon the shortcomings seen through the widely popular Curve “vote escrow” model, plus older systems like Sushi’s “xSUSHI” vault model.


# Proof of Existence


# Proof of Existence

The “version 1” core product offering was conceived by the core team through cooperation as Governor DAO, a fair launch volunteer collective, in 2021. The first rendition, Proof of Existence, attracted over 1,000 users and represents the first in-market Biometric Proof of Personhood protocol.

DEMOS and the “version 2” product stack, starting with OnlyMeID, represents the culmination of lessons learned from v1 and a dedicated, focused vision to establish DEMOS as the premier solution for Sybil Resistance and Bot-Proofing throughout the space.

DEMOS is independent of Governor DAO and is the sole owner of the Sybil Resistance product stack. In return, a small percentage of $DEM is allocated to $GDAO and Governor DAO, while Governor DAO maintains a separate roadmap outside Sybil Resistance and a dedicated community supporting it.

#### Purpose

The primary goal with DEMOS is to articulate and establish this “v2” as a significant evolution from the initial offering. Every component of the initial DEMOS launch is designed to answer the question, "Why v2?" While other endeavors are important to the overall success of the project, the primary focus is on creating a compelling narrative for v2 that resonates with DEMOS key audiences: investors, community members, and partners/users.

Given the current market landscape, there is a significant demand for a user-friendly, one-size-fits-all authentication product, especially one that respects user autonomy and can be easily integrated into any project.

Through alignment with Governor DAO, an existing community and a base of original adopters exist. The $DEM token will bootstrap the first users and integrations, offering long-term incentives to DAO members who recruit more users and encourage more projects to integrate with DEMOS.

DEMOS UX improvements are designed to maximize user retention and integration success. The sign-up and integration process for OnlyMeID will be seamless, reducing the risk of losing potential users or integrations due to technical difficulties.

As market share increases, the value of the DEMOS product stack also grows. The improved product capabilities and revenue capabilities suggest the ability to extend the product beyond the MVP, offering unique selling points once DEMOS matures beyond the token-subsidized growth hacking adoption subsidies.

DEMOS’ vision is to clearly communicate to users and projects the benefits of choosing $DEM and DEMOS, and to instill confidence in investors about DEMOS’ ability to create value and capture market share.

Version 1 (Governor DAO, Proof of Existence) lacked the dedicated resources, user-friendly experience, and cohesive vision necessary to support significant adoption. Additionally, the market was not as aware of the product we were offering.

Version 2 (DEMOS, OnlyMeID) is better positioned to target sophisticated market participants who already understand the value proposition, secure them with incentives, and utilize those engagements as a foundation to achieve widespread adoption. The overarching goal is to create a unique, differentiated, full-stack ecosystem to serve as the quintessential Sybil Resistance protocol.

#### Key Improvements

The transition from v1 to v2 includes several key improvements:

1. User Experience (UX) Improvements: 10x improvements to the user interface and overall experience to make it more intuitive and user-friendly.
2. $DEM Incentives & Privileges: Introducing new incentives and privileges for $DEM token holders to encourage participation and engagement.
3. Treasury & Runway: Financial backing and implementation of a more sustainable financial model to ensure the project's long-term viability.
4. &#x20;Clear Vision: A well-articulated, clear vision for DEMOS, emphasizing the mission of Securing Human Integrity through the Sybil Resistance product set.
5. Alignment of Community: Utilization of incentives, revenue, and DAO structure to activate community members as productive ambassadors.
6. Improved Business Model: Introduction of step-up product offerings and SaaS subscription models to enable large scale and higher-margin revenue opportunities.
7. Product Capabilities: Expansion of the product set to support a step-up set of Sybil Resistance and Bot-Proofing solutions.
8. Changing Market Dynamics: The market knowledge surrounding Biometric Proof of Personhood has rapidly expanded since v1.

Through continued refinement and development of DEMOS v2, the core team remains committed to the mission of empowering individuals in the digital world. Through emphasis on user empowerment, privacy, and security, DEMOS is differentiated against competitors in the industry and positioned for success.


# ⚙️How to Section


# OnlyMeID Enrollment Process

One pager on the high-level steps to enroll Demos OnlyMeID dApp and mint an OnlyMeID token Enrollment URL: https\://app.demos.global

***

<div><figure><img src="/files/nRy1y1Joe4R1x8KryUmM" alt=""><figcaption></figcaption></figure> <figure><img src="/files/SvzsQGXsZ4E39WBtdbVp" alt=""><figcaption></figcaption></figure></div>

### Introduction to Demos Enrollment process:&#x20;

{% embed url="<https://www.loom.com/share/51ba3d77eda446c89320a8374c00b2c1?sid=c932fbbf-e26d-4808-9ce9-89ee1cef9c96>" %}


# Token Bridge Guide & Add Chains to Wallet

Quick guide on how to bridge tokens and add network chains

<figure><img src="/files/knDBltqhubx0Gtwdfl4L" alt=""><figcaption></figcaption></figure>

### Demos currently supports.

* Hemi Mainnet
* Polygon Mainnet
* Blast Mainnet
* Base Mainnet

## **Platforms to use for bridging.**

The following Dex (Decentralized Exchanges) can be used to swap tokens with a swap & bridge to other chain options.

### <mark style="color:yellow;">Hemi Mainnet Tunnel</mark>

[Tunnel Link](https://app.hemi.xyz/en/tunnel/?networkType=mainnet)

<figure><img src="/files/FLQgvO1x8tCZRnioeWug" alt=""><figcaption></figcaption></figure>

### <mark style="color:yellow;">Stargate</mark>

[Stargate Bridge](https://stargate.finance/bridge?srcChain=ethereum\&dstChain=hemi)

### <mark style="color:yellow;">Free Tunnel</mark>

[Free Tunnel](https://tunnel.free.tech/)

### <mark style="color:yellow;">Meson Finance</mark>

[Meson Bridge](https://meson.fi/swap)

### <mark style="color:yellow;">Rubic Exchange</mark>

<https://app.rubic.exchange/>

Rubic Exchange can swap & bridge assets through simple choices on tokens and destination network chains.

#### **ETH Mainnet > Blast Mainnet**

*Examples*

#### <mark style="color:yellow;">**Bridge ETH from ETH Mainnet to Blast Mainnet**</mark>

{% embed url="<https://app.rubic.exchange/?fromChain=ETH&toChain=BLAST&from=ETH&to=ETH>" %}

#### ![](/files/kV3y2VjLVo3QkC7zSFQY)

#### <mark style="color:yellow;">**ETH > Matic token \[Swap & Bridge]**</mark>

Swap ETH to Matic via ‘bridge & swap’ from ETH Mainnet to Polygon Mainnet

{% embed url="<https://app.rubic.exchange/?fromChain=ETH&toChain=POLYGON&from=ETH&to=MATIC>" %}
Swap ETH to Matic via ‘bridge & swap’ from ETH Mainnet to Polygon Mainnet
{% endembed %}

#### <mark style="color:yellow;">**USDC > Matic Token \[Swap & Bridge]**</mark> Swap USDC to Matic with a ‘bridge & swap’ from ETH Mainnet to Polygon Mainnet

{% embed url="<https://app.rubic.exchange/?fromChain=ETH&toChain=POLYGON&from=USDC&to=MATIC>" %}
Swap USDC to Matic with a ‘bridge & swap’ from ETH Mainnet to Polygon Mainnet
{% endembed %}

### ![](/files/yDvUJNjCohSnpNmFIJJW)

#### <mark style="color:yellow;">**ETH Mainnet > Base Mainnet**</mark>

*Examples*

#### **Bridge ETH from ETH Mainnet to Base Mainnet**

{% embed url="<https://app.rubic.exchange/?from=ETH&fromChain=ETH&to=ETH&toChain=BASE>" %}
URL for ETH mainnet to ETH on Base Mainnet conversion
{% endembed %}

<div align="left"><figure><img src="/files/C4Ubxv4bWhBzcHMZjlMx" alt="" width="375"><figcaption><p>ETH Mainnet to Base Mainnet</p></figcaption></figure></div>

### Additional DEX

### **Owl Finance**

<https://owlto.finance/?ref=0xD8c84eaC995150662CC052E6ac76Ec184fcF1122>

### **Polygon Portal**

<https://portal.polygon.technology/swap>

<https://portal.polygon.technology/bridge><br>

## How to add blockchain networks to wallets

The following link will navigate to a website that will add the networks with ease by ‘Add to metamask'

### Blast Mainnet

<https://chainlist.org/chain/81457>

Recommend choosing the following “RPC Server Address”.

<https://rpc.blast.io>

<figure><img src="/files/vrudTsI8KFZvVncZwHZt" alt=""><figcaption><p>Option to choose <a href="https://rpc.blast.io">https://rpc.blast.io</a></p></figcaption></figure>

### Polygon Mainnet

<https://chainlist.org/chain/137>


# Demos dApp Support

Important to add wallet address otherwise the support team may not be able to assist.

<mark style="color:yellow;">**Contacting Demos Support**</mark>

Please email **<support@demos.global>** with

1. The issue you are experiencing
2. wallet address
3. Discord Username


# Demos / Hemi Overview

https\://points.absinthe.network/hemi

Addressing questions raised on why wallet owners require a re-verification.

There are three parts to the Demos Enrollment process

1\)      <mark style="color:yellow;">**Proof of Existence**</mark> | Enroll your wallet and identity through sign-up (off-chain)

2\)      <mark style="color:yellow;">**OnlyMeID Token**</mark> | After enrolling off-chain, mint a MeID token on-chain.

3\)      <mark style="color:yellow;">**Proof of Liveness**</mark> | When active, the option to ‘verify’ on-chain to verify your wallet ownership. The timestamp will be displayed in the Demos UI (dApp)

&#x20;

<mark style="color:yellow;">**Re-verification**</mark>, or officially ‘[<mark style="color:yellow;">**Proof of**</mark> ](/demos-overview/biometric-proof-of-personhood)<mark style="color:yellow;">**Liveness'**</mark>, is a service in which Demos provide continued protocol integrity. Demos Global, to date, is unique in providing the option for continued verification, which is recorded on-chain and can be used for many outcomes.

\-          Periodic check-ins to accumulate points or rewards requested by a protocol ie Hemi

\-          Confidence: The person who enrolled on a wallet remains the person who initially enrolled, which is the core mantra of Demos Global: ‘<mark style="color:yellow;">1 person, 1 wallet</mark>’.

\-          Last active timestamp on-chain.

Snapshot voting | Confidence: The wallets contributing to votes could be requested to ensure they have updated their on-chain POP before each vote or after a specific period for a continued 1-person 1 wallet trust.

\-          Additional user cases detailed here: [https://docs.demos.global/onlymeid/overview/use-cases](/onlymeid/overview/use-cases)

&#x20;<mark style="color:yellow;">Proof of Personhood Link</mark>

[https://docs.demos.global/demos-overview/biometric-proof-of-personhood](/demos-overview/biometric-proof-of-personhood)

### <mark style="color:yellow;">Demos Global System Integrity</mark>

&#x20;The integrity of the Demos enrollment system is paramount. The OnlyMeID protocol has undergone extensive User Acceptance Testing (UAT) to ensure its integrity, reliability, and seamless enrollment performance. We fortify our commitment to security by integrating cutting-edge global security innovations and establishing a world-class, on-chain security solution that protects personal and sensitive data.

&#x20;As part of our robust security framework, Demos reserves the right to refuse access to the system at our discretion. Demos do not require justification for any refusal, ensuring an efficient and secure enrollment experience for all users while maintaining the highest data protection standards.

&#x20;Our top priority is the security of our protocol, and we continue to monitor and update our systems to meet evolving global security standards.

&#x20;The company has limited capacity to service edge case users reporting client-side issues primarily due to a lack of technical knowledge of our products. These issues include claims of unawareness of prior enrollments and verifications on another device or in a previous period and how to connect a wallet. Information that has been provided numerous times.

&#x20;<mark style="color:yellow;">**Swarms & Face Harvesting**</mark>

Based on intelligent traffic patterns and behaviour analysis, the company can make positive decisions that ensure and reinforce the system's stability, which is not influenced by individual user awareness or actions.

<mark style="color:yellow;">**Discord Terms & Conditions.**</mark>

&#x20;Users in Discord who continue to report incorrect and misleading information to other users risk a ban. Information has been provided to advise to engage the Demos support team via email, which users can utilise.

&#x20;For users who repeatedly contact the Demos support team claiming their wallet has been incorrectly flagged as a duplicate, the support team responds to all initial inquiries, providing relevant information, including details about the enrolled wallet and steps for resolution.

&#x20;In some cases, individuals fail to accept and acknowledge they are enrolled on an alternative wallet. Unfortunately, the Demos support team cannot offer a solution for users who are unaware of how they enrolled on a different wallet.&#x20;

Furthermore, on occasions, traffic patterns indicate a high volume of users enrolling through shared devices, which aligns with other protocol patterns and face harvesting to secure an identity on a wallet for gain. This activity can contribute to challenges managing multiple wallets associated with a single device or PC, potentially leading to a confused user experience when users have enrolled already but the device owner is unaware.

## Additional Hemi Resources

<mark style="color:orange;">Hemi Website</mark>

{% embed url="<https://hemi.xyz/>" %}

<mark style="color:orange;">**Hemi Status Page**</mark>

If issues are experienced when accessing Demos Website ie RPC errors please check the status of the Hemi Services.

{% embed url="<https://hemistatus.com/en>" %}

{% embed url="<https://hemistatus.com/en/maintenance>" %}

<mark style="color:orange;">**Hemi Twitter (X) Account**</mark>

{% embed url="<https://x.com/hemi_xyz>" %}


# Hemi Support Notes

Details of issues raised by Discord Users

### <mark style="color:yellow;">High level Overview</mark>

Deleting your enrollment and burning your token will provide the following.&#x20;

<mark style="color:yellow;">**\[1st Stage]**</mark> Delete MeID Token on all chains | From 3 days of enrolling, a wallet can firstly ‘burn’ or delete their MEID token 1st. The token was minted with a face after enrollment. **{Warning , the MeID token needs to be older than 3 days to burn the token, therefore if the age of the token is less than 3 days a timer will appear}**&#x20;

<mark style="color:yellow;">**\[2nd Stage]**</mark> Delete MeID Enrollment | After the MEID Token has been deleted, there will be an option to burn/delete the MEID enrollment associated with the wallet. The option to delete the MEID Enrollment will only appear once the MeID token is deleted. **Important to note**: If you have minted a MeID token on other chains, e.g., Polygon, you will need to burn the token on those chains, too. Switching to other chains is available on the page.&#x20;

<mark style="color:yellow;">**\[3rd Stage]**</mark> Purging account data | When stages 1 & 2 are complete, a message will appear advising to return after 24 hours, when the enrollment will be deleted from the system. The message will display a countdown. A new person cannot enrol on the wallet until the timeout has been completed. When steps 1 and 2 are complete, the enrollment and token have been deleted, and timeout \[stage 3] has timed out, that wallet is no longer owned or associated with DEMOS MeID system or contract. **Very Important Note: If a wallet has been tagged as a DUPLICATE, the wallet will be untagged and error removed after a peson successfully enrolls on the flagged wallet. If the person has purged their enrollment on another wallet, they can attempt to enroll on the flagged wallet.**

When steps 1, 2, and 3 are complete, anyone with access to that wallet can enroll again and mint a token. It is important to note that some users may not have minted a MeID token and want to change wallets. If this is true, the person must follow step 2 to delete their enrollment.

***

### <mark style="color:yellow;">**Enrollment logic and policies**</mark>

1. The basic principle of the Demos solution.

<mark style="color:yellow;">1 WALLET > 1 ENROLLMENT > 1 MEID TOKEN ON HEMI TESTNET PERMITTED</mark>

2. <mark style="color:yellow;">**Duplicate Warnings**</mark> | If a person is enrolled in the DEMOS system and the enrolled person attempts to enroll on any additional wallets, that wallet will be FLAGGED AS A DUPLICATE.

**When a wallet is flagged as a duplicate, an error will be displayed until a user successfully enrolls on the wallet which maybe after a purge on another wallet.**

3. <mark style="color:yellow;">**Purge/Delete Enrollment**</mark> | If a person decides to change wallets, please consider the following

&#x20;         \-  Burning MeID token will require 3 days timeout after activation of the delete

&#x20;          \- Each person can only own 1 MeID token on Hemi Testnet, so it doesn’t matter how often a    person switches wallets. If they mint a token, everyone will only be enrolled once with 1 MeID token.

&#x20;        \- There are two parts to deleting your profile from Demos

&#x20;                 \--<mark style="color:yellow;">Burn MeID token if minted (3-day timeout) --Delete enrollment (7-day timeout)</mark>

4. When the purge/deletion has been completed, and the person must use another wallet previously tagged as a duplicate, please look at point 2 above.

**The DEMOS team must assess any wallet flagged as a duplicate.**

5. **Settings Button:** If the button doesn’t appear, ensure the connected wallet has ETH for transactions.
6. *Enroll* button: Users report that the button is unavailable. When a person moves their mouse over it, the button changes to yellow.
7. Once steps have been completed to a) burn MeID token and b) Delete/purge your enrollment the person can enroll on another wallet which will include a wallet that is tagged as a duplicate.

***

### <mark style="color:yellow;">How to Burn / Delete your enrollment</mark>

{% content-ref url="/pages/BDFX5A7o45y9UqES50Gi" %}
[How to burn/delete enrollment](/how-to-section/demos-hemi-overview/how-to-burn-delete-enrollment)
{% endcontent-ref %}

### <mark style="color:yellow;">How to connect to Hemi BlockChain</mark>

{% content-ref url="/pages/NpZgAfCyZutAwedbzfCk" %}
[How to connect to Hemi BlockChain](/how-to-section/demos-hemi-overview/how-to-connect-to-hemi-blockchain)
{% endcontent-ref %}

***


# How to connect to Hemi BlockChain

## <mark style="color:yellow;">Hemi Mainnet</mark>

* Network Name: Hemi Mainnet
* **Chain ID:** 43111
* **Gas Token:** ETH
* **Mainnet Explorer:** <https://explorer.hemi.xyz/>
* **Mainnet RPC:** <https://rpc.hemi.network/rpc>

### <mark style="color:yellow;">Hemi Sepolia \[Testnet]</mark>&#x20;

* Chain ID : 743111&#x20;
* **Gas Token:** ETH
* **Testnet Explorer:** <https://testnet.rpc.hemi.network/rpc>
* Block explorer URL (Optional) <https://testnet.explorer.hemi.xyz/>


# Reported issues & Questions

Issues reported with feedback

### *<mark style="color:yellow;">#1 Enrollment failed due to a multiple persons associated to wallet.</mark>*

*<mark style="color:yellow;">**Error**</mark>**&#x20;**<mark style="color:red;">**'Could not complete your verification due to a duplicate enrollment'**</mark>*

When attempting to enroll, if presented with the following message ‘*<mark style="color:yellow;">Could not complete your verification due to a duplicate enrollment</mark>*’ and the image below, the system has detected a <mark style="color:yellow;">**different**</mark> person who has attempted to enroll on the wallet previously.

&#x20;To explain further, if <mark style="color:blue;">\[Person 1]</mark> attempts to enrol on <mark style="color:green;">\[Wallet 1]</mark> it fails due to environmental conditions, such as lighting conditions, face positioning, etc. If <mark style="color:blue;">\[Person 1]</mark> fails enrollment and <mark style="color:purple;">\[person 2]</mark> attempts to enrol on <mark style="color:green;">\[Wallet 1</mark>], this will fail on <mark style="color:green;">\[Wallet 1]</mark>. Please contact <mark style="color:yellow;"><support@demos.global></mark> for advise.\
\
![](/files/GRI1bFsdb2JRWOFZf6AY)

Workaround, if a person is unclear who enrolled on the wallet, the option is to purge the enrollment following the instructions detailed here.&#x20;

{% content-ref url="/pages/BDFX5A7o45y9UqES50Gi" %}
[How to burn/delete enrollment](/how-to-section/demos-hemi-overview/how-to-burn-delete-enrollment)
{% endcontent-ref %}

### <mark style="color:yellow;">#2 Duplicate wallet warning</mark>

If the following error is displayed the Demos system has dectected a person is already <mark style="color:yellow;">'{onboarded}'</mark>. If a person is already enrolled <mark style="color:yellow;">{onboarded}</mark> and there is another attempt to enroll on another wallet the error displayed below will be displayed.\
*<mark style="color:red;">**"Our records report the biometrics on the connected wallet are enrolled on a different wallet already"**</mark>*

<figure><img src="/files/5s0kWeCWa25W1VgvP9L7" alt=""><figcaption><p><br>Example of a wallet which has detected multiple enrollments</p></figcaption></figure>

## <mark style="color:yellow;">Hemi Mainnet Feature Changes</mark>

Previously, when a wallet was detected as a duplicate, the '<mark style="color:yellow;">enroll</mark>' button was disabled therefore required Demos team to address.\
New feature will allow a wallet owner to purge their MeID token, the biometric enrollment and change wallets that may have been tagged as a duplicate.

Revised changes will allow a previously disabled wallet to allow a user to attempt to enroll after a wallet is displaying an error. On success if that person is not detected in the system,

&#x20;the person will be 'onboarded' onto the wallet with the removal of the error message.\
\ <mark style="color:yellow;">**Important note :**</mark> 1 WALLET > 1 ENROLLMENT > 1 MEID TOKEN ON HEMI PERMITTED

<mark style="color:purple;">The Demos system will not allow anyone to enroll against multiple wallets.</mark>

To explain further, if <mark style="color:yellow;background-color:yellow;">\[Person 1]</mark> attempts enroll on <mark style="background-color:orange;">\[Wallet 1]</mark> the status will be <mark style="color:purple;">**\[onboarded]**</mark>

If <mark style="color:yellow;">**\[Person 1]**</mark> attempts to enroll on <mark style="background-color:orange;">\[Wallet 2]</mark> as that person is already onboarded in the Demos system <mark style="background-color:orange;">\[Wallet 2]</mark> will detect and display an error message.

If <mark style="color:yellow;background-color:yellow;">\[Person 1]</mark> wishes to change wallets, there is a procedure which can be followed to clean their enrolled wallet in order to allow a user to change wallets. The process will change the status to 'not onboarded' and burn MeID tokens. Process [Link](/how-to-section/demos-hemi-overview/how-to-burn-delete-enrollment)

Once <mark style="color:yellow;">\[Person 1]</mark> has cleaned up <mark style="background-color:orange;">\[Wallet 1]</mark>, the person can attempt to enroll in another \[Wallet 2], including a duplicate wallet.

<mark style="color:yellow;">**Important Note 1 :**</mark> If a person has cleaned up a wallet and continues to see the following error message, the system has detected an attempt from that person in the system on another wallet. Or the purge/delete process has not been completed.

"*<mark style="color:red;">Our records show that the biometrics associated with the connected wallet are already enrolled on a different wallet. If the biometrics have been deleted and you wish to switch wallets, a successful enrollment will clear the error message. However, if you have attempted to enroll on multiple wallets, there is a risk that the warning may not resolve</mark>*<mark style="color:red;">.</mark>"

<mark style="color:yellow;">**Important Note 2 :**</mark> If a person has decided to change wallets, the following points apply

a) To burn and delete an account the process can take up to 10 days (3 days + 7 Days)

b) While the burn and delete is in process a person is unable to enroll on another wallet as an account still exists in the system and will prompt errors.

c) After the 10 days errors on a conflicting wallet will not automatically disappear. If the process to delete an enrollment is complete, the person can return to another wallet which has duplicate warnings and and attempt to enroll again. On success, the errors will be removed. If there errors still exist, reference the above point <mark style="color:yellow;">**Important Note 1 :**</mark>&#x20;

### <mark style="color:yellow;">#3 RPC Errors</mark>&#x20;

If users experience RPC errors they will be typically related to the blockchain therefore out of the control of Demos.&#x20;

\ <mark style="color:purple;">**Recommend checking the following Hemi Network status also**</mark>\
<https://hemistatus.com/en>

<https://hemistatus.com/en/maintenance>

***

### <mark style="color:yellow;">#4 Request failed—TypeError’</mark>

These errors could be generated from a number of factors, for which Demos can only provide information to assist with the issue.&#x20;

<mark style="color:yellow;">A refresh of the browser page fixes under most circumstances.</mark>

Demos doesn't support client side issues.

* Poor internet connection
* The blockchain
* Browser configuration
* Wallet configuration.
* Repeatedly hitting (F5) refresh in their browser. This would result in a large number of requests being sent that are blocked due to security rate controls. I recommend using a different browser or attempting to use another time.<br>

<figure><img src="/files/RTDBhNMYLuTiuVo3lz1n" alt=""><figcaption></figcaption></figure>

#### <mark style="color:yellow;">Recommendations</mark>

<mark style="color:yellow;">if the above errors are experienced, please attempt the following</mark>

1\.      Hard refresh the browser page, click F5 or CTRL + F5.

2\.      Clear cookies and Cache in the browser

3\.      Try a different browser, Edge, Brave, Chrome

4\.      Open a browser in a private window, allow 1 wallet in the private window, no other extensions enabled.

5\.      [Confirm wallet is connected to the correct Blockchain ie Hemi](/how-to-section/demos-hemi-overview/how-to-connect-to-hemi-blockchain)

6\.      Try a VPN (Virtual Private Network)

7\.      Try a different hardware device, PC, or Mobile Phone.

### <mark style="color:yellow;">#5 My wallet has been hacked and requires to change wallets</mark>

If a person is unfortunate to have their wallet hacked, they will still have access to their wallet to purge their enrollment. The Instructions can be followed below

{% content-ref url="/pages/BDFX5A7o45y9UqES50Gi" %}
[How to burn/delete enrollment](/how-to-section/demos-hemi-overview/how-to-burn-delete-enrollment)
{% endcontent-ref %}

### <mark style="color:yellow;">#6 \[Wallet connection Errors]</mark>

&#x20;If people are experiencing issues connecting Metamask to the Demos website, we recommend using other supported wallets that can use 'Wallet Connect', Rabby, OKX, etc.; all are supported. Metamask deployed changes in December, which have affected its stability.

**We are not advising** users to create a new wallet address; they can import their private keys into other supported wallets and connect via ‘Wallet Connect’

## Common Questions

<mark style="color:yellow;">**Q1 : Why do I see a 'verify' option on the UI, I have a MEID token and enrolled.**</mark>

Response: *Verification is an option for continued confidence of wallet ownership for points and campaign validation. On success, a verify a small gas charged is required to provide an on-chain timestamp of the last verify timestamp.*\
*Please refer to the following article for additional information.*

<mark style="color:yellow;">**Q2 : Do I pay gas for a failed verify ?**</mark>

Response: Wallets are only charged a fee on a successful verify, which results in an on-chain timestamp and an update to the UI. The 'verify' option isn't available for wallets that don't have sufficient gas will will be displayed.<br>

{% file src="/files/vmSkvmTVkFxdac9euzCT" %}
Video Clip displaying low gas
{% endfile %}


# How to burn/delete enrollment

Details on how burn MEID token and delete enrollment (2 parts) including how to change wallets

### <mark style="color:yellow;">Steps to change/burn/delete your enrollment & MEID token</mark>

#### Change wallet timeline |  \[3 / 7 days]

* Burn MeID token | Token can be burned after <mark style="color:yellow;">**3 days**</mark> of minting, if token already 3 days old, token can be burned immediately&#x20;
* Delete Enrollment | After MeID token has been burned, the request to delete the account can be made. The process will count down over <mark style="color:yellow;">**7 days**</mark>. On 8th day the person must return to delete the enrollment as per the instructions below.

#### IMPORTANT NOTE: <mark style="color:green;">To follow the process of changing wallets, the wallet must have minted a MEID Token. If a person has just enrolled without minting a MEID token, the process can not be followed; therefore</mark>, <mark style="color:green;">minting a MEID is always required to change wallets.</mark>&#x20;

*In summary If enrolled but not minted, mint a MEID token, follow steps below <mark style="color:yellow;">noting a MEID token has to exist for at least 3 days before burning</mark>.*

Prior Checks: **Ensure the wallet has ETH available in wallet to burn MeID token**&#x20;

a) Go to url [https://app.demos.global/dashboard/hemi](https://app.demos.global/dashboard/hemitest)

b) Connect the wallet that was enrolled {Onboarded}&#x20;

<figure><img src="/files/s17AHV8Audp35BVNESCm" alt=""><figcaption><p>The following screenshot details the wallet is 'onboarded' and has a MeID token minted.</p></figcaption></figure>

c) Go to the ‘*<mark style="color:yellow;">**settings**</mark>*’ button and click on ‘*<mark style="color:yellow;">**Burn MeID**</mark>*’, where you will be prompted for a confirmation that you wish to delete your MeID Enrollment (step 1) . Click on ‘*<mark style="color:yellow;">**Yes, burn my token**</mark>*’. From here your wallet will prompt the person to sign a message authorising the transaction to burn enrollment.&#x20;

<mark style="color:yellow;">**‘settings’ will not appear unless a MeID token has been minted. \[Important to note, The MeID token needs to be older than 3 days to burn the token; therefore, if the age of the token is less than 3 days a timer will appear}**</mark>&#x20;

<figure><img src="/files/zA93ZJ7RBMqk4c2nihvQ" alt=""><figcaption><p>Click on 'Settings'</p></figcaption></figure>

<figure><img src="/files/hlSRqUerriYQSrKxeNfc" alt=""><figcaption><p>If a MeID has been minted 'Burn MeID' will appear</p></figcaption></figure>

d) If the wallet doesn’t have MeID tokens on other chains and deleting MeiD is successful, you will see an option to ‘*<mark style="color:yellow;">**Mint**</mark>*’ again. <mark style="color:purple;">**DO NOT MINT**</mark>**&#x20;again unless required.**&#x20;

e) To complete the next stages, click on ‘*<mark style="color:yellow;">**settings**</mark>*’ then ‘*<mark style="color:yellow;">**Purge MeID enrollment**</mark>*’; a prompt will ask for confirmation from there. To delete, choose ‘*<mark style="color:yellow;">**Deactivate account**</mark>*’&#x20;

<figure><img src="/files/3W2FdYQEEOm70gsXJwq9" alt=""><figcaption><p>Purge biometrics will only appear if MeID has been burnt</p></figcaption></figure>

f) <mark style="color:red;">**IMPORTANT**</mark>**:** A timeout will appear confirming the data is being deleted; return after a timeout to enroll a new person on the wallet. **If a wallet has been tagged as a duplicate, the error message will remain displayed until a successful enrollment has been completed.**\
\
If the connected wallet detects a duplicate enrollment in the system, the following message will be displayed: *<mark style="color:green;">**"Our records show that the biometrics associated with the connected wallet are already enrolled on a different wallet. If the biometrics have been deleted and you wish to switch wallets, a successful enrollment will clear the error message. However, if you have attempted to enroll on multiple wallets, there is a risk that the warning may not resolve."**</mark>*

<mark style="color:yellow;">IMPORTANT NOTE</mark>: <mark style="color:yellow;">Once the 7-day wallet enrollment timeout is over, the person can attempt to enroll in another wallet. If a wallet was tagged as a duplicate, if the person successfully enrolls in that wallet, the message will disappear. If the person has attempted to enroll in another wallet, the message will continue to display.</mark>


# Enrollment Status explained

Information detailing the status of an enrollment on Demos Website

### <mark style="color:purple;">Demos dApp URL</mark> [<mark style="color:purple;">https://app.demos.global/</mark>](https://app.demos.global/)

### <mark style="color:yellow;">\[1] STATUS | Not Enrolled \[Not Onboarded] | No MeID minted</mark>

The screenshot highlights the connected wallet is <mark style="color:yellow;">NOT</mark> enrolled {not onboarded} and has <mark style="color:yellow;">NOT</mark> minted a MeID token on Hemi Blockchain

<figure><img src="/files/IC1pnIRs0b1mA5E4tKiK" alt=""><figcaption></figcaption></figure>

### <mark style="color:yellow;">\[2] STATUS | Enrolled \[Onboarded] | Not Minted a MeID</mark>

Screenshot highlights the connected wallet is enrolled {onboarded} and <mark style="color:yellow;">NOT</mark> minted a MeID token on the Hemi Blockchain

<figure><img src="/files/97Ty9E5om7lYrcvgjsYJ" alt=""><figcaption></figcaption></figure>

### <mark style="color:yellow;">\[3] STATUS | Enrolled \[Onboarded] | Minted a MeID</mark>

Screenshot highlights the connected wallet is enrolled {onboarded} and has minted a MeID token on Hemi Blockchain

<figure><img src="/files/cWGwB8D1SyIQVK2xL8Lq" alt=""><figcaption></figcaption></figure>

### <mark style="color:yellow;">\[4] To check if the wallet has minted a MeID token</mark>

1. Connect wallet to the Website the [UI](https://app.demos.global/dashboard) will display status as above
2. Connect to the blockchain [explorer](https://testnet.explorer.hemi.xyz/) , enter wallet address, click on 'tokens' where 'OnlyMeID (MeID) will appear\ <img src="/files/QkkOU11DmYGklVsBWflB" alt="" data-size="original">

### <mark style="color:yellow;">\[5] Burn MeID / Delete Enrollment status</mark>

#### <mark style="color:yellow;">Burn MeID Option \[Settings</mark>]

The following will only appear if the wallet has a MeID token minted

<figure><img src="/files/3a8iYkElQ5jIR0jNLncJ" alt=""><figcaption><p>Burn MeID option under settings</p></figcaption></figure>

#### <mark style="color:yellow;">Purge biometrics / Enrollment</mark> <mark style="color:yellow;">\[Settings]</mark>

The following option will only display if the wallet the wallet hasn't a minted a MeID on any chain. For example, if a person has minted a MeID on Polygon and Hemi, the token will have to be burnt on both chains for the option to 'Purge MeID Enrollment'

<figure><img src="/files/TIECMkB9rJwxN2qcNSnK" alt=""><figcaption><p>Purge biometrics option under settings</p></figcaption></figure>

### <mark style="color:yellow;">\[6] Verify Option</mark>&#x20;

The 'Verify' option is not available on Hemi Testnet, the button will be active on Mainnet. On mainnet on occassion, there will be a requirement to revalidate ownership of the wallet by verifying.

<figure><img src="/files/5NvgfUDbXnwu2IFY3AfX" alt=""><figcaption><p>Available on all chains [Not Hemi Testnet]</p></figcaption></figure>

Please note that upon successful verification, an on-chain transaction will be initiated to finalize the verification timestamp. To complete this process, the wallet must have sufficient gas/tokens. If the on-chain transaction fails to complete, the verification will not be finalized, potentially resulting in non-validation of the campaign requirements.

An example of a successful on-chain verification, if the following is not displayed or doesn't have a recent date/time in the UI/Website the on-chain transaction hasn't completed successfully.

<figure><img src="/files/fbaXyxZ2sMkQLf3JewKI" alt=""><figcaption><p>Last verified timestamp</p></figcaption></figure>

### <mark style="color:yellow;">\[7] To change wallets, follow the procedure below</mark>

{% content-ref url="/pages/BDFX5A7o45y9UqES50Gi" %}
[How to burn/delete enrollment](/how-to-section/demos-hemi-overview/how-to-burn-delete-enrollment)
{% endcontent-ref %}


# Mint / Verify FAQ

Details on Mint and verify questions

## Costs

Costs are approximate and not pegged to USD; costs will be closely calculated on the following.

Mint cost: <mark style="color:yellow;">$4 \*\*</mark>

Verify Cost: <mark style="color:yellow;">$2 \*\*</mark>

\*\* <mark style="color:orange;">**Costs will fluctuate based on the cost of token**</mark>

### <mark style="color:yellow;">Viewing  verify cost in UI</mark>

Hover over the 'Verify' button to view the on-chain cost

<figure><img src="/files/6q1lPZhOI8dJslcMOjax" alt=""><figcaption><p>View 'Fee'</p></figcaption></figure>

### <mark style="color:red;">Important Note : The wallet needs to have sufficient gas for a verify to start, a warning message will display if there isn't. Please update balance of wallet.</mark>

### ![](/files/ym6A0LteOvsyDpHol9zm)&#x20;

### <mark style="color:yellow;">On-chain Verify process</mark>

On a successful face verify, a prompt will request an on-chain transaction at a cost to timestamp it. On success, the UI will display the latest timestamp, which confirms a successful on-chain transaction.

Example of a successful on-chain verification\ <img src="/files/hhHgrLEXnx3E9vUZlcWW" alt="" data-size="original"><br>


# ✨Hiring @ Demos✨

👉 DEMOS NEEDS YOU 👈

## Introduction

As Demos Global scales, team expertise and skill set will play a significant part in the success. Therefore, we welcome offers of assistance to get Demos where it needs to be sooner. We have decades of experience within the company in many areas that require additional resourcing on a part-time basis, where skills can be shared both ways.

We encourage you to reach out and let us know how you could fit into the team to leverage your skill set.

❗️<mark style="color:yellow;">IMPORTANT INFORMATION</mark>

·         Competitive pay rates to be discussed with the team

\-          Current CV / Resume required

\-          Highlight relevant experience for roles advertised

\-          Link to Github or Portfolio Site

\-          Link to LinkedIn and/or Twitter

\-          Onchain reputation score (Debank, DegenScore, or Nomis) on **OnlyMeID Authenticated** wallet

\-         <mark style="color:yellow;">Answers to these questions:</mark>

1\) Why are you the best candidate to join Demos Global Team?

&#x20;2\) Are you currently working on other projects ?

3\) Details of any work or companies where you have provided your expertise.

Important a CV or Resume is sent through if you are seriously considering a role.

Email <seek@demos.global> with resume/CV

<br>


# 📝Social Liaison Content Manager

Role: Social Liaison Content Manager

## Management of Social Content Calendar

### <mark style="color:yellow;">Roles & Responsibilities</mark>&#x20;

* Coordinate approvals & Reviews of content.
* Schedule and confirm dates.
* Prestage content in Demos Content Calendar for review

1. Schedule Tweets and Blog posts from the content calendar
2. Request creation of graphics/media requests through ClickUp
3. Post Tweet links to internal social media channels internally after posting
4. Assemble/create short-form content ideas for blogs and posts

<mark style="color:yellow;">SKILLS:</mark>

1. Good Communication and coordination skills.
2. Basic documentation creation.
3. Grammarly Application.
4. Using and posting to social channels, Twitter, Discord & Telegram.
5. Utilizing Google Docs / Sheets.

Nice to have&#x20;

* Using Slack Application
* Using Clickup Application


# 📡Business Development Associate

Role: Business Development Associate

## Engagement & Relationship Management of Partner Integrations

### <mark style="color:yellow;">Roles & Responsibilities</mark>&#x20;

1. Scout and Initiate Conversations with relevant Projects to integrate OnlyMeID
2. Manage Conversations towards integration
3. Coordinate with DEMOS team on integration go live efforts (GTM marketing, DevRel, etc.)
4. Support creation and iteration of auxiliary BizDev materials (one pagers, dev docs, etc.)
5. Engage with relevant communities generally to drive Demos & OnlyMeID reach

<mark style="color:yellow;">SKILLS:</mark>

1. Strong Crypto Background/Understanding
2. Social/Messaging platforms - Twitter, Telegram, Discord
3. Business Development, Relationship Management, or Sales Background
4. Written and Verbal Business Communications

Nice to have&#x20;

* Using Slack Application
* Using Clickup Application
* Familiarity with Warpcast/Farcaster


# ⚙️Applications/Frontend/Software (non-solidity)

Role for Front End Developers

<mark style="color:yellow;">SKILLS:</mark>

1. architecture/strategies
2. Web development
3. Architect expertise
4. Continuous integration/deployment
5. Github / Actions / build / Deploy / CI
6. Cloudflare
7. AWS / EC2 / Load balancers /
8. Experience with smart contracts & solidity would be a welcome addition.

&#x20;

### <mark style="color:yellow;">Specific Skills:</mark>

#### a) overlapping:

• javascript

• https calls (restful apis etc…)

• testing + environments \[web3]

&#x20;

#### b) frontend:

• html (bones)

• css/scss/sass (design)

• react.js

• web3.js

• typescript

&#x20;

#### c) backend optional , nice to have:

* node.js (optional)
* &#x20;webhooks + apis
* &#x20;virtual machines + server + nginx
* &#x20;linux commands/jobs
* &#x20;AWS Lambda
* &#x20;AWS API Gateway
* &#x20;AWS S3
* AWS EC2
* MySQL
* API/Rest
* Infura

### <mark style="color:yellow;">General Requirements:</mark>

a) Cosmetic React updates: Change a text or some logic; no major changes. Simple React: mostly HTML/CSS, some testing, and Web3…

b) Continuously updating GitHub repo with standard files/components. Advanced react, understanding components, lifecycles, github, webhooks, web3

d) Track all work in Clickup to align with a scrum methodology.

e) Coordinating with teams across time zones with an understanding of deliverables and expectations.

&#x20;

#### 2) project based:

1. Understanding the requirements of the project. Planning and working to a schedule and critical path.
2. Creating, maintaining & deploying a react app
3. Fetching/handling data from various sources/requests (versatility required)
4. Being comfortable with web3 calls and how “it” works
5. Realising the importance of test envs and creating the environments accordingly
6. Insight in the deployment process. Understanding how the scripts are executed and why they are executed in this way…


# 🔩Full Stack Developer

Full Stack Developer requires for part time capacity

## Job Brief

Limited capacity is available for a skilled Full Stack Developer to assist with the Demos buildout as we evolve.

You will be part of a cross-functional team responsible for the full software development life cycle, from conception to deployment.

As a Full-Stack Developer, you would be comfortable with both front-end and back-end coding languages, development frameworks, and third-party libraries.

Also, hoping for a team player with expertise in visual design and utility.

&#x20;

### Responsibilities

* Work with the development team to assist with building out requirements
* Design client-side and server-side architecture
* Build the front-end of applications through appealing visual design
* Assist with & develop and manage well-functioning databases and applications
* Support and Write effective APIs
* Test software to ensure responsiveness and efficiency
* Troubleshoot, debug and upgrade software
* Create security and data protection settings
* Build features and applications with a mobile responsive design
* Write technical documentation when required.

&#x20;

### Qualifications

* Proven experience as a Full Stack Developer or similar role
* Experience developing desktop and mobile applications
* Familiarity with common stacks
* Knowledge of multiple front-end languages and libraries (e.g. HTML/ CSS, JavaScript, XML, jQuery)
* Knowledge of multiple back-end languages (e.g. C#, Java, Python) and JavaScript frameworks (e.g. Angular, React, Node.js)
* Familiarity with databases (e.g. MySQL, MongoDB), web servers (e.g. Apache) and UI/UX design
* &#x20;AWS Lambda,  AWS API Gateway,  AWS S3, AWS EC2
* Excellent communication and teamwork skills
* Great attention to detail
* Organizational skills
* An analytical mind