# Verifiable SBT on Sui

## TBook vSBT on Sui — Partner Brief

### What is vSBT?

**vSBT (verifiable Soulbound Token)** is a non-transferable, verifiable proof of identity and contribution issued by **@**[**realtbook**](https://x.com/realtbook) on **Sui**. Each vSBT permanently binds a real action—learning, building, participating, yield farming, token holding, helping—to the holder’s Sui address and becomes a reusable **signal for access and rewards** (gating, allowlists, weighting, quotas, leaderboards).

**Key properties**

* **Non-transferable**: eliminates reselling/farming and captures *real* participation.
* **Collection-based**: organize by program, release, or campaign; easy to manage and re-use.
* **Signed issuance**: off-chain authorization + on-chain verification prevents forgery/replay.
* **Operational controls**: pause, role separation, and key rotation for safe growth.

***

### Why Sui

* **Object-centric model**: vSBTs are first-class, non-transferable objects—simple to query and compose.
* **Throughput & cost**: ideal for high-volume campaigns, achievements, and community activations.
* **Move capabilities**: crisp permission boundaries; secure and auditable.
* **Ecosystem fit**: vSBTs form a shared **proof layer** that Sui dApps can plug into for access, points, airdrops, and retention.

> **Our shared value:** Sui and @[realtbook](https://x.com/realtbook) both put **community first**. vSBTs are designed to **recognize, reward, and amplify** the people who *show up*—builders, learners, testers, volunteers. We believe identity is *earned* through contribution, and every earned proof should stay useful across the entire ecosystem.

***

### Use Cases (growth & retention, community-first)

1. **Finding your true core users**
   * Tiered vSBTs (Tier 1/2/3) by effort, streak, quality of contribution.
   * Filters out sybil/farm behavior with one-per-address, non-transferable proofs.
   * Re-use for: priority allowlists, closed betas, early-bird channels, governance weighting.
2. **Fairdrop & weighted access**
   * “Holds vSBT X?” becomes a plug-and-play gate or weight—no spreadsheets, minimal manual review.
   * Consolidate multi-source effort (courses, hackathons, quests, IRL check-ins) into one consistent eligibility signal.
3. **Education & developer growth**
   * Issue vSBTs for course completions, PRs, approved demos; build a durable dev reputation over time.
   * Use vSBT trails to support grants, beta access, mentoring, and team matching.
4. **Community roles & rights**
   * KOL/mod/volunteer badges; connect to Discord/Telegram for role-based unlocks.
   * Proof-of-participation (PoP) with time windows / IRL confirmations for re-engagement.
5. **Game-style achievements & loyalty**
   * Milestones like First Launch, Power User, Bug Hunter, Top Referrer.
   * Loop: achievement → benefits → deeper participation → new achievement.
6. **Testnet & Mainnet launch**
   * **Testnet Dry-Run**: “Testnet Genesis vSBT” for early testers (first interactions, feedback, join dev group).
   * **Mainnet Genesis / Early Adopter vSBT**: binds first-day participation and early support to lasting access and weighting.
   * **Bridged incentives**: map Testnet vSBT → Mainnet vSBT so test-phase effort translates into mainnet advantages.

***

### Case Study A — Native: Structured testnet→mainnet tiers & fair distribution

**Context**: Native targets BTCFi on Sui, bringing Bitcoin liquidity into DeFi with minimized trust.\
**Goals**:

* Identify high-intent early users in testnet and mark them with verifiable tiers.
* Prepare mainnet with allowlists and fair weighting based on *earned* participation.\
  **Approach with @**[**realtbook**](https://x.com/realtbook) **vSBT**:
* Multiple **Sui-native vSBTs** for layered depth: *Believer* → *Testnet Seeker* → *Testnet Adventurer*.
* Users complete tasks; backend authorizes; users mint an immutable proof.
* vSBTs then power mainnet allowlists, quota boosts, and private testing access.\
  **Outcome**: Converts “interest → trial → depth” into **verifiable cohorts** that can be recalled, rewarded, and re-used across partners—cutting noise and improving fairness.

***

### Case Study B — Talus: Turning event participation into reusable launch assets

**Context**: Talus builds decentralized AI-agent/forecasting infra with deep ties to Sui.\
**Goals**:

* Turn attendance and engagement at *Talus Thursday / Testnet Launch* into on-chain credentials.
* Establish a reusable **Genesis/Early Adopter** group for future releases.\
  **Approach with @**[**realtbook**](https://x.com/realtbook) **vSBT**:
* “Talus Testnet Launch vSBT” issued to eligible attendees/participants.
* One-click claim flow converts online/IRL behavior into an immutable proof on Sui.\
  **Outcome**: Event effort becomes **mainnet-ready capital**—reusable for allowlists, weighted airdrops, higher quotas, and priority testing—lowering acquisition and risk every subsequent launch.

***

### Helping developers **find and keep** their most valuable community members

* **Verifiable**: real contribution becomes a durable on-chain credential; noise gets filtered.
* **Composable**: the *same* vSBT can gate multiple partner dApps, creating **ecosystem-level reputation**.
* **Actionable**: target holders with upgrades, priority lanes, and quota boosts—turning one-off campaigns into **ongoing community operations**.

***

### Sui ecosystem developer benefits

* **Free access to TBook Nexus Portal**: one-click to create collections, set rules, and issue vSBTs on **Sui**.
* **Visibility to the right audience**: your vSBTs appear in **@**[**realtbook**](https://x.com/realtbook) community surfaces frequented by builders and power users.
* **Community co-creation**: standout vSBTs can be **featured in Engagement Basecamp** for extra exposure and seed users.
* **Ecosystem integrations**: plug into task platforms, allowlist systems, points/leaderboards, and more.

> **CTA:** Go here → [**https://sui.tbook.com/**](https://sui.tbook.com/) — if you have a Sui address, you can use **Sui-native SBTs** to resonate with your community today.

***

#### Our shared ethos

We believe **community is the protocol**: identity should be *earned*, transparent, and reusable—so the people who build, test, teach, moderate, and support are **seen** and **rewarded**. Sui’s performance and developer-first design meet @[realtbook’s](https://x.com/realtbook) contribution-proof rails to create a growth loop that is fair, composable, and proudly community-led.