Social Layer X

Social Layer (X/Twitter) + On-chain Proof (Blockchain)

We transform on-chain events into social content that anyone can independently verify.

• Every hero craft, item acquisition, and quest completion is recorded by smart contracts as an event.

• These events flow into our index (e.g., Postgres) via ingestion from blockchain RPC/event APIs.

• From the index, we generate hero/item cards (PNG/WEBP) as a clean “showcase” of results.

• Each card and post contains a Proof Capsule: chain/network, contract/app ID, hero/item ID, transaction hash, block/ledger reference + timestamp, event type, recipe/build hash.

• Every post includes a proof link where anyone can click and verify the transaction and event details on a public explorer / verification page.

Result: discussions on X become conversations about verifiable artifacts, not untrusted screenshots.

---

Managed discussions through quest threads

To avoid chaos, every quest has an official launch thread — a single aggregation point.

• Players publish builds and strategies as replies inside the specific quest thread.

• Posting happens only via an explicit Share button in the game — no auto-spam.

---

Publishing and content delivery

Posting is handled through a Share API + queue + worker so the game stays responsive.

• The worker uploads the card via chunked media upload and publishes a tweet/reply via the X API.

• We maintain a quest_threads table (anchor_tweet_id, last_post_id) so the reply chain stays correct.

• We maintain share_jobs with an idempotency_key to prevent duplicates during retries/webhooks.

---

Official digests and growth events

The official account doesn’t “invent numbers” — it publishes digests built from on-chain facts.

• Daily/Weekly Digest highlights top heroes, top completions, rare recipes, and “first discoveries” by block/time.

• Each digest entry includes a card + proof link so everything is verifiable.

• Milestone posts are generated from network facts: 1k crafted heroes, 10k completions, rare recipe discovered.

This creates regular information moments without marketing fiction.

---

Security and anti-spam by default

• User X tokens are stored in a vault/secret-store; automation tooling doesn’t get direct access to them.

• Automation is used for official campaigns (launch, digest, milestones) via cron/webhooks.

• Posting is protected with rate limits and backoff on 429 so it doesn’t look like coordinated spam.

• An audit log tracks the full chain: ingest → render → upload → tweet → saved IDs.

---

Why this works with blockchain proofs

Blockchain here is a provability layer for every public claim:

• “I crafted hero X” is confirmed by the transaction hash + Crafted event.

• “I completed quest Y” is confirmed by QuestCompleted event.

• “This build is top of the week” is confirmed by aggregating on-chain events for the period.

Strategy discussions become practical: builds can be verified and reproduced.

---

Ecosystem impact

• Creators get a durable showcase of discoveries and builds, not one-off posts.

• Players are motivated to share because progress is publicly verifiable.

• The community sees honest dynamics: growth, rarities, records — all from facts.

• Scalable: thousands of players generate UGC, while aggregation stays structured (quest threads).

• Safe: replies happen only via explicit user action.

• Reliable: queue + idempotency prevent duplicates and failures.

• Transparent: the proof page enables verification without trusting our server.

In the end, X becomes the social layer for quests, and blockchain becomes the proof layer for progress — enabling organic distribution through players’ accounts while keeping every build a verifiable artifact.

Verifiable UGC and discussions around on-chain progress

Core idea

We connect gameplay progress and social distribution so that public posts reflect real on-chain facts, while discussions remain structured and manageable.

Events on Stellar / Soroban (hero creation, item crafting, quest completion) become:

• verifiable UGC artifacts (a hero/item card + a compact proof),

• collected discussions on X (official quest threads + regular digests).

Result: any public “claim” (I built a hero, completed a quest, found a rare combination) is not just words, but a statement that can be verified from an on-chain trail.

---

What it looks like for the player

• After a key action (craft/completion) the player gets a simple Share button.

• Publishing can be:

  • a standalone post,

  • a reply to the thread of a specific quest (so a build/strategy is seen where the discussion is happening),

  • a continuation of the player’s personal thread (a series of builds/progress).

Important: we don’t “post on behalf of the user.” Any UGC publication is initiated by the player’s explicit action.

---

What it looks like for the community

We maintain clear “gathering points” for discussion:

• Official quest threads are where players publish builds, tactics, results, and compare approaches.

• Official digests (weekly/daily) are a curated view of the best of the period: top builds, interesting strategies, rare finds, and key milestones.

Because of this, discussions don’t scatter across random posts — they remain in a clear structure: “quest → thread → best replies → digest”.

---

Verifiability as a product value

“a blockchain somewhere in the background,” but as a layer of verifiability.

What becomes verifiable:

• the existence of a hero/items and the progress associated with them,

• the fact of crafting/claiming a reward,

• the fact of completing a quest,

• “first discovery” and rarity of finds (when this is defined by the game rules).

Each card/post includes a compact Proof Capsule: a minimal set of identifiers that can be used to verify the corresponding on-chain event.

The user sees this as “✅ Verified on blockchainr” with a link to a verification page.

Why this doesn’t turn into spam

We design distribution to be controlled and safe from the start:

• UGC posting happens only via user action.

• Official publications go through a separate content pipeline with frequency and quality rules.

• Protection against duplicates and accidental retries.

• Posting pace limits and careful repetition (without “flooding the feed”).

• Separation of concerns: user posts and official content are different modes.

---

Growth loops on X

We use a few clear scenarios that scale with the ecosystem:

1. Quest launch (Launch Thread) Each new quest gets an official “hub” thread: rules, rewards, an explanation of verifiability, and verification links.

2. Player replies in the quest thread Builds and strategies are posted where the discussion is — and are immediately tied to proof.

3. Regular digest (Weekly/Daily) The best of the period is formed from verifiable progress facts and engagement, and each item includes a proof link.

4. Milestones Public moments triggered by network/game facts (major achievements, rare discoveries, meaningful progress thresholds).

---

Why this matters for Stellar

This model turns user content into mass, distributed public awareness built on verifiable events:

• many different accounts,

• different audiences,

• continuous mentions and click-throughs,

• and most importantly — a transparent, verifiable foundation without trusting server “claims”.

---

What we ask from the blockchain ecosystem

• Amplification: boosting key threads (quest launches, digests, milestones).

• Tech touchpoint: a short sync on best practices for working with on-chain events and building showcases on top of them.