FiDi
  • 🚀Get Started
  • FiDi Overview
    • 🔮FiDi Analytics Portal
    • 🖥️Widget Types
    • 📊Metrics Collection
    • 🤝Data Providers
  • Projects built on FiDi
    • 🌕Moonbeam Analytics
      • Project Information Requirements
      • Metrics Definitions
    • 📊Portfolio Analytics
      • Net Worth Tracking
      • Aggregation
      • Filters
      • Holdings
    • Staking & Lending Analytics
    • NFT Analytics
    • Swap & DEX Aggregation
    • Block Explorers
    • Analytics on iOS
  • Developer Relations
    • 🎯DotSight Library Overview
    • 👩‍💻Developer Support
    • 🎓Developer Guide
    • ⚙️Data API
  • Team
    • 🌐Get in touch
Powered by GitBook
On this page
  • FiDi's Approach to dApp Activity
  • Required Project Information
  • Additional Project-Specific Information
  • Additional Considerations
  1. Projects built on FiDi
  2. Moonbeam Analytics

Project Information Requirements

This section covers the indexing guideline and essential project's information.

FiDi's Approach to dApp Activity

In the web3 landscape, there's considerable debate and variation in how dApps and dApp activity are defined. At FiDi, we've opted for an inclusive approach, embracing the broadest definitions available to capture the range of blockchain-based projects and activities.

In addition to the smart contracts associated with the projects, FiDi indexers will consider deployer wallets, treasury wallets, and factory contracts associated with a particular dApp.

Required Project Information

To ensure comprehensive indexing of your project's activity, please provide the following information:

  1. Core Smart Contracts

    • Addresses of main contracts that define your project's core functionality and interact with the network in significant ways

    • Optionally, a brief description of each contract's purpose

  2. Factory Contracts

    • If applicable, addresses of any contracts that deploy other contracts, as a part of your dApp

    • Please also specify the creation topic (hash of the creation event) for each factory contract

  3. Deployer Wallets

    • If applicable, addresses of wallets used to deploy your project's contracts

Additional Project-Specific Information

You can optionally submit any other common contract types if applicable to your project:

  1. Treasury/Admin Wallets

    • Addresses of wallets that have administrative control or hold project funds

    • Optionally, a brief description of each wallet's function

  2. Oracle Contracts

    • Addresses of any oracle contracts used by your project

    • Optionally, a brief description of what data these oracles provide

  3. Bridge Contracts

    • Addresses of any bridge contracts for cross-chain functionality

    • List of chains connected by these bridges

  4. Governance Contracts

    • Addresses of any contracts related to on-chain governance

    • Optionally, a brief explanation of your governance model

Additional Considerations

By providing this information, you'll help ensure that FiDi can accurately index and analyze your project's on-chain activity. If you have any questions about what information to include or how to format it, please don't hesitate to reach out to our team.

Last updated 10 months ago

Please leverage if your project batches transactions before sending them on-chain to Moonbeam.

For factory contracts, please make sure your contract is derived from or mimics the standard .

The (multi-faceted proxy) are supported and will be indexed correctly.

🌕
Batch Precombile
Uniswap factory contract
Diamond contracts