Shadow
  • 🌗Overview
  • 🏁Quickstart
  • 🎯Use cases
  • ⛓️Supported chains
  • MODIFY CONTRACTS
    • Versioning
    • How to's
      • Proxy contracts
      • Using oracles
      • Factory contracts
      • Interdependent shadow contracts
  • GETTING DATA
    • Shadow RPC
    • Database syncs
    • Recurring exports
    • One-off exports
    • API Keys
  • Integrations
    • Postgres
    • GCS / S3
    • Dune
  • Product Guide
    • Catalog
    • Test runs
    • Subgraphs
  • Tips
    • Proxy contracts
    • Solidity beginners
      • Recommended tools
  • Resources
    • 📚Concepts
    • ❓FAQs
Powered by GitBook
On this page
Export as PDF
  1. Integrations

Dune

Set up a fully managed data pipeline to upload data to Dune in a one-off or recurring fashion.

PreviousGCS / S3NextCatalog

Last updated 8 months ago

The Dune integration is included on paid .

The Dune integration is available for and . It's ideal for teams who want to make their shadow events accessible to the community, or for teams who primarily use Dune as a tool for data analysis.

When you set up a data export to Dune, you’ll be able to specify:

  1. Which contracts and events to export

  2. How often to upload the data to Dune (daily, hourly, every 15 min)

You’ll also need to provide a Dune API key, which you can create on Dune following these . Make sure that your Dune plan allows you to upload the amount of data required for your data export.

See the or pages for additional information.

one-off exports
recurring exports
Shadow Fork plans
one-off exports
recurring exports
instructions