> For the complete documentation index, see [llms.txt](https://degen-games-2.gitbook.io/degen-games-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://degen-games-2.gitbook.io/degen-games-docs/how-the-game-works/contract-verification.md).

# Automatic Contract Verification

Every coin's source code is verified on the block explorer automatically, and its ownership is burned. No black boxes.

Every coin launched on Degen Games is **source-verified on the chain's block explorer automatically** after launch. The creator doesn't need to do anything.

## Why it matters

An unverified contract is a black box. Wallets, scanners and traders can see the bytecode but can't easily read what it does, and that's where hidden mints, blacklists and trading switches hide. Verified source code means:

* **Anyone can read it.** Open the coin's contract on the explorer and read the actual code.
* **Scanners can check it.** Security tools and screeners can analyze a verified contract, and they usually flag unverified ones.
* **It's the same for every coin.** Every coin comes from the same template, deployed by the same factory. There are no custom one-off contracts.

## Check a coin yourself

{% stepper %}
{% step %}

### Copy the contract address

It's on the coin's page. Use the copy button next to the address.
{% endstep %}

{% step %}

### Open it on the explorer

On Robinhood Chain, use [robin.etherscan.io](https://robin.etherscan.io), the official Etherscan explorer. [rh-scan.com](https://rh-scan.com) and [robinhoodchain.blockscout.com](https://robinhoodchain.blockscout.com) work too.
{% endstep %}

{% step %}

### Open the Contract tab

A verified contract shows its full source code, compiler settings and a read/write interface.
{% endstep %}
{% endstepper %}

## No owner, from block one

Every Degen Games coin sets its owner to the **burn address** at deployment:

```
0x000000000000000000000000000000000000dEaD
```

On most launchpads a coin has an owner wallet, and buyers have to trust that ownership gets renounced later. Here it's already gone, burned in the deploy transaction. No wallet can call an owner-only function, because no wallet is the owner. That includes the creator and Degen Games.

It's the same address a coin's liquidity goes to at [graduation](/degen-games-docs/how-the-game-works/graduation.md). Ownership and liquidity are burned to the same place, and neither can come back.

To check it, open the coin on the explorer, go to **Contract → Read Contract**, and read `owner()`. Scanners that flag "ownership not renounced" pass a Degen Games coin from its first block.

## Is it a real Degen Games coin?

Anyone can deploy a copycat token with the same name and image. To confirm a coin really came from the Degen Games factory, check any one of these:

* It appears on [degen.vip](https://degen.vip) when you search its **contract address**.
* `getLaunchedToken(token)` on the [launch factory](/degen-games-docs/developers/contracts.md) returns `exists = true`.
* The factory emitted a `TokenLaunched` event for it.

{% hint style="warning" %}
Always go by the contract address. Names, tickers and images can be copied. Addresses can't.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://degen-games-2.gitbook.io/degen-games-docs/how-the-game-works/contract-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.