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

# Deadmarks

Banknotes spend in the county. Ship them to the wallet you signed in with, and one note becomes one Deadmark (DMRK) on Solana.

Kevin runs the wire from the Birchport market. The marks go to the wallet already on your ledger.

Contract: [DMRKspYf38RCq9M6RSHP2CRhXVAPEkPLN9E7MwTfa95h](https://solscan.io/token/DMRKspYf38RCq9M6RSHP2CRhXVAPEkPLN9E7MwTfa95h)

## Shipping east

* The day's shipments are one shared pool of 120,000 notes. It resets on the UTC day. First come, first served.
* Your Ashen standing sets how many of those notes you can put on the truck.
* 250 notes is the smallest wire. If less than that is all the book has left today, that remainder can still go.
* Hostile and Exiled standing ships nothing.

| Standing | Notes you can ship in one day |
| -------- | ----------------------------- |
| Wary     | 1,000                         |
| Neutral  | 2,500                         |
| Warm     | 6,000                         |
| Friendly | 12,000                        |
| Allied   | 25,000                        |

If the coast is full, or your own cap is used up, the wire stays closed until the next day.

## Buying notes back

Kevin also sells notes for Deadmarks, out of paper the coast has already set aside. Most standings pay 2 Deadmarks for one note. Allied standing pays 1 for 1.

Deadmarks buy notes, rare blueprints, and property deeds. The notes themselves are what you spend on food, gear, and Kevin's counter.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://deadtiles.gitbook.io/deadtiles-docs/money/deadmarks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.