> For the complete documentation index, see [llms.txt](https://docs.jpegd.io/jpegd-dao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jpegd.io/jpegd-dao/about-the-jpegd-protocol/tokens/jpeg-cards.md). # JPEG Cards JPEG Cards are a series of 1,020 NFT cards that offer utility within the JPEG'd protocol. A subset of these cards will have additional utility (to be announced) on our upcoming platform, but regardless **all** JPEG cards will be eligible to stake for 1% of the JPEG supply over a month period. The JPEG cards display some of the most pervasive, captivating, and influential memes in crypto. Certain JPEG cards without a cig attribute will be whitelisted for culturally significant Weenis Warmers. Cigarette cards will additionally be able to be locked and used to gain boosts on your credit limit and liquidation ratio. **Unstaking a cigarette card will lead to a loss of the boosts and may trigger liquidations of overborrowed positions.** All JPEG cards will be whitelisted related to the upcoming AMM for NFTs we are building. The total NFT supply is 1,000 NFTs, plus an additional 20 honoraries. Of the 1,000, about 50 cards are reserved for the team. --- # 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.jpegd.io/jpegd-dao/about-the-jpegd-protocol/tokens/jpeg-cards.md?ask=&goal= ``` `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.