# Create Cred

### Creating a Cred in Phi Protocol

Creating a Cred is a fundamental process in the Phi Protocol ecosystem. This guide will walk you through the steps to create a Cred, including setting up basic information and choosing the appropriate verification method.

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2FCT22sRx9omNSICtLmLxX%2Fnapkin-selection%20(20).png?alt=media&#x26;token=20962b0e-03bb-478e-b321-a0e0976e0486" alt=""><figcaption></figcaption></figure>

{% embed url="<https://www.loom.com/share/be016e2f3eab45dbbd295f25c4956f04?sid=41f60594-4827-41a1-bb8d-2520ea9d374a>" %}

#### Step 1: Basic Information

1. **Title/Requirement**: Clearly explain what requirement users need to meet to claim the Cred. For example, "Receive tokens from Optimism's first airdrop".
2. **Eligibility Networks**: Select the blockchain network(s) relevant to your Cred (e.g., Base).
3. **Cred Logo**:
   * File types: JPG, PNG, SVG, or GIF
   * Maximum file size: 2MB
   * Recommended dimensions: 512x512 pixels
4. **Project**: Select a related project to enhance user search results.
5. **Related Links**: Add relevant links (e.g., <https://app.uniswap.org/swap?chain=base>).
6. **Description**: Provide a detailed description of your Cred. For example: "This cred is awarded to individuals who were recipients of Optimism's first airdrop, recognizing their early involvement and positive contribution to the Optimism network. The first airdrop was a pivotal moment in Optimism's journey, aimed at rewarding users who actively contributed to the ecosystem's growth.

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2FUZhXXU7FlsyZ3L6Bzry7%2FTerminal___Phi.png?alt=media&#x26;token=c61d25b3-a12d-4e53-9bc0-6a2d9077f290" alt=""><figcaption></figcaption></figure>

#### Step 2: Verification

Choose a verification type based on your Cred's requirements:

1. **File Upload (CSV)**:
   * Best for on-chain activity that won't have updates and can be extracted into a CSV.
   * The first row must include 'address' as a header.
   * Maximum file size: 5MB
   * Example use case: Beacon chain genesis depositor
   * Using onchain analytics tools like [Dune](https://dune.com/), you can create csv easily .

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2Fqeo3VxWyD5HmtVeCT6hp%2FTerminal___Phi.png?alt=media&#x26;token=57fc9ad2-4b40-4ec4-a377-303fe654cc86" alt=""><figcaption></figcaption></figure>

2. **API**:

* Best for on-chain activity linked to APIs, allowing for dynamic eligibility checks.
* You need to provide an API endpoint.
* The response should be a JSON object with 'mint\_eligibility' and 'signature' properties.
* Example use case: Creating a transaction on Base
* [Please check this document](https://docs.phi.box/explore-phi/~/changes/76/phi-protocol/signature-verifier)

<figure><img src="https://2819029275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN3SP59WsdH4ATy0OAWIv%2Fuploads%2FAF4XtwaculZMB72GgzAl%2FTerminal___Phi.png?alt=media&#x26;token=6a33e510-fb5a-4ffb-8031-914b3c960c25" alt=""><figcaption></figcaption></figure>

For both types, provide a Source Link (URL for the data source or source code).

### Best Practices

1. **Clear Requirements**: Ensure your Cred's requirements are clearly defined and easily verifiable.
2. **Relevant Networks**: Choose eligibility networks that are most relevant to your Cred's purpose.
3. **Compelling Description**: Write a description that clearly explains the significance of the Cred and why users would want to claim it.
4. **Appropriate Verification**: Choose the verification type that best suits your Cred's nature (static vs. dynamic).
5. **Data Integrity**: For CSV uploads, ensure your data is accurate and properly formatted.
6. **API Reliability**: For API verifications, ensure your endpoint is reliable and follows the required response format.