Open the app, claim your Web3 name, and build a portable proof that you’re a real person. xstar guides you to connect wallets across chains, then add proof types you’re comfortable sharing—ID checks, mobile number, social profiles, or peer attestations. Each proof contributes with its own weight to a single human trust index pinned to your name. If you choose face presence, record a short video; XSTAR converts it into a de‑identified 3D mesh and asks you to follow micro‑prompts to confirm live presence in real time. You control what is visible on your public name record versus what stays private while still counting toward your score. When satisfied, publish your profile so apps can reference your current index without exposing raw personal data.
Use your profile anywhere you connect a wallet. Share a single link or attach your XSTAR reference to your name record so dApps can read your score on demand. When an app requests access, you approve which proof bundle to share; the app compares it to a threshold (for example, “score ≥ 70 with fresh liveness”) and instantly unlocks mints, allowlists, or chat access. Set reminders to refresh time‑sensitive proofs; your index decays gracefully if signals get stale, and you can re‑run liveness in under a minute. Manage multiple personas under one account, each with different visibility rules. If something looks off, pause sharing with one tap, review recent verification events, and request a re‑check. more
Organizers and community leads can design fair entry rules without doxxing members. Create tiers like “view‑only,” “post,” and “moderate,” each mapped to minimum scores and proof freshness. Weight recent liveness more for high‑risk actions (claiming tickets, big airdrops) and accept social attestations for low‑risk spaces (open forums, interest groups). DAOs can curb Sybil attacks by combining token voting with a human index multiplier, or cap influence from accounts that fail freshness checks. Creators can display a “unique human” badge on profiles, reduce farmed collab requests, and filter campaign invites. Marketplaces can require a baseline index for high‑value listings to deter churn from bot accounts.
Developers can integrate in a few steps. Use the SDK to request a user’s signed index by name or wallet, verify the signature server‑side, and enforce thresholds before mint, claim, or post actions. For on‑chain flows, reference the attested score via a resolver or oracle; for off‑chain, subscribe to webhooks when a user’s score or freshness changes to keep caches current. Follow recommended policies: set minimums by risk, require recent liveness for sensitive benefits, and avoid single‑proof lock‑ins by accepting multiple equivalent bundles. Start in sandbox with test identities, simulate attack patterns (multi‑wallet farms, stale proofs), and tune thresholds before launch. Ship with clear prompts in your UI so users know exactly which proofs you’re asking for and why.
Comments