# Logging Claims

## What is a claim?

A claim is the process of uploading images and information to the Silvi App in order to produce a proof for an event. Claims can be configured to send/receive payouts. The information in the claim, and the methodology that it is fulfilling will determine the payout. However claims can be made by anyone to initiate the project in the Silvi database, and methodologies/payouts are not required. \
\
There are two types of claims:

### Registration Claim

A registration claim is a genesis claim when you register an asset on the map page for the first time. It can also be used to define environment types such as seed beds, potted beds or reforestation sites.&#x20;

### Post-Registration Claim

A post registration claim is filed on an asset that has already been registered - think of it as an update on the asset. The information in the claim, and the methodology that it is fulfilling will determine the payout for the follow-up events such as proof of maturity etc

## Logging a Claim on an Asset

1. Show up to the asset in-person with the Silvi app
2. Click on an asset in the map page.&#x20;
3. Make sure it is the right asset, and click log claim.&#x20;
4. Choose the type of claim you would like to make and follow the instructions.

<figure><img src="https://2065371811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw1Pg5SrG22I3HhrT5WM8%2Fuploads%2FL6jtZs5f0pNMQTucFrjU%2FScreenshot%202024-06-22%20at%2011.04.24%E2%80%AFAM.png?alt=media&#x26;token=3adb8442-6db7-4378-bd99-8752c7c56217" alt=""><figcaption></figcaption></figure>

## Viewing filed claims:

1. Information about your claims will be visible on the claim history page.&#x20;
2. Claims will also be visible on the bottom of the information card as it relates to your asset.&#x20;

<figure><img src="https://2065371811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw1Pg5SrG22I3HhrT5WM8%2Fuploads%2FofzNPKXDUenoYbRxKqDD%2FScreenshot%202024-06-22%20at%2011.07.59%E2%80%AFAM.png?alt=media&#x26;token=8c2bf6d2-5730-4c05-836d-9a8313aafeff" alt=""><figcaption></figcaption></figure>
