DipDup primary-source snapshot
Fetched: 2026-05-09 UTC
1) Official docs home
Source: https://dipdup.io/docs
Selected excerpts from the docs:
DipDup is a Python framework for building smart contract indexers. It helps developers focus on business logic instead of writing a boilerplate to store and serve data.
Get started in three steps!
dipdup new … dipdup run
Additional signals from this page:
- DipDup presents itself as a developer framework first, not as a tokenized network or hosted data marketplace
- The docs emphasize fast project scaffolding and app-specific backend construction rather than one canonical shared query layer
- The quickstarts are chain-specific, which supports the view that DipDup is becoming a multi-chain developer tool rather than remaining Tezos-only infrastructure
2) Next-gen docs navigation
Source: https://docs-next.dipdup.io/
Selected excerpts from the docs structure:
GraphQL API REST endpoints Hooks Job scheduler Reindexing Monitoring Backup and restore
Additional signals from this page:
- The docs surface is much broader than a minimal indexing framework and includes substantial operational and API-serving concerns
- DipDup can be analyzed as application-backend infrastructure, not only as a chain data ingester
- The breadth of docs suggests the framework is opinionated about how indexed data becomes a usable service for apps
3) Public README
Source: https://raw.githubusercontent.com/dipdup-io/dipdup/next/README.md
Selected excerpts from the README:
DipDup is a Python framework for building smart contract indexers.
DipDup-based indexers are selective, which means only required data is requested.
This project is maintained by the Baking Bad team.
Additional signals from this page:
- Selective indexing is a core part of DipDup’s identity and differentiates it from more global indexing-network narratives
- The project foregrounds maintainership and ecosystem support, which is relevant context for governance and continuity even without token-governance surfaces
- The README still frames DipDup around developer productivity and reduction of boilerplate more than protocolization
4) Main GitHub repository
Source: https://github.com/dipdup-io/dipdup
Selected excerpts from the repo page:
Modular framework for creating selective indexers and featureful backends for dapps
Additional signals from this page:
- The repo subtitle makes the backend/application layer explicit, which is important for categorization
- The public repository surface reinforces that DipDup is being built as reusable infrastructure rather than a single hosted product
- GitHub remains one of the clearest primary surfaces for understanding its positioning
5) Indexer SDK repository
Source: https://github.com/dipdup-io/indexer-sdk
Selected excerpts from the repo page:
SDK for building indexers by DipDup. Provides a set of packages for constructing modular, flow-based indexing pipelines.
The SDK follows a flow-based programming (FBP) approach: independent asynchronous modules communicate through typed inputs and outputs, forming a processing pipeline (workflow).
Additional signals from this page:
- The separate SDK suggests DipDup is exploring a more composable pipeline architecture in addition to the main Python framework
- Source/process/sink framing helps distinguish DipDup from purely query-centric data providers
- The project is therefore useful for comparison against both developer frameworks and decentralized indexing networks
Notes
- This pass did not locate a classic whitepaper or litepaper from official sources.
- The most useful primary materials were the docs portals, first-party READMEs, and the main public repositories.
- DipDup is worth cataloging because it highlights a selective, app-backend-centric path through crypto data infrastructure rather than the network-token or hosted-platform path.
- Performance and ecosystem-support claims should still be treated as project claims unless independently verified.