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. GETTING DATA

Database syncs

PreviousShadow RPCNextRecurring exports

Last updated 7 months ago

Database syncs are included on paid .

Database syncs allow you to stream data to your own database in realtime.

Data will appear within seconds of a transaction on mainnet landing, and Shadow handles re-orgs for you automatically by replacing rows.

Steps

  1. Choose your data: Export shadow and/or mainnet data (coming soon), and specify which contracts and events you want to export.

  2. Choose your destination: You can send your data to your own Postgres database.

  3. Choose your settings: You’ll be prompted to set a start block for the recurring export if you’d like to export historical data.

If you choose to export shadow data, you’ll only be able to select events from contract addresses that you have shadowed (e.g. deployed modifications to). If you shadowed the implementation of a proxy contract, you’ll need to perform a “no-op deploy” on the proxy contract by hitting “Compile > Deploy” in the editor without making any shadow changes. We’re working on a better experience for this!

Pro Shadow Fork plans