zkPass 백서

zkPass

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 13쪽 중 1쪽

# Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation This site has an agentic ask interface you may use to query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zkpass.org/index.md?ask=<question>&goal=<user_goal> ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. --- # Get Started ## Welcome to the zkPass Documentation Library #### New Here? Start with [What is zkPass](https://medium.com/zkpass/reintroducing-zkpass-an-identity-infrastructure-for-the-decentralized-society-based-on-mpc-zkp-4023683c718e) <table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td></td><td><strong><code>Introduction</code></strong></td><td>Overview of the fundamental principles, and methodologies of zkPass.</td><td><a href="/overview/introduction">Introduction</a></td><td></td></tr><tr><td></td><td><strong><code>Use Cases</code></strong></td><td>Potential use cases that can be built on top of zkPass.</td><td><a href="/overview/use-cases">Use Cases</a></td><td></td></tr><tr><td></td><td><strong><code>User Guides</code></strong></td><td>General instructions for users to attest anything on zkPass ecosystem apps.</td><td><a href="/user-guidelines">User Guidelines</a></td><td></td></tr><tr><td></td><td><strong><code>Developer Guides</code></strong></td><td>A comprehensive tutorial for developers on how to leverage zkPass tech.</td><td><a href="/developer-guides/js-sdk/quick-start">Quick Start</a></td><td></td></tr></tbody></table> *This page is currently undergoing updates. If you need assistance with any missing information, please reach out to us via <info@zkpass.org> or*[ *join our community*](https://discord.gg/zkpass)*.* # User Guidelines To ensure a smooth and secure experience when using applications integrated with the zkPass TransGate-SDK, please refer to the following platform-specific instructions and recommendations. ## 🖥️ Desktop (Windows / macOS) **Recommended Setup:** * **Browser**: Latest version of **Google Chrome** or **Brave** * **Wallet**: [MetaMask](https://metamask.io/download/) browser extension (ensure it is installed, unlocked, and connected) ::: warning When you’re setting up a wallet, be sure to: ✅ Download and install only the latest version from their official source. ✅ Back up and keep your recovery phrases safe. ❌ Never share your recovery phrases with anyone, under any circumstances. ::: **Usage Instructions:** **Option1: Install the** [**TransGate**](https://chrome.google.com/webstore/detail/zkpass-transgate/afkoofjocpbclhnldmmaphappihehpma?utm_source=ext_sidebar\&hl) **on Google Extension Store** ::: warning Please kindly note that **DON’T** install any **Transgate Extensions** obtained from third-party channels. This measure ensures that all installed extensions have undergone proper vetting and are up to our standards. Stick to [**official link** ](https://chrome.google.com/webstore/detail/zkpass-transgate/afkoofjocpbclhnldmmaphappihehpma?utm_source=ext_sidebar\&hl)and protect your personal accounts securely. ::: <figure><img src="https://2216484837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC2Jh1oquOpJPfwzD3x9L%2Fuploads%2FMy0lPRNcRnrAb1weFafY%2Fimage.png?alt=media&amp;token=4d6ac59a-52d3-4e91-b612-1f22d9455b87" alt=""><figcaption></figcaption></figure> ::: tip **IMPORTANT!** Please refrain from installing extensions from third-party sources. We cannot take responsibility for any problems that may occur as a result of installing such extensions. Stick to zkPass official link and trusted sources for a secure browsing experience. ::: 1. Open the application link in your browser. 2. When prompted, approve the wallet connection via MetaMask. 3. Grant permissions for pop-ups and cross-site cookies (if disabled, verification flow may be blocked). 4. Log in the data source like usual, zkPass verification will run in-browser; please **do not close the tab** during the process. ::: warning **Notes:** * **Ad blockers or privacy extensions** may interfere with wallet communication. Disable them temporarily if issues occur. * Refresh the page if any UI components fail to load after connecting. ::: **Option2: Scan the QR Code and finish the process on mobile. 👇** ## 📱 iOS (iPhone) **✅ Instant Access via App Clip (No App Installation Required)** zkPass SDK is fully supported through Apple’s **App Clip** experience, offering a seamless and secure verification process with no installation needed. **Instructions:** 1. Open the zkPass-integrated dApp link in **Safari** or scan the associated **QR code**. 2. An App Clip card will appear — tap **“Open”** to launch the zkPass verification flow. 3. You will be guided through wallet connection and data verification within the App Clip environment. 4. Complete the process and return to the main dApp. No persistent app or background services will remain. **Requirements:** * iOS 14.3 or later * Safari or camera access (for QR codes) * Ensure App Clips are enabled under iOS Settings → App Clips ::: warning **Notes:** * Wallet connection will be handled in-session. MetaMask or WalletConnect will be triggered as needed. * All processes are sandboxed and privacy-preserving per Apple’s App Clip policies. ::: ## 📱 Android Devices Required: Install [TransGate App](https://play.google.com/store/search?q=transgate\&c=apps) from Google Play Store On Android, zkPass SDK operates via a native client—**TransGate**—to ensure secure communication and proof generation. **✅ Recommended Method: Chrome Browser + MetaMask Mobile App** 1. Open the application link in Chrome or another Chromium-based browser. 2. Upon wallet connection request, select **MetaMask** or via WalletConnect. 3. Approve all requests in MetaMask and return to the original browser tab to complete verification. **⚠️ MetaMask In-App Browser (Android):** * Due to system-level restrictions, MetaMask’s in-app browser **does not fully support dApp redirects** or advanced authentication features. * Use a standalone browser for better stability. ::: warning **The TransGate Android app currently supports Android 12 and above.**\ If your device isn’t compatible, using the Mise + TransGate extension is the recommended alternative below: ::: 1. **Open Mise Browser**\ Download Mise from <https://mise.xyz> if you haven't already. 2. **Go to the Extension Page**\ Open this link in Mise:\ 👉 [TransGate on Chrome Web Store](https://chromewebstore.google.com/detail/zkpass-transgate/afkoofjocpbclhnldmmaphappihehpma) 3. **Click "Add to Chrome"**\ Confirm the prompt and wait for the installation to finish. 4. **Verify Installation**\ After installation, you should see the TransGate icon in the top-right corner of your browser. Visit any zkPass-supported page to start using it. ::: danger ***Important Reminder:*** to ensure the efficient use of computational and gas resources, it is advisable not to use multiple addresses to attest the same schema with the same account. Doing so will overwrite previous attestations, resulting in unnecessary resource consumption without yielding additional rewards. ::: # VRS Verifiable Reputation Score (VRS): A Coverage-Penalized Multi-Source Reputation Scoring Framework ### Purpose & Vision The **Verifiable Reputation Score (VRS)** was first introduced as a proof-based mechanism to recognize authenticity, contribution, and engagement across the zkPass ecosystem.\ It quantifies how complete and credible your digital identity is across multiple verified data sources, while preserving privacy through zero-knowledge proofs.\ Higher scores grant greater access and priority in ecosystem participation, ensuring that credibility and genuine contribution are rewarded alongside timing. ### Quick Start Access the VRS module at [portal.zkpass.org](https://portal.zkpass.org/), where users can connect wallets, verify data sources, and view their computed Verifiable Reputation Score in real time. #### **What you get** A personal VRS ranging from 0 to 100 determines your $ZKP allocation priority on Kaito Capital Launchpad. Users with higher scores receive preferential access to allocations under the campaign rules. #### What you need 1. A wallet such as [MetaMask](https://metamask.io/download/). 2. TransGate on your device.\ • Desktop Chrome installs the [TransGate extension](https://chrome.google.com/webstore/detail/zkpass-transgate/afkoofjocpbclhnldmmaphappihehpma?utm_source=ext_sidebar\&hl).\ • iOS uses TransGate via app-clip. **No need to download any apps.**\ • Android installs the [TransGate app](https://play.google.com/store/search?q=transgate\&c=apps) from Google Play. 3. A few eligible accounts to verify such as Binance, LinkedIn, GitHub, Duolingo, or Kaito Yap. **We recommend using the desktop web version for the smoothest experience.** #### How to verify on desktop web 1. Install the[ TransGate Chrome extension](https://chrome.google.com/webstore/detail/zkpass-transgate/afkoofjocpbclhnldmmaphappihehpma?utm_source=ext_sidebar\&hl). 2. Open the [zkPass Portal page](https://portal.zkpass.org/). 3. Connect your X account → Pick a source and select Verify → A new tab opens the source site → Sign in as usual. 4. Click Start in the popup, a zero-knowledge proof generates locally within seconds. Your VRS updates automatically. No gas fee is required. #### How to verify on mobile iOS 1. Open the [zkPass Portal page](https://portal.zkpass.org/) in the in-app browser flow. 2. Connect your X account and sign in to each source when prompted and tap Start. 3. Return to see the Verified status and updated VRS. Android 1. Install TransGate from [Google Play.](https://play.google.com/store/apps/details?id=com.zkpass.transgate\&hl=en\&pli=1) 2. Open the [zkPass Portal page](https://portal.zkpass.org/) in any wallet. 3. Connect your X account, sign in to a source, tap Start, then return to view the updated VRS. ::: tip #### Privacy and security Proofs are generated locally. Raw personal data does not leave your device. Verifiers receive only cryptographic attestations. ::: ### **Core Principal** VRS isn’t about popularity, wealth, or social ranking.\ It’s about **proof density** - how many aspects of your digital footprint have been independently verified, and how consistent they are. * A single Binance KYC attestation may prove you’re a real person. * A LinkedIn or GitHub profile shows professional authenticity. * A Duolingo streak or Kaito YAP credential reflects learning or contribution. Together, these form your **verifiable identity fabric**.\ The more complete and trustworthy that fabric becomes, the higher your VRS. #### **Conceptual Design** The VRS is derived from zkPass’s open-source *Coverage-Penalized Multi-Source Reputation Framework*, designed to fairly evaluate users based on both **what they’ve proven** and **what they’ve yet to prove**. It consists of five layers: | Layer | Purpose | What It Does | | ---------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Feature Normalization | Handle raw metrics (e.g., followers, balances, account age) | <p>Map heterogeneous data to 0–1 range using log scale, SoftClip, and Boolean mapping</p><p>A Coverage-Penalized Multi-Sour…</p> | | Per-Source Aggregation | Combine features within one source | Weighted sum based on feature importance | | Cross-Source Weighting | Aggregate scores from multiple sources | Assign global weights (e.g., KYC > Social) without re-normalizing missing sources | | Weighted Coverage | Compute how complete your proofs are | Evaluate coverage ratio across all expected sources | | Nonlinear Penalty | Apply soft discount for missing data | Use exponent α > 1 to intensify incompleteness penalty | #### **Mathematical Formulation** Let ***S***&#x69;​ be the score of source i, and ***W***&#x69;​ its global weight.\ Let ***A*** be the set of sources a user has verified. $$ (1) Raw Aggregation:Rraw=∑i∈AWiSi $$ $$ (2) Coverage Ratio:C=∑i∈AWi∑iWi $$ $$ (3) Final Score with Penalty:VRS=100×Rraw×Cα $$ Where α>1 controls how aggressively incomplete coverage reduces your score.\ Example: with C=0.8,α=1.5, only 83.7 % of the value is retained #### **Score Interpretation** | Score | Meaning | Typical Profile | | ------ | ------------------------- | -------------------------------------- | | 0–30 | Limited Proof | Only 1–2 basic verifications | | 30–60 | Partial Identity | Some key proofs (KYC + social account) | | 60–80 | Verified User | Multiple dimensions covered | | 80–90 | High Credibility | Strong proofs with minor gaps | | 90–100 | Fully Verifiable Identity | Complete and consistent proof set | #### **Examples** <table><thead><tr><th width="432.51953125">Connected Proofs</th><th>Coverage Ratio C</th><th>Approx. VRS</th></tr></thead><tbody><tr><td>Twitter + Duolingo</td><td>0.4</td><td>≈ 45</td></tr><tr><td>Binance KYC + LinkedIn</td><td>0.6</td><td>≈ 70</td></tr><tr><td>Binance + OKX + LinkedIn + GitHub</td><td>0.8</td><td>≈ 85</td></tr><tr><td>Binance + OKX + LinkedIn + GitHub + Duolingo</td><td>1.0</td><td>≈ 95–100</td></tr></tbody></table> #### **Properties** * **Boundedness:** All scores strictly within \[0, 100]. * **Monotonicity:** Adding new proofs or improving quality never lowers VRS. * **Weighted Fairness:** High-impact sources (KYC, verified identity) carry greater influence. * **Coverage Sensitivity:** Missing major sources penalized more than minor ones. * **Nonlinear Incentivization:** Penalty strength tuned by α to motivate completeness. * **Interpretability:** Every layer (feature → source → aggregate → coverage) is auditable. * **Extensibility:** Supports temporal decay, confidence weighting, or residual mixing without breaking consistency. #### **How to Increase Your VRS** 1. **Connect More Core Proofs** - Verify across financial, social, and skill dimensions. 2. **Maintain Account Quality** - Older, active, verified accounts score higher. 3. **Diversify Your Sources** - Cover both Web2 and Web3 identities. 4. **Stay Consistent** - VRS updates as your proof ecosystem evolves. #### Algorithmic Implementation (Pseudocode) ```python def compute_vrs(sources, alpha=1.5): """ sources: list of dicts with fields {weight, score, provided} """ total_weight = sum(s["weight"] for s in sources) provided = [s for s in sources if s["provided"]] coverage = sum(s["weight"] for s in provided) / total_weight quality = sum(s["weight"] * s["score"] for s in provided) vrs = 100 * quality * (coverage ** alpha) return round(vrs, 2) ``` #### **Open Framework & Future Extensions** The VRS framework is open for developers and projects to integrate.\ Future modules may include: * **Temporal Decay:** recent proofs weighted higher. * **Confidence Scores:** sources with cryptographic attestations weighted more. * **Federated Aggregation:** cross-domain proof composition without data sharing. By aligning economic incentives with verifiable identity strength, VRS lays the foundation for the **Proof Economy** - where reputation becomes a liquid, portable, and provable asset. #### Open Access & Disclaimer The Verifiable Reputation Score (VRS) framework is open and transparent by design.\ All algorithms, weight parameters, and pseudocode are publicly auditable and available for developers to reference or extend.\ The open-source implementation is maintained on GitHub:\ 👉 <https://github.com/zkPassOfficial/Verifiable-Reputation-Score> ::: tip All calculations are performed client-side; no personal or raw data leaves the user’s device.\ zkPass does not store, collect, or process any private information related to VRS computation.\ The framework is intended for informational and research purposes and should not be interpreted as a financial or investment rating. ::: # Introduction What is zkPass and what makes it stand out ### What is zkPass zkPass is a decentralized oracle protocol that transforms private internet data into verifiable proofs on-chain. Built on **zkTLS** — a novel integration of 3P-TLS and Hybrid-ZK cryptography — zkPass enables users and applications to prove facts derived from any HTTPS website without requiring OAuth, API keys, or trusted intermediaries. Through zkPass, individuals can selectively prove attributes across a wide range of data domains, including: * **Legal identity** (passport, driver’s license, national ID) * **Financial records** (account balances, transaction history, credit scores) * **Healthcare information** (medical records, prescriptions, genetic data) * **Social and behavioral data** (social media accounts, activity proofs) * **Professional and educational background** (employment history, diplomas, certifications) * **Digital activity and assets** (gaming accounts, loyalty programs, real-world assets) All proofs are generated locally in the user’s browser or device, ensuring that raw personal data is never exposed or transmitted. These verifiable proofs can be integrated into a broad spectrum of use cases spanning **AI, DePIN, digital identity (DID), DeFi lending, governance, compliance, and beyond**. ### Why zkPass zkPass introduces a new verification paradigm that addresses the limitations of existing identity and data solutions: 1. **Privacy-Preserving**\ Sensitive user data never leaves the device. Proofs reveal only the attributes required for verification. 2. **Verifiable Integrity**\ zkTLS extends the standard TLS protocol into a three-party model, ensuring the provenance and authenticity of private data. 3. **Universal Compatibility**\ Works with any HTTPS website, without requiring OAuth APIs, commercial licenses, or custom integrations. 4. **Anti-Cheating**\ Template-based verification ensures that client requests and server responses cannot be manipulated. Users cannot falsify achievements or credentials. 5. **Efficient Proof Generation**\ Powered by the **VOLE-in-the-Head (VOLEitH)** algorithm, zkPass enables millisecond-level proof generation directly on local devices, producing proofs that remain publicly verifiable. 6. **Trustless Attestations**\ Decentralized MPC nodes verify data integrity before a proof is accepted, guaranteeing that zkSBTs and attestations cannot be forged. ### Public vs. Private Data zkPass is designed to bridge the gap between **publicly accessible information** and **private, user-controlled data**: * **Public Data**: Information already open and accessible, such as census statistics, weather data, or government-published records. While useful for transparency, this data typically lacks individual-level granularity and is not privacy-sensitive. * **Private Data**: Personally identifiable or sensitive information that belongs to individuals or organizations, such as identity documents, ba
프로젝트로 돌아가기