> ## Documentation Index > Fetch the complete documentation index at: https://docs.cantina.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Competitions > Finding labels, statuses, payments, and teams in Cantina security competitions. ## Finding labels > Find and understand the labels used in security competitions, helping to classify and resolve findings during the judging and escalation process. Below you can find a list with all the finding labels used during a competition. These labels are primarily used by judges. | Labels | Description | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Escalated | The "Escalated" status is designated for findings that have been escalated due to a disagreement between the researcher and the judge during the judging phase. This status is exclusively applied during the escalation phase of the process. After the judging phase when the escalation phase starts, if a researcher disagrees with the decision made by the judge regarding their finding, they have the option to escalate it. This status serves as a mean to address such disagreements and ensure fair resolution. For further details on the escalation process and its guidelines, please refer to the escalation-process page. | ## Finding status > Discover the various finding statuses used in Cantina competitions, including how issues are categorized from submission to resolution. Below you can find a list with all the finding statuses used during a competition. | Finding Status | Explanation | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | New | Once a finding is submitted by the security researcher, it will be labelled as new by default. | | Rejected | Upon review, if the finding does not fit the criteria within the competitive scoring schema, the judge will list the finding as rejected. | | Duplicate | A finding is marked as duplicate when it's the same issue reported by someone else. Duplicates are rewarded as well. | | Confirmed | When the finding is valid, it will be labelled as confirmed and be awarded based on the competition prize pool. | | Spam | When a finding is marked as spam, it typically refers to the issue reported being irrelevant, low-quality, automated and inappropriate. Both the judge and the sponsor can mark this status for findings. | | Withdrawn | If the researcher submits an issue and decides to withdraw it for any reason, the finding will be labelled as "Withdrawn". | ## Payments > Explore the Cantina Docs for insights on services, competition guidelines, account management, and payment details to enhance your experience. > **Note:** To receive payments, you must first undergo the KYC process and set up your payment address. Find all the necessary information regarding payments and KYC in the KYC and Payments documentation. ### Payment Statuses | Status | Description | | ----------- | ----------------------------------------------------------------------------------------------------------------------------- | | `planned` | Payment is planned, and will have to be scheduled by the Cantina team, common blockers for this include incomplete KYC status | | `scheduled` | Payment is scheduled, and will be processed on next batch of transactions | | `submitted` | Payment is submitted, awaiting on the multi-sig to be signed by majority | | `executed` | Payment is executed successfully on-chain | | `disputed` | Payment is disputed, where in the planned/scheduled phase, it was disrupted | | `cancelled` | Payment has been cancelled | ## Teams > Learn how security researchers can form competitive teams in Cantina, ensuring effective collaboration and streamlined payment distribution during events. In Cantina, security researchers are able to form teams with other researchers to participate in competitions. To register as a team, refer to the team-submissions section in our Discord. Within a team, you can read comments left by your teammates on a code base as well as view, edit and escalate their findings, allowing for efficient collaboration during competitions. ### Team Payments 💰 As of now team payments are disbursed to the team leaders, and it's up to the team leader to distribute responsibly. Cantina will **not** be responsible for any internal feuds within teammates. ### Team Creation In order to apply as a team, within the Cantina discord team-submissions chat, send in the team submission request as the following format: ```javascript theme={null} Team Submission Request - Team Name: - Competition Name: - Team Lead (Cantina Username): - Other Team Members (Cantina Usernames): ``` When the Cantina core team has processed the application, you will see the team name you are part of on the top right section within the competition repository. Team applications are **only effective for the mentioned competition.** If you want to participate in a different competition with the same team, send another team application request. Please refrain from making findings before the team is made, as once a finding is submitted, teaming up is no longer possible.