Onchain Traction Submission Guide
How to submit your traction data for Onchain Traction scoring.
What You Need
Before starting, gather the following:
| Item | Required | Notes |
|---|---|---|
| Smart contract addresses | Yes | All main contracts |
| Wallet ownership proof | Yes | For contract verification |
| Analytics dashboard link | Yes | DeFiLlama, Dune, etc. |
| TVL data | Recommended | Current and historical |
| Transaction data | Recommended | Volume and wallet metrics |
| Cross-chain deployments | If applicable | Contract addresses per chain |
Submission Process
Step 1: Access Power Signals
From the project submission flow, navigate to Step 2: Power Signals.
Step 2: Select Onchain Traction
Click on "Onchain Traction" to expand the section.
Step 3: Provide Contract Information
Smart Contract Authorship:
- List all main contract addresses
- Specify chain for each contract
- Provide block explorer links
- Be prepared to sign verification message or transaction
Step 4: Provide Traction Metrics
For each applicable metric:
TVL (30-Day Change):
- Current TVL
- TVL from 30 days ago
- Link to DeFiLlama or data source
Transaction Volume:
- Transaction count or volume (last 7 days)
- 30-day average for comparison
- Link to block explorer or analytics
Active Wallet Growth:
- Unique wallets in last 7 days
- Comparison to 30-day average
- Link to Dune dashboard or Flipside query
Cross-Chain Activity:
- List all chains with active deployments
- Contract addresses on each chain
- TVL or activity data per chain
Protocols Built Atop:
- Count of integrating protocols
- Names of key protocols
- Evidence of integrations (DeFiLlama, docs, announcements)
Step 5: Review and Continue
Verify all information is correct and click "Continue".
Tips for Higher Scores
For Smart Contract Authorship
Be prepared to verify:
- Have access to owner wallet
- Can sign messages from owner address
- For multi-sig, identify team member signers
- Document deployment history
Best practices:
- Use multi-sig for important contracts
- Maintain clear ownership records
- Keep verification keys secure but accessible
- Document proxy/upgrade patterns
For TVL (30-Day Change)
Grow TVL organically:
- Build user trust through security
- Offer competitive value propositions
- Market effectively
- Avoid mercenary capital
Monitor consistently:
- Track TVL daily
- Understand drivers of change
- Respond to market conditions
- Cross-reference multiple sources
For Transaction Volume
Drive usage:
- Launch new features
- Improve user experience
- Run campaigns thoughtfully
- Reduce friction
Filter manipulation:
- Exclude wash trading
- Focus on unique users
- Document organic patterns
- Be transparent about spikes
For Active Wallet Growth
Grow user base:
- Improve onboarding
- Build community
- Focus on retention
- Provide ongoing value
Filter bots:
- Apply proof-of-humanity checks
- Analyze transaction patterns
- Exclude automated behavior
- Document methodology
For Cross-Chain Activity
Deploy strategically:
- Launch on chains where users are
- Ensure >$10k TVL per chain
- Maintain activity on each deployment
- Consider omnichain frameworks
If single-chain:
- Integrate with bridges
- Make cross-chain easy for users
- Track bridge volume
- Need >$50k/30d bridge volume to count
For Protocols Built Atop
Build infrastructure:
- Design for composability
- Provide clear APIs and SDKs
- Document integration patterns
- Support integrators
Foster ecosystem:
- Showcase integrations
- Announce partnerships
- Maintain integrations page
- Track ecosystem growth
Verification Process
Contract Ownership Verification
You'll be asked to verify contract ownership through one of:
- Wallet Signature: Sign a specific message with owner wallet
- Transaction: Send 0 ETH to verification address
- Multi-sig: Execute verification transaction through multi-sig
Be prepared with:
- Access to owner wallet
- Knowledge of multi-sig participants
- Deployment history documentation
Data Verification
Guardians will verify:
- TVL matches DeFiLlama or other sources
- Transaction data matches block explorers
- Wallet counts are accurate and bot-filtered
- Cross-chain deployments are active
- Protocol integrations are legitimate
After Submission
- Your submission is reviewed by Thrive's Guardian network
- You'll be contacted for contract ownership verification
- Guardians verify all metrics against public data sources
- Scores are assigned based on verified information
- Metrics are automatically updated at specified frequencies
Common Issues
Cannot verify contract ownership:
- Ensure you have access to owner wallet
- If keys are lost, contract may not be verifiable
- For multi-sig, at least one signer must be verifiable
- Document any ownership transfers
TVL data doesn't match:
- DeFiLlama data may lag
- Report discrepancies to DeFiLlama
- Provide alternative sources with explanation
- Ensure all chains are counted
Transaction volume unclear:
- Clarify if reporting count or value
- Explain calculation methodology
- Document bot filtering approach
- Note any unusual events
Wallet growth looks suspicious:
- Document bot filtering
- Explain any spikes (campaigns, etc.)
- Show organic growth patterns
- Provide context for guardians
Cross-chain counts disputed:
- Only active deployments count (TVL > $10k)
- Testnets don't count
- Verify recent activity on each chain
- Provide block explorer links
Protocol integrations unclear:
- Provide specific evidence for each
- Must be independent teams
- Must be active protocols
- Document integration depth
Need Help?
If you encounter issues during submission:
- Review individual signal pages for detailed guidance
- Check methodology pages to understand scoring
- Contact Thrive support for technical assistance
- Join the Thrive Discord for community help