> For the complete documentation index, see [llms.txt](https://wiki.pepe.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.pepe.wtf/chapter-2-the-rare-pepe-project/fake-rares-and-dank-rares/fake-commons/fake-commons-submission-rules.md).

# Fake Commons Submission Rules

**You can find the official Fake Commons Submission rules** [**here**](https://fakeraredirectory.com/fake-submission-rules/)**.**

First thing you need to do when creating your Fake **Common**, is to create a [Counterparty](/chapter-3-blockchain-counterparty-how-to/counterparty-what-is-it.md) asset to associate with it.

To the non crypto-coin person this can be quite the learning task. To people already involved in Bitcoin it’s not that hard. Visit [this guide](https://github.com/robotlovecoffee/xcponboarding/wiki/Creator:-Onboarding-to-XCP-Freewallet-Desktop) to learn how to create an asset.

The cost to create an asset is 0.5 XCP (and a little bitcoin for the miner fee).

Use the [Fake Commons Submission Portal](https://fakeraredirectory.com/fake-submissions/) and fill out the form with the details of your FAKE COMMON submission. Please ensure that your card image is under 10MB - here you upload your card image only (referenced by 'image\_large' in your JSON), other media can be referenced via URL.

To submit to the Fake Commons Directory, and as an ode to our forefrog-fathers, you will need to destroy a minimum of 2,100 [PEPECASH](https://pepe.wtf/asset/PEPECASH). You can destroy the token by using the [Freewallet.io](http://freewallet.io/) app. Please do not destroy anything until your card has been approved… no refunds.

Once approved your card will appear on [fakeraredirectory.com](https://fakeraredirectory.com/fake-commons/), and [pepe.wtf](https://pepe.wtf/new/collections/Fake-Rares)… and probably all over Twitter. Don’t feel compelled to DM the team to check on the status. Persistence is key in many things… but here it will only distract and delay.

### **Format Rules**

Similar to Fake Rares, your base card image (jpeg, png or gif) should be portrait and of 400X560 pixels in dimensions, your enhancements can explore other sizes, keeping ratio is nice for your enhancements but not essential – but should be followed if you would like to show your mp4 instead of the card in the directory for example.\
\
Your base card image should be under 10MB (squeezing something to that size is part of your art now) and you must always supply a base card image, even if your prefer media is the mp4 or Iframe URL. Your token description field should reference a JSON which also expresses the base image as the “image\_large” keys value.

{% hint style="info" %}
Reach out on the [Official Telegram Chat](https://t.me/OFFICIALFAKERARES) if you need help.
{% endhint %}

![FAKE SUBMISSIONS](/files/OOFnC8BKoDEW15XG7i9A)


---

# 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://wiki.pepe.wtf/chapter-2-the-rare-pepe-project/fake-rares-and-dank-rares/fake-commons/fake-commons-submission-rules.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.