> For the complete documentation index, see [llms.txt](https://docs.skullco.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skullco.in/encrypted-nfts.md).

# Encrypted NFTs

**Core Innovation:** NFTs with two layers of information:

* **Public layer:** Visible to all (artwork, metadata, rarity)
* **Private layer:** Encrypted secret readable only by owner (word, coordinate, code)<br>

An Encrypted NFT (eNFT) is an NFT that **commits on-chain** to a private payload while keeping the payload itself **non-public**, and exposes a **standardized interface** for:

* publishing/verifying integrity (commitments),
* owner-gated access (authorization),
* optional proof-based gameplay (verification without disclosure).

#### **Why incomplete information matters:**

Traditional blockchain games have complete information  -  everything is public. This limits strategic depth:

* Bots can see all game state → optimal play is computable
* No negotiation (nothing hidden to trade)
* No bluffing, deception, or social gameplay

Incomplete information unlocks:

* **Uncertainty:** Players infer what others know
* **Markets:** Hidden data becomes tradeable asset
* **Social strategy:** Trust, betrayals, alliances matter
* **AI-resistance:** Social dynamics harder to automate than pure computation

***

####

***

####


---

# 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
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, and the optional `goal` query parameter:

```
GET https://docs.skullco.in/encrypted-nfts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.