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

# Quick Start

## Create an Ethscription in 60 Seconds

[Ethscriptions.com](https://ethscriptions.com) has an [easy creation tool](https://ethscriptions.com/create), but if you want to go step-by-step:

1. Convert an image (max size: \~90KB) to a Base64-encoded data URI (`data:image/png;base64,...`) using a service like [base64-image.de](https://www.base64-image.de/). The Ethscriptions protocol supports all data URIs but images work best.
2. Convert the data URI to hex using an online tool like [hexhero](https://www.hexhero.com/converters/utf8-to-hex).
3. Send a 0 ETH transaction *to the person you want to own the Ethscription* with the hex data from (2) in the "Hex data" field.
4. After a few moments it should appear on this site.

{% hint style="info" %}
**Duplicate Content**: By default, duplicate content is rejected—only the first ethscription with a given data URI is valid (uniqueness is determined by the SHA256 hash of the full data URI, including headers). To allow duplicates, add `rule=esip6` to your Data URI (e.g., `data:image/png;rule=esip6;base64,...`). See [ESIP-6](/esips/accepted-esips/esip-6-opt-in-ethscription-non-uniqueness.md) for details.
{% endhint %}

## How to Transfer Ethscriptions

1. Find the id of the Ethscription you want to transfer. An Ethscription's id is the transaction hash of the transaction that created it. It looks like this: `0xcdb372580242c1c1bbcd2914ddbdb609b33d2e2e163c6595e164cb4dc6665153`. You can get this from Etherscan or from this site.
2. Send a 0 ETH transaction to the new proposed owner, including the Ethscription ID in the "Hex data" field.

{% hint style="info" %}
**Bulk Transfers**: You can transfer multiple ethscriptions in a single transaction by concatenating their IDs (without `0x` prefixes) in the hex data field. See [ESIP-5](/esips/accepted-esips/esip-5-bulk-ethscription-transfers-from-eoas.md) for details.
{% endhint %}

## How to Track Ethscriptions

You can use [ethscriptions.com](https://ethscriptions.com)! However, if you don't want to rely on a third party, you have two options:

### Option 1: Traditional Indexer

Run your own indexer that follows [the protocol specification](/overview/protocol-specification.md). The [ethscriptions-indexer](https://github.com/ethscriptions-protocol/ethscriptions-indexer) is open source.

### Option 2: Ethscriptions AppChain

Run an [AppChain node](/ethscriptions-appchain/running-a-node.md) to get cryptographic state with Merkle proofs. The AppChain derives L2 state from L1 calldata using a deterministic pipeline—no trust required.

## Where to Inscribe

You can create ethscriptions by posting calldata to Ethereum L1:

| Method          | Description                                                                                                                                                   |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **L1 Calldata** | Send a transaction with a Data URI in the hex data field                                                                                                      |
| **L1 Event**    | Smart contracts can emit `ethscriptions_protocol_CreateEthscription` events ([ESIP-3](/esips/accepted-esips/esip-3-smart-contract-ethscription-creations.md)) |

The AppChain observes both methods and translates them into L2 transactions.

## Next Steps

* [Protocol Specification](/overview/protocol-specification.md) - Detailed rules for creating and transferring
* [AppChain Overview](/ethscriptions-appchain/overview.md) - Learn about the L2 derivation pipeline
* [Collections](/ethscriptions-appchain/collections.md) - Create curated NFT collections (AppChain only)
* [Fixed Denomination Tokens](/ethscriptions-appchain/fixed-denomination-tokens.md) - Create fungible tokens (AppChain only)


---

# 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:

```
GET https://docs.ethscriptions.com/overview/quick-start.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.