Smart Contract Authorship

Verifies that the project team owns the smart contracts they claim.

Methodology

What We Look For

Proof that the project team controls the smart contracts they claim to have deployed.

Verification Process:

1. Request wallet signature or specific transaction to a verification address
2. Cross-reference signing wallet with smart contract owner address on block explorer
3. Verify deployment history and admin rights
4. Check for multi-sig wallets if applicable
5. Document verification transaction hash for audit trail

Data Sources

• Block explorers (Etherscan, Arbiscan, etc.)
• Smart contract source code
• Wallet signatures
• Multi-sig records

Guide

Finding Information

Step 1: Identify Your Contracts

List all smart contracts your project has deployed:

• Contract addresses
• Chain(s) they're deployed on
• Block explorer links

Step 2: Verify Ownership

For each contract, identify:

• Deployer address
• Owner/admin address
• Multi-sig participants (if applicable)
• Upgrade authority (if upgradeable)

Step 3: Prepare Verification

Be ready to prove ownership through:

• Wallet signature from owner address
• Transaction from owner address to specified verification address
• Multi-sig transaction (if applicable)

Submitting Evidence

When submitting smart contract authorship:

1. Contract Addresses:

   • List all main contract addresses
   • Specify chain for each
   • Link to block explorer

2. Ownership Proof:

   • Owner/admin wallet addresses
   • Deployer address
   • Multi-sig configuration (if applicable)

3. Verification Method:

   • Preferred: Wallet signature with specific message
   • Alternative: Transaction to verification address
   • For multi-sig: List of signers and their roles

4. Additional Context:

   • Contract deployment dates
   • Upgrade mechanism (if applicable)
   • Proxy patterns used