# TheBadge's Introduction

What is TheBadge? How does it work?

## Overview

The Badge is a **decentralized** certification platform powered by Blockchain. It provides users the opportunity to tokenize information from the real world in the form of certifications (badges) by giving a peer-to-peer certification mechanism. This means that these badges are verified and validated by the community, which decides what should be accepted and what is not. Those from the community that participates in this process are economically incentivized.

{% hint style="info" %}
This means that these badges are verified and validated by the community, which decides what should be accepted and what is not. Those from the community that participates as data curators are economically incentivized.
{% endhint %}

The solution that TheBadge brings to the industry is a decentralized verification and certification platform that allows information from the off-chain world to be certified.&#x20;

Users will be able to create their certification standards and perform the verification process themselves while being financially rewarded for doing it. This will help to reinstate trust and transparency because the users themselves will be doing the verification. Users will be able to certify documents (Diplomas, finished courses, etc), social media accounts, cryptocurrency projects, companies, communities, digital art copyright, RWA ownership, etc.&#x20;

The market as well as the use cases will make TheBadge a platform used by millions of users.

## **Video overview:**

{% embed url="<https://www.thebadge.xyz/video/TheBadge.mp4>" %}

## Quick links

{% content-ref url="/pages/Oam058lwOyZoU09QwKrJ" %}
[How it works](/protocol-mechanics/how-it-works)
{% endcontent-ref %}


# Relevance

Why do we need decentralized certifications?

To ensure that our initiatives to attract more people to the crypto ecosystem are fruitful, we must make the ecosystem trustworthy. To create a decentralized future, having accurate information is essential. If we as a decentralized community entrust all verification duty only to centralized entities, the entire ecosystem will suffer the consequences of bad actors' wrongdoings.

Also, decentralized certifications on the blockchain can offer several advantages over traditional centralized certification systems. Here are a few reasons why we need decentralized certifications on the blockchain:

1. Trust and Transparency: A decentralized certification system on the blockchain can provide a high level of trust and transparency. This is because the blockchain is a distributed and transparent ledger that records every transaction and certificate issuance. It can also allow users to verify the authenticity of certificates without relying on a central authority.
2. Tamper-proof Certificates: Blockchain-based certificates are tamper-proof, which means that they cannot be altered or modified once they are issued. This can help to prevent fraud and ensure the integrity of the certification process.
3. Portability: Decentralized certifications on the blockchain can be easily shared and transferred between individuals and organizations. This can reduce the administrative burden and cost associated with verifying certificates across different platforms.
4. Decentralized Governance: Decentralized certification systems can be governed by a distributed network of users, rather than a central authority. This can help to ensure that the certification process is fair, transparent, and accessible to everyone.

Overall, decentralized certifications on the blockchain can provide a more secure, transparent, and efficient way to verify and manage certifications. It can also help to reduce the administrative burden and cost associated with traditional certification systems.


# Definition

Web3 certificates

A **Badge** is a Web3 certificate that in order to receive it, the person needs to go through a decentralized verification process.&#x20;

Web3 certificates are similar to traditional certificates, but they have two big differences.&#x20;

* The first one is the verification process in order to obtain them. In traditional certifications, the verification process is carried out by a centralized authority, and in Web3 certifications, this process is done in a decentralized way by the community.&#x20;
* The second difference is the possible use cases. Having a Web3 certificate enables people to not only use them in the traditional world, but also in the Web3 world. Nowadays, people cannot use normal certificates, such as university degrees, or a course completion diploma, to apply for a job in a Web3 company.&#x20;

This is because there is currently no way to connect these two worlds. TheBadge and its Web3 certificates allow this by wrapping a real-world certificate into a Web3 version of it.\ <br>

<figure><img src="/files/d2xs1OqsW0ajnp8NwG1e" alt=""><figcaption><p>Badge examples</p></figcaption></figure>

<br>


# Badge history

Badge registry

This is a registry that collects all the information of a [badge](/what-is-a-badge/definition).<br>

This information can be:

* Badge creation
* Badge’s curation criteria
* Badge application
* Evidence provided by the applicant
* Challenged information
* Arbitration data
* Badge revalidation

This section can be found in each individual badge’s profile.

<br>


# Badge Categories

TheBadge offers two categories of badges that are designed to address the needs of all types of users.&#x20;

## [Community Badges](/what-is-a-badge/badge-categories/community-badges)

## [Third-party Badges<br>](/what-is-a-badge/badge-categories/third-party-badges)


# Community Badges

Badges verified by the community

* These are badges that go through TheBadge’s decentralized certification process in which the community does the proof of evidence submitted and grants the badge to the applicant.
* These badges are backed by TheBadge’s community.
* These badges have to be created by an individual which is registered in the protocol as a creator.
* The evidence submitted will be verified by a community curator.
* These badges can be challenged and follow the decentralized arbitration system.

**For example:**

A web3 user can apply to get an on-chain ID certificate to bring his/her reputation from web2 to the blockchain. Once the user applies to one of these certificates, TheBadge's community can then verify the provided evidence.


# Third-party Badges

Blockchain certifications as a service

* These are also referred to as “web3 certifications as a service”
* They are issued by a third-party entity that decided to use TheBadge’s certification platform to issue its own certificates.
* These badges are backed by this third-party entity.

**For example:**

An online educational platform, such as Udemy, could issue its certifications on-chain by registering as a third-party entity on TheBadge. Once registered, it will be able to create its certifications on-chain without having to develop the technology.


# Creators

Certification's designers

**Creators** design and publish badges (web3 certificates) with their own certification criteria for others to apply for and receive it. They will determine what information/proof potential badge holders need to provide in order to receive their badge.\
\
They will also set the price of their badge, and their profit comes whenever a person has claimed their badge.

{% hint style="info" %}
For example, Bob is a compliance officer in the traditional world, and he would like to apply his knowledge to increase trust in the Web3 ecosystem. He could register as a creator in TheBadge, and use his knowledge to create the criteria necessary for a project or a person to receive the decentralized compliance badge.&#x20;

Then, every time someone claims a badge of this type, Bob will receive his profit for being the creator.
{% endhint %}

In order to become a creator, the user will have to go through a registration process in The Badge.

[Step by step guide on how to become a creator](broken://pages/RpVWvoLOIh9DH9UokoMi)


# Curators

Bounty Hounter

**Curators** will be in charge of verifying and validating the proof submitted by potential badge receivers. They will be able to generate a challenge if they have discovered that the evidence submitted by the potential badge receiver is fake or inaccurate. In order to generate this [challenge](/protocol-mechanics/challenge), curators will have to provide their evidence for why they consider that the data provided is not veridic.

{% hint style="info" %}
Providing incentives for curators to review the evidence and raise challenges when necessary carefully, helps to ensure that only deserving candidates receive badges and protects the reputation and integrity of the certifications.
{% endhint %}

Their profit will come from a percentage of the deposit left by the potential badge receiver. Providing incentives for curators to carefully review the evidence and raise challenges when necessary, helps to ensure that only deserving candidates receive badges and protects the reputation and integrity of the certifications.

Every user can be a curator, for more information about how to start & earn curating follow this [step by step guide](/how-to-guides/how-to-curate).


# Badge Receiver

Badge applicant

Badge receivers are users claiming their desired badges to verify specific information.&#x20;

They will be responsible for providing the evidence requested by the creator of their desired badge. Also, when applying for their desired badge, they will need to pay a small fee and leave a deposit.&#x20;

{% hint style="info" %}
The fee is the cost that the creators define on it when they create the certificate, you can read more about it [here](/protocol-participants/creators), and the deposit will be the reward of the curators in case the information submitted is challenged and the [challenge](/protocol-mechanics/challenge) is lost.&#x20;
{% endhint %}

Follow this [Step by step guide on how to apply for a badge.](/how-to-guides/how-to-get-a-badge)

<br>


# Badge Types

Each badge will have a sub-category referred to as “type”. All badge types will certify a specific niche of information. Each niche represents an industry within the blockchain ecosystem. It is expected that the more use cases that the blockchain industry develops, the more badge types that will be added.&#x20;

Examples of current Community Badges types are:

* #### DeFi
  * Decentralized compliance
  * Decentralized credit score
  * Decentralized project auditing
* #### RWA
  * Real world asset verification
* #### On-chain ID
  * Proof of talent
  * Social media verification
* #### NFT
  * Decentralized NFT Registry
  * NFT artist


# Badge Status

In the process of getting a badge, the badge can go through four different stages:

:mag: **Pending/ in review**

> This status lasts from the moment the user applies for the badge, until it finishes the curation period.

:checkered\_flag: **Ready**&#x20;

> This status means the badge was approved and it is ready to be claimed. Status lasts from approved until the badge was claimed by its owner.

:white\_check\_mark: **Claimed**

> This status means that the badge was claimed and it is in possession of the wallet’s owner.

:scales: **Challenged**

> The badge is in the arbitration process, and it will stay there until jurors make a final decision.\
> \
> If the badge is approved, it will change its status either to “ready” or in case it was already claimed, it will go back to claimed status.


# How it works

TheBadge’s decentralized certification mechanism consists of 5 steps in which all 3 [protocol participants](/protocol-participants/creators) play a role:

## 1. Evidence submission:

Badge applicants have to prove that they meet the requirements needed to receive that badge. Therefore applicants need to submit all the information required by the badge creator.

These requirements will be shown as open fields in the second step of the badge application. The user needs to fill in this information as detailed as possible in order to prove to the curators that they qualify for the badge.

## 2. Optimistic evaluation period&#x20;

This step begins once the user fully submits his badge application, and it will be automatically shown among the badges pending for review. This information can be seen by all [curators](/protocol-participants/curators), who take care of the veracity of the information, which are all members of TheBadge’s community.

The application will stay in review until a curator challenges the application, or until the “review time” pre-selected by the badge creator is over.

## 3. Evidence challenge

This step is only triggered if a curator initiates a \[challenge]\(link to challenge doc) to the applicant because he/she believes that the proof submitted is fraudulent.

To initiate the challenge, the curator will have to make a deposit. The deposit amount depends on the type of badge. This deposit will be used to reward the jurors, as well as the winner of the challenge.

## 4. Arbitration&#x20;

Once the curator initiates the challenge, the arbitration starts. The arbitration process is delegated to Kleros.io. Kleros will select an odd number of jurors and it will initiate the dispute resolution.

The duration of the dispute will depend on the juror's decision. Once the majority of jurors agree on an answer, the case is resolved.

## 5. Resolution&#x20;

This is the final step in which it is revealed whether the badge applicant receives the badge or not.&#x20;

There are **two ways** to arrive at a **resolution**:

<details>

<summary>Challenged</summary>

If the evidence provided was challenged by a [curator](/protocol-participants/curators) the arbitration is started:

1. If it is decided that the evidence provided is true, the applicant receives the badge, his own deposit, and the deposit of the curator that initiated the challenge.
2. If it is decided that the evidence provided was false, the applicant does not receive a badge, and loses his deposit and the application fee.

</details>

**a**. It is decided that the evidence provided was false:

<figure><img src="/files/lDPAKI2IcfVY21aMBFlO" alt=""><figcaption><p>Badge requester lose the challenge.</p></figcaption></figure>

**b**. It is decided that the evidence provided is true:

<figure><img src="/files/XZZ8wDcZ5r4QGwN2vZIz" alt=""><figcaption><p>Badge requester win the challenge.</p></figcaption></figure>

<details>

<summary>Not Challenged</summary>

If the evidence was not challenged by a [curator](/protocol-participants/curators), the applicant receives the badge after the review period is over.

</details>

<figure><img src="/files/PzoXFmin2wJmTnvutrOY" alt=""><figcaption><p>Not challenged badge request.</p></figcaption></figure>


# Challenge

The curation mechanism

A challenge is the step initiated by a curator when they find that the evidence provided by the badge applicant is fraudulent. Once the curators discover fraudulent information, they will make a deposit to initiate an arbitration process. Which is similar to a normal legal case in the traditional justice system.&#x20;

The objective of the deposit is that in case the jurors determine that the information was fraudulent, the curator will get the deposit of the applicant and his own deposit back. If the jurors found that the information provided was veridic, the juror will lose his/her deposit.

During the challenge process, the badge’s applicant and the curator can upload as much evidence as they can to prove their point to the jurors for them to make the final decision.<br>


# Challenge Flow

1. Badge applicant submits information and leaves his deposit.
2. Curators verify it.
3. Curator finds fraudulent information.
4. Curator challenges information.
5. Arbitration starts and an odd number of jurors are randomly selected
6. Jurors decide on a case winner.
7. Both deposits are sent to the case winner.


# How to get a badge

Badge's application process

Once you have found your desired badge, the first step to receive it is applying for it.&#x20;

Apply by doing the following steps:

#### **1. Select the connect button on the top right corner and approve it.**

#### **2. Select your desired badge in the section “Apply to get one of these badges” in the homepage.**

![](https://lh4.googleusercontent.com/yoCAmfrCg7hFNljYRYMCfqvLNGo9tYzjnxgHQdPmLc_nKfT8uLNHF0tkHSU0P780vOcH48d9637IsiCXPYcxBEVCd1TQKIVagudHNfXhz2y4OmLIezGD85QgVYlVHZ8llzZ15sxOXxK51Li-13mz4Q)

#### **3. Read the small guide and terms and conditions and press next if agreed.**

![](https://lh5.googleusercontent.com/ue8-CaUiRyzN9GM2cp3Z-L7KMokWei0AyN0OVu6OdCjD5yAGO2Z-S1MpPP_a8TVcd5HgB6Jp0ZCk7AAVVf0jnAzul64eiffaN3_0vtfGY2PHLW5Y3fS0mjQJOMbeW3-PB2q-6gRXmg410VuD2HsvIA)

#### **4. Provide evidence required**

In this step, you will have to provide the evidence required for your desired badge type, which will depend on each badge type.

![](https://lh5.googleusercontent.com/HOe0KUzDh-0DptxHcpkHH5sCSPTuawv1LlpZXrdEdAqHwC8hj9Qd9LJxh-0_f5kodsWrYKHYU6Bn0tGuq2PPn5M9eSfO2_svr_HlZM1TZ_pbfkjNaTjVw6CaG5ue_gmsKntdCn8UJ3nlEZOW8OXgNg)

#### **5. Provide the deposit and pay the application fee**

Each badge will have a different deposit and fee depending on the difficulty of the verification of the evidence, and the price placed by the badge creator.

![](https://lh5.googleusercontent.com/fjpndiEcrtsyyV4evruV8t6JKn4WYP3CqTn_toT_ouOgCs2kDHgOMvm7Qk7lvHXu-Kln-jZZ6Koo7y1ftuAX5fGJf72Ke7blkAkm3LFpbkDLXwPv4CqfbW7QXBG0v03KRDD6_lQVhH8xm_1nl2YaXA)

#### **6. Your badge was submitted and it is waiting for review!**

![](https://lh5.googleusercontent.com/ImqBgH4jxrBMC65zRbbAQUnRcpdn1ZcxV5wd2jjBPYkV8gEnR2AFQf5I2LCU6cSr-xtVdLYrUE53tjX3GsAjhLpdw5U6MXtRMbaCmP07C6uxkIqh-71fpavmSQ_BmiJF2IpIPhCeuUFlHnt9vTTORQ)<br>


# How to create a badge

Badge creation guide

In order to create a badge, first you need to register as a creator on TheBadge platform. Learn the steps to register as a creator here.

## Steps to create a badge:

### **1.** Go to your profile and select “Create a Badge”

### **2.** Read and accept the terms and conditions

### **3.** Provide badge-type basic information

#### Badge name

* An easy-to-remember name for your badge-type

#### Badge description

* Describe as detailed as possible what your badge is aiming to certify.

#### Badge picture

* Upload a picture that most represent your desired certification.

#### Badge cost

* Place the cost of your badge.
* The % will be for the creator and the % will be for TheBadge.

#### Upload the curation criteria

* This is a PDF document where the creator needs to write a detailed guide for the curators on how to verify the evidence submitted by the applicant.
* Learn more about it and find an example here

#### Badge expiration date

* If no revalidation is needed, simply leave it blank.
* If your badge will have to be revalidated after a certain period of time:
* Select after how long revalidation will be needed

#### Rigorousness

* This pre-determines the amount of jurors needed in case the badge application is challenged.
* The greater the rigorousness the larger the amount of jurors needed.
* The larger the amount of jurors, the greater the deposit that the applicant will have to make.

#### Badge challenge period duration

* This is the period in which a curator can challenge the evidence submitted.

### **4.** Evidence form

In this step, the creator needs to select the evidence that the applicant will have to submit in order to apply for this badge.

For every type of information asked, the creator will have to fill in:

#### Name

* This name will depend on what information they are trying to find out

#### Type

The options are predesigned, among them there are:

* Address
* Number
* Text
* File
* Link
* Twitter user
* PDF
* Video
* Etc.

#### Description

* Write in detail what you are intended to ask to best explain to the user what he needs to upload.

### **5.** Submit

You should now be able to see your created badge within your creator profile section.

<br>


# How to become a creator

Creator's registration

For users to become creators, they will have to go through a short and easy registration process:&#x20;

#### 1. Click on "Become a creator" on the Dapp's homepage.

![](/files/5lTpHUYlOjD6lR0yaTAA)

#### 2. Fill in the registration form which is divided into 3 steps:

1. Provide the information requested:
   * Profile picture
   * Description
   * Provide at least one contact method
2. Agree to terms and conditions
3. Registration’s confirmation

Submit your transaction and once confirmed, you will officially be a creator!<br>


# How to become a curator

There is no registration needed to become a curator.

{% hint style="info" %}
All users are allowed to curate badges and raise challenges.&#x20;
{% endhint %}

Learn how to curate [here!](/how-to-guides/how-to-curate)


# How to curate

Curation guide

The steps to curate the evidence submitted by the badge applicant are:

1. Connect your wallet by clicking on the “Connect” button in the top right corner.
2. Once connected, click on the button “Curate” in the top right corner.
3. In this section are all the badges waiting to be curated.
4. Click on a badge, and the evidence submitted will appear on a pop-up window.
5. Click to open the “Curation Criteria”, and follow the curation guidelines.
6. Examine the evidence following the criteria
   1. If evidence follows the criteria, move on to curate the next badge.
   2. &#x20;If the evidence does not clearly follow the criteria, click on “Challenge” to initiate the challenge process.


# How to challenge

Challenge guide

### Initiate a challenge

If evidence does not follow the curation criteria, the curator will start the challenge process. These are the steps:

1. &#x20;Click on the “Challenge button”
2. A new form will open for the curator to submit as much information as possible to back his claim that the applicant does not follow the curation criteria. This information will be forwarded to the jurors to make the final decision.
3. The following information should be added in this form:
   1. Title of the challenge

      > For example: Applicant does not follow criteria
   2. Description
      * Describe in text form why the evidence submitted does not follow the criteria.
      * You can add links, numbers, and all you consider necessary to prove your point.
   3. An attachment
      * Attach any document to better support your challenge
4. Deposit
   * Add your deposit which will be used to reward jurors and the case winner.
5. Click on “Send” to confirm your challenge submission

You have successfully initiated a challenge, now you can follow the updates on that badge’s profile.

<br>


# How to claim a third party certificate

Get a badge from a third party company

These badges, diplomas, or certifications are backed by a company that uses TheBadge's Dapp to issue and distribute them. This means that in order to receive a third-party badge or certificate you must first be in direct contact with the company.

### Steps to claim your third-party badge:

1. Go to your email inbox and look for an email coming from TheBadge (<hello@thebadge.xyz>)
2. Open the email and it should look like this!

   <br>

   <figure><img src="/files/Ru0P5M6Q0hzEsVXsANZ5" alt=""><figcaption><p>email example</p></figcaption></figure>
3. Click on the "Claim my badge" button
   * You will be directed to TheBadge's app
4. Fill up your wallet address in the corresponding area and press submit!

<figure><img src="/files/fU3kzSHMOvwHbaFaaTBw" alt=""><figcaption><p>Badge claiming portal</p></figcaption></figure>

After doing that, you will see a confirmation like this that your badge was successfully claimed:

<figure><img src="/files/18FDcXpiNnqhl4vdw8cP" alt=""><figcaption><p>Badge's successful claim confirmation</p></figcaption></figure>

You can now find your badge, diplomas, or certificates in your profile at TheBadge's app, as well as among your NFTs in your wallet.

Visit your profile by just clicking on "Check your new badge" button.

If you have any questions feel free to reach out to our support on [Discord](https://discord.gg/bcchkpvwGm).


# How to place your diploma on LinkedIn

Show your diplomas from TheBadge among your achievements

In order to successfully do this, you should have first claimed your third-party badge, diploma, or certification.

### Steps to place your diploma on your LinkedIn page:

1. Visit your [profile](https://app.thebadge.xyz/user/profile) in TheBadge's app (connect your wallet if needed)
2. Scroll down to the "Owned badge section" and click on the badge or diploma

   <figure><img src="/files/994ZupPg1Q9VPL7Q0v8f" alt=""><figcaption></figcaption></figure>
3. Click on the LinkedIn icon below the diploma
   * You will be directed to the LinkedIn website

<figure><img src="/files/NZP7Qgd8QuZB7kgjYShF" alt=""><figcaption></figcaption></figure>

4. Once on LinkedIn press "Save".
   * The add license or certification window will pop-up automatically.

<figure><img src="/files/phbAw2Js4Qglxk7paxsP" alt=""><figcaption></figcaption></figure>

Enjoy your new credential on LinkedIn!

If you have any questions feel free to reach out to our support on [Discord](https://discord.gg/bcchkpvwGm).


# How to fetch badges

You can get access to Badges connecting to TheBadge’s subgraph:

<details>

<summary>Goerli Testnet</summary>

Graph url: <https://api.thegraph.com/subgraphs/name/nicosampler/thebadge-goerli>

Graph name: `theBadge`

</details>

<details>

<summary>Ethereum Mainnet</summary>

Coming soon :rocket:

</details>

In the subgraph, you can request data about badges. You can search for them by using the badge's id.&#x20;

For example:

```
query badgeById($id: ID!) {
   badge(id: $id) {
     id
     evidenceMetadataUrl
     reviewDueDate
     status
     isChallenged
     receiver {
       id
     }
     badgeType {
       id
       metadataURL
       validFor
       badgesMintedAmount
     }
   }
 }
```

**Take into account that a badge’s id has the format: “ {ownerAddress} - {badgeTypeId} ”**

Using the field: “evidenceMetadataUrl” (IPFS hash) you can obtain further information about the Badge. If you get the IPFS data from it, the JSON file that you receive has a structure like this:

<pre><code>{
    Columns: [],
<strong>    Values: {},
</strong>    Image:
}
</code></pre>

On the Image field, you will get the hash of the PNG file stored in IPFS for this particular Badge. If you want to show visually a Badge, you can use the image from there.\
\
On the other hand, Values and Columns contain the evidence provided by the user to obtain it.

“Columns” represents the form fields with label, type and description, and “Values” is an object (key-value) with the form label as key and the evidence on the other side. <br>

If you want to obtain all the badges for a particular address, you can use this:

```
query userBadges($ownerAddress: ID!) {
    badges(where: {requestedBy: $ownerAddress}) {
      id
      status
      reviewDueDate
      evidenceMetadataUrl
      badgeType {
        validFor
        metadataURL
        id
        badgesMintedAmount
        creator {
          creatorMetadata
        }
      }
    }
  }
```

\
If you have any questions or need further assistance, feel free to contact our team on our [Discord](https://discord.gg/ygVs48kRCm)!


# How to render badges

**Disclaimer:** we are under development, expect changes in the model in the future, we are migrating to the V2 of our contracts. We also plan to launch an SDK for making the integration easy but it's still under development. If you want to collaborate with us feel free to contact us on [discord](https://discord.gg/FTxtkgbAC4)

**Note**: we store the information under **IPFS**, that means that every ipfs hash that you will see on this tutorial has to be converted to urls to fetch the info from it. We recommend using one of the [following gateways](https://ipfs.github.io/public-gateway-checker/).

**For example with PinataCloud:**

* Original ipfs hash: QmZnKDwa7rkJEraPKVuDHSeQGCKuamG8WyxpNfZ9jm9qye
* Hash converted with gateway:&#x20;

```
https://gateway.pinata.cloud/ipfs/QmZnKDwa7rkJEraPKVuDHSeQGCKuamG8WyxpNfZ9jm9qye
```

1\) First to have to obtain the metadata of the badge that you want to render:&#x20;

* [How to fetch badges](/integration-guide/how-to-fetch-badges)

2\) Once you have the metadata it will look like this:

```
{
    "badge": {
      "id": "0x51fd663a6b85383c96e229ec12c0882eaa9886fe-8",
      "evidenceMetadataUrl": "ipfs://QmYVn1MGonZ6n1VKN8M7fEeGtfLeyjGSztFDEaTHqERcgD",
      "reviewDueDate": "1680277596",
      "status": "InReview",
      "isChallenged": false,
      "receiver": {
        "id": "0x51fd663a6b85383c96e229ec12c0882eaa9886fe"
      },
      "badgeType": {
        "id": "8",
        "metadataURL": "ipfs://QmaMdeyvZbgo2v5rKxopdZ6CFuJd95V2Lp3hmoWYYer4jJ",
        "validFor": "0",
        "badgesMintedAmount": "0"
      }
    }
  }
```

3\) Now you need to fetch the general information of the badge from the \`badgeType.metadataURL\` from IPFS, it will have a format like this:

```
{
    "description": "Proof of ownership of a Mercado Libre Sellers account",
    "image":"ipfs://QmW3hVcLJ1a5fD9yeKCLuoKB3WbZGY7kfxg66Hx53Wkk3n",
    "name":"Proof of Merchant Account in MercadoLibre"
}
```

4\) From here you can take "**name**" and "**description**"

5\) The **image** should be taken from the badge evidenceMetadatUrl (is an ipfs hash, you need to fetch it first):

```
{
  "columns": [
    {
      "label": "Wallet Address",
      "type": "address",
      "description": "Provide your personal wallet"
    },
    {
      "label": "Personal post link",
      "type": "link",
      "description": "Add your link to a Mercado Libres sellers post. With your wallet's address in the description."
    }
  ],
  "image": "ipfs://QmZnKDwa7rkJEraPKVuDHSeQGCKuamG8WyxpNfZ9jm9qye", -> this is the image of the badge
  "values": {
    "help": true,
    "Wallet Address": "0x7EC0354F3Df24B4F18a6691D42E97A4c0C422585",
    "Personal post link": "https://servicio.mercadolibre.com.ar/MLA-1381674462-servicio-de-certificacion-de-calificacion-_JM"
  }
}
```

6\) Then you can access using the **image** value

7\) Now you have two methods to render it:

* Using the TheBadge-UI-Library: <https://github.com/thebadge/thebadge-ui-library>
* Rendering the image using custom HTML.


# Using the TheBadge-UI-Library

#### Available components

* The UI-Lib contains a lot of components and different formats for displaying the badges, you can check them and access to the docs in [Storybook](https://main--638b62c10e52ebb22bd55c21.chromatic.com/?path=/docs/).
* Please note that the library it's still **under development.**
* The library repository can be found [here](https://github.com/thebadge/thebadge-ui-library).

#### 1) First you have to install the library:

```
yarn add thebadge-ui-library
```

#### 2) Then import CSS files with styles in your \_app.tx file:

```
import 'node_modules/thebadge-ui-library/dist/index.css'
```

#### 3) Now you can use the component by providing to it the badge metadata

#### Example with BadgePreviewV2:

```
{
    "badge": {
      "id": "0x51fd663a6b85383c96e229ec12c0882eaa9886fe-8",
      "evidenceMetadataUrl": "ipfs://QmYVn1MGonZ6n1VKN8M7fEeGtfLeyjGSztFDEaTHqERcgD", -> contains the imageUrl
      "reviewDueDate": "1680277596",
      "status": "InReview",
      "isChallenged": false,
      "receiver": {
        "id": "0x51fd663a6b85383c96e229ec12c0882eaa9886fe"
      },
      "badgeType": {
        "id": "8",
        "metadataURL": "ipfs://QmaMdeyvZbgo2v5rKxopdZ6CFuJd95V2Lp3hmoWYYer4jJ", -> contains the badgeTypeMetadata
        "validFor": "0",
        "badgesMintedAmount": "0"
      }
    }
  }
```

<pre><code><strong>imageUrl: "https://gateway.pinata.cloud/ipfs/QmZnKDwa7rkJEraPKVuDHSeQGCKuamG8WyxpNfZ9jm9qye"
</strong></code></pre>

```
const badgeTypeMetadata = {
    "description": "Proof of ownership of a Mercado Libre Sellers account",
    "image":"ipfs://QmW3hVcLJ1a5fD9yeKCLuoKB3WbZGY7kfxg66Hx53Wkk3n",
    "name":"Proof of Merchant Account in MercadoLibre"
}
```

```
<BadgePreviewV2
  imageUrl={badgeTypeMetadata.imageUrl} -> it should be an url, ipfs not supported at the moment
  size="medium" -> Large / Medium / Small
  title={badgeTypeMetadata.name}
  description={badgeTypeMetadata.description}
  badgeUrl={`staging-app.thebadge.xyz/${badgeType.id}/${ownerAddress}`}

  {/** NON-EDITABLE VALUES (under development) **/}
  animationEffects={['wobble', 'grow', 'glare']}
  animationOnHover
  badgeBackgroundUrl="https://images.unsplash.com/photo-1512998844734-cd2cca565822?ixlib=rb-4.0.3&ixid=MnwxMjA3fDB8MHxzZWFyY2h8MTIyfHxhYnN0cmFjdHxlbnwwfHwwfHw%3D&auto=format&fit=crop&w=500&q=60"
  textContrast="light-withTextBackground"
/>
```

It will look like this:<br>

<figure><img src="/files/XE90sk0tPTs6BvZAq0nL" alt=""><figcaption><p>Badge example</p></figcaption></figure>


# TheBadge's Ambassador

TheBadge is looking for a group that would like to join the community team to take on a vital role, in spreading awareness of TheBadge. The ambassadors get to work closely with the team in all that involves community affairs. They are part of the image of TheBadge in live and online events, in their communities, as well as in social media. They understand what TheBadge does and how it adds value to the blockchain industry. They love to contribute and share with the world!<br>

Some other characteristics of TheBadge Ambassadors:\
\
1\. They find blockchain cool!\
2\. They would like to learn a lot about The Badge.\
3\. They would like to create their own Web3 Certifications.\
4\. They attend crypto events regularly.

\
Do these characteristics resonate with you?\
\
If yes, we would love to get to know you!\
\
Feel free to Join our [Discord](https://discord.gg/bcchkpvwGm), and write that you would like to apply to become one.


