Role

Deploying contracts on Arc · 26

These projects have their own contracts on Arc. Deploying is the role with the most on-chain surface, so these entries carry checks where they are meaningful: whether the contract source is verified on an explorer, whether an audit has been published, and where a token pair exists, whether liquidity is locked. Each check records what we observed, when, and where you can see it. A check that does not apply to a project is shown as Not applicable and is never a mark against it. None of this is a safety judgment — read the audits and verify addresses yourself.

#ProjectWhat it builds on ArcRoleStatusLinksChecked

Questions

What does contract verified mean?

The deployed bytecode has matching published source on an Arc explorer, so you can read what you are interacting with. It says nothing about whether the code is good.

Why do some entries show Not applicable?

Because the check has no meaning for that project — a protocol with no token pair has no liquidity to lock. Not applicable is never rendered as a negative.

How is status decided?

Status reflects what we observed on the date shown, not what a project announced. Every entry carries a dated source you can open and check yourself. Live can become Inactive if activity stops.