Skip to content

Verification Methods

Before registering a token, you must prove you own it. Chain Daddy supports multiple verification methods depending on the chain type.

Chain vs Method Matrix

MethodEVM ChainsSolana
Mint Authority
Update Authority
Owner (contract)
Deployer
Majority Holder

Strength Rankings

Each method has a strength ranking that determines priority when multiple wallets could verify the same open slot.

RankMethodDescription
1 (Strongest)Mint AuthorityWallet controls token minting (Solana only)
2Update AuthorityWallet controls metadata updates (Solana only)
3OwnerContract owner() returns your address (EVM only)
4DeployerWallet that originally deployed the contract
5 (Weakest)Majority HolderWallet holds >50% of total supply

Strength matters only while a slot is unclaimed or expired. Registrations are first-claim-wins per (symbol, chain, token): once a valid registration exists, it is not displaced by a later claimant — even one with a stronger method. The stronger badge does show on your token page as a stronger trust signal.

EVM Methods

Owner

Chain Daddy calls the owner() function on your token contract. If it returns your connected wallet address, verification passes.

Requirements:

  • Contract implements owner() (standard Ownable pattern)
  • Connected wallet matches the returned address

Deployer

Chain Daddy checks on-chain deployment history to confirm your wallet created the token contract via CREATE or CREATE2.

Requirements:

  • Connected wallet is the original deployer
  • Deployment transaction is indexable on the target chain

TIP

Deployer verification works even if ownership was later transferred or renounced.

Majority Holder

Chain Daddy checks your wallet's token balance against total supply. You must hold more than 50% of the circulating supply.

Requirements:

  • Connected wallet holds >50% of total supply
  • Balance is checked at verification time (not historical)

WARNING

If you sell tokens and drop below 50%, your verification remains valid — registrations are first-claim-wins and are not displaced by other claimants. But if your registration later expires through activity decay, the slot opens again and any qualifying wallet (including one with a stronger method) can claim it.

Solana Methods

Mint Authority

Chain Daddy checks if your connected wallet is the current mint authority for the SPL token — this is the strongest Solana verification because mint authority has the most control over token supply.

Requirements:

  • Connected wallet is the current mint authority
  • Mint authority has not been revoked

Update Authority

Chain Daddy checks if your wallet is the metadata update authority. This proves control over the token's on-chain metadata.

Requirements:

  • Connected wallet is the update authority on the token's metadata account

Deployer

Similar to EVM, Chain Daddy checks if your wallet initiated the token creation transaction.

Requirements:

  • Connected wallet signed the original token creation instruction

Majority Holder

Same as EVM, your wallet must hold more than 50% of the token's total supply.

Requirements:

  • Connected wallet holds >50% of total supply
  • Balance checked at verification time

Frequently Asked Questions

I lost access to my deployer wallet. What can I do?

If you still have access to a wallet with a stronger verification method (e.g., Mint Authority on Solana, Owner on EVM), use that instead.

If you have no other qualifying wallet:

  1. Wait for the registration to expire via activity decay (30+ consecutive days below 60)
  2. Register again from a new wallet through the standard flow (see pricing)
  3. For future registrations, consider using a multisig wallet for built-in recovery

Prevent this scenario

Register from a multisig (like Safe) so no single key loss locks you out.

Can I verify with a different wallet than I registered with?

No. The wallet that verifies is the wallet that registers. Registrations are permanently bound to the verifying wallet.

What if ownership was transferred after I deployed?

Deployer verification still works — it checks historical deployment, not current ownership. And because registrations are first-claim-wins, the new owner cannot take over your existing registration with a stronger method; strength only matters if the slot is unclaimed or your registration expires.

My token has no owner function. Which method should I use?

Use Deployer if you created the contract, or Majority Holder if you hold >50% of supply — these are your available alternatives on EVM chains.