New kid (chain) on the block (Dune)? Here’s what you need to know to submit your chain’s protocol contracts to Dune.
Decoding enables you to create dedicated, easy-to-use datasets for your protocol on Dune, making it easier to build insightful dashboards.
Use the Dune UI for a guided submission process: https://dune.com/contracts/new.
For more details on decoding and submission, watch the Decoding Tutorial.
If you are looking to submit dozens of protocol contracts, you may submit via CSV. Work with us through Slack or Telegram, ensuring the CSV is formatted correctly for batch submission.
Batch submission bypasses UI safeguards, so make sure all flags are accurate, the ABI is formatted correctly, and naming follows Dune standards. Using the UI is preferred, as it includes checks that reduce errors and debugging time.
Follow this Google Sheet template for exact format, and refer to Dune’s documentation for guidance on fields like:
has_multiple_instances
is flag for for dynamic contractsis_created_by_factory
is flag for factory contractsIf using a proxy pattern, submit the implementation contract’s ABI.
These contracts typically don’t need submission, as Dune already covers standard approvals and transfers. Submit only if custom events are needed.
Look for below sets of contracts:
If decoding is required for additional contracts like routers or position managers, please submit those as well.
Submit the main marketplace contract with key events, such as:
ERC721BuyOrderFilled
ERC721SellOrderFilled
ERC1155BuyOrderFilled
ERC1155SellOrderFilled
If the contract isn’t verified on the block explorer, contact the protocol developers to obtain the ABI.