# Encrypted Encounters

### eNFT Integration

**Concept:** Encrypted NFTs bridge Find2Earn and Strike by carrying actionable information<br>

**Discovery layer (Find2Earn):**

* Assemble shards → unlock boss location
* Map Shards reveal coordinates to hidden encounters

**Access layer (Strike):**

* Encounter Keys grant entry to solo duels or party raids
* Keys are tradeable (owners can host lobbies and charge tickets)
* Tactics Scrolls reveal boss behavior patterns

#### How it works

Encrypted NFTs (eNFTs) carry different kinds of **actionable information** that links our two modules:

* **Find2Earn → Strike:** eNFTs can hold **map shards/coordinates** that lead to treasure or unlock a **dungeon/raid entry**.
* **Strike → PvE/PvP:** other eNFTs hold **boss access** (start an encounter) or **boss intel** (e.g., attack sequence, weak points), giving owners a real edge in duels/raids.

Players trade, rent, or team up around these secrets. Information becomes an asset.

#### NFT Types

* **Map Shard (eNFT):** public art hints the region; **private layer** = coordinates or a narrowed search zone. Collect shards or trade to assemble the full location.
* **Encounter Key (eNFT):** grants **entry** to a solo or party boss/dungeon. Public layer shows the theme/tier; private layer holds lobby/entry data.
* **Tactics Scroll (eNFT):** **owner-only** instructions like a **boss attack sequence** (e.g., *Head → Head → Legs* opener), counter-tips, or timing notes.

#### Core Loops

**Path A — Find2Earn-first**

1. Win/collect **Map Shards** → assemble the **location** → claim chest or mint an **Encounter Key** there.
2. Use the **Key** to open a **solo/raid**.
3. Bring **Tactics Scroll** to increase success; share or rent intel to allies.
4. Clear → drop loot (gear/cosmetics), earn XP, spend on repairs/consumables.

**Path B — Strike-first**

1. Duel/raid in **Strike** to drop **Scrolls**.
2. Sell or bundle your intel with hosts who have **Keys**.
3. Join Find2Earn hunts to get **Map Shards** and access new encounters.

#### Mechanics Options (pick per event/season)

* **Simple Sequence (default):** Scroll reveals a **fixed attack pattern** (e.g., first 3 moves, or full opener). Easy to understand and share; scarce drops keep value.
* **Phase Notes (lightweight):** Scroll adds 1–2 **phase hints** (e.g., “below 30% stamina boss favors leg strikes”). Still simple, not overly technical.

#### Fairness & Longevity (minimal but enough)

* **Season-bounded intel:** Scrolls can be **seasonal** or **encounter-specific** to limit eternal spoilers.
* **Instance IDs (optional):** for high-stakes events, tie the Scroll’s value to an **instance ID** or **tier**, so leaked sequences don’t solve everything everywhere.
* **Positive sharing:** it’s **profitable to cooperate**—hosts split ticket revenue; teams trade Scrolls for a cut. Markets > secrecy policing.

#### Economy

* **Sinks:** encounter tickets, repairs, consumables, rerolls.
* **Faucets:** loot drops, cosmetics, leaderboard rewards, sponsor bounties.
* **Protocol revenue:** % fee on tickets/hosting and secondary trades of intel eNFTs.
* **Social markets:** lend/rent **Keys**, **Scrolls**; bundle intel with hosted runs.

#### Why this works

* **Simple to grasp:** “This NFT opens a fight.” “This one tells you the boss sequence.”
* **Naturally social:** owners host, others bring intel; teams coordinate roles.
* **Bridges modules:** Find2Earn feeds discovery; Strike pays it off in action.
* **Sustainable:** knowledge has resale value; sinks/faucets keep the loop healthy.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.skullco.in/strike/encrypted-encounters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.