Bump version 7.5.9 (#1070)

CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog], and this project adheres to [Semantic Versioning].
 
-## [Unreleased]
+## [7.5.9] - 2024-07-20
 
 ### Fixed
 
@@ -1447,6 +1447,7 @@ This release contains no changes except for the version number.
 
 <!-- Versions -->
 [Unreleased]: https://github.com/dipdup-io/dipdup/compare/7.5.8...HEAD
+[7.5.9]: https://github.com/dipdup-io/dipdup/compare/7.5.8...7.5.9
 [7.5.8]: https://github.com/dipdup-io/dipdup/compare/7.5.7...7.5.8
 [7.5.7]: https://github.com/dipdup-io/dipdup/compare/7.5.6...7.5.7
 [7.5.6]: https://github.com/dipdup-io/dipdup/compare/7.5.5...7.5.6

docs/10.supported-networks/0.overview.md

@@ -1,12 +1,12 @@
 ---
-title: "→ Overview"
+title: "Overview"
 description: "DipDup can index any EVM-compatible network as long as there's enough historical data. This page contains a list of supported networks and instructions on how to configure your indexer for them."
 network: "ethereum"
 ---
 
 <!-- markdownlint-disable no-bare-urls no-inline-html no-emphasis-as-heading -->
 
-_Latest update: 2024-06-01._
+_Updated 2024-07-18: Found and marked/fixed broken external links._
 
 # Supported networks
 

docs/10.supported-networks/36.polygon.md

@@ -54,7 +54,7 @@ Explorer: [Polygonscan](https://testnet-zkevm.polygonscan.com/)
 |        datasource | status        | URLs                                                           |
 | -----------------:|:------------- | -------------------------------------------------------------- |
 |  **evm.subsquid** | 🟢 works      | `https://v2.archive.subsquid.io/network/polygon-zkevm-testnet` |
-| **abi.etherscan** | 🟢 works      | `https://api-testnet-zkevm.polygonscan.com/api`                |
+| **abi.etherscan** | 🟢 works      | `https://api-testnet-zkevm.polygonscan.com/api` (🔴 404)       |
 |      **evm.node** | 🤔 not tested |                                                                |
 
 ### Polygon zkEVM Cardona Testnet

docs/10.supported-networks/43.taiko.md

@@ -11,10 +11,10 @@ description: "Taiko network support"
 
 ### Taiko Katla
 
-Explorer: [Blockscout](https://explorer.katla.taiko.xyz/)
+Explorer: [Blockscout](https://explorer.katla.taiko.xyz/) (🔴 404)
 
-|        datasource | status       | URLs                                   |
-| -----------------:|:------------ | -------------------------------------- |
-|  **evm.subsquid** | 🔴 no API    | N/A                                    |
-| **abi.etherscan** | 🟢 works     | `https://explorer.katla.taiko.xyz/api` |
-|      **evm.node** | 🟡 HTTP only | `https://rpc.katla.taiko.xyz`          |
+|        datasource | status       | URLs                                            |
+| -----------------:|:------------ | ----------------------------------------------- |
+|  **evm.subsquid** | 🔴 no API    | N/A                                             |
+| **abi.etherscan** | 🟢 works     | `https://explorer.katla.taiko.xyz/api` (🔴 404) |
+|      **evm.node** | 🟡 HTTP only | `https://rpc.katla.taiko.xyz`                   |

docs/10.supported-networks/44.tanssi.md

@@ -9,10 +9,10 @@ description: "Tanssi network support"
 
 {{ #include 10.supported-networks/_intro.md }}
 
-Explorer: [Blockscout](https://3001-blockscout.a.dancebox.tanssi.network)
+Explorer: [Blockscout](https://3001-blockscout.a.dancebox.tanssi.network) (🔴 404)
 
-|        datasource | status        | URLs                                                    |
-| -----------------:|:------------- | ------------------------------------------------------- |
-|  **evm.subsquid** | 🟢 works      | `https://v2.archive.subsquid.io/network/tanssi`         |
-| **abi.etherscan** | 🤔 not tested | `https://3001-blockscout.a.dancebox.tanssi.network/api` |
-|      **evm.node** | 🤔 not tested |                                                         |
+|        datasource | status        | URLs                                                             |
+| -----------------:|:------------- | ---------------------------------------------------------------- |
+|  **evm.subsquid** | 🟢 works      | `https://v2.archive.subsquid.io/network/tanssi`                  |
+| **abi.etherscan** | 🟢 works      | `https://3001-blockscout.a.dancebox.tanssi.network/api` (🔴 404) |
+|      **evm.node** | 🤔 not tested |                                                                  |

docs/10.supported-networks/7.bitgert.md

@@ -7,8 +7,6 @@ description: "Bitgert network support"
 
 # Bitgert
 
-{{ #include 10.supported-networks/_intro.md }}
-
 ### Bitgert Mainnet
 
 Explorer: [Brisescan](https://brisescan.com/)
@@ -21,7 +19,7 @@ Explorer: [Brisescan](https://brisescan.com/)
 
 ### Bitgert Testnet
 
-Explorer: [Brisescan](https://testnet-explorer.brisescan.com/)
+Explorer: [Brisescan](https://testnet-explorer.brisescan.com/) (🔴 502)
 
 |        datasource | status       | URLs                                                     |
 | -----------------:|:------------ | -------------------------------------------------------- |

docs/10.supported-networks/_dir.yml

@@ -1,5 +1,5 @@
 navigation.title: "Supported Networks"
-navigation.icon: "zap"
+navigation.icon: "link"
 navigation.subdir: true
 navigation.pin: true
 navigation.network: "ethereum"

docs/14.contributing.md

@@ -10,48 +10,66 @@ DipDup is a free and open-source software licensed under the [MIT License](#mit-
 
 ## Contributor Guide
 
+Thanks for considering contributing to DipDup! We're happy to have you here. This document is meant to help you get started with the project. If you have any questions, feel free to open an issue on [GitHub](https://github.com/dipdup-io/dipdup/issues/new/choose) or join our [Discord server](https://discord.gg/aG8XKuwsQd). Have fun!
+
+### Workflow
+
+1. Fork the repository, clone it, and `git checkout next`.
+2. Create a new branch with `git checkout -b <your-branch-name>`.
+3. Make your changes. Run `make format lint` to perform basic code checks.
+4. When finished, push your branch with `git push origin --set-upstream <your-branch-name>`.
+5. Create a pull request to merge `<your-branch-name>` into `next`. Maintainers will review your pull request and may make comments, ask questions, or request changes. When all feedback has been addressed the pull request will be approved, and after all checks have passed it will be merged by a maintainer.
+
+### Development environment
+
+You'll need Python 3.12 and PDM package manager to run DipDup locally. To set up the development environment, run `pdm venv create python3.12 && pdm sync && $(pdm venv activate)`. To see the list of development commands, run `make help`.
+
+## Maintainer Guide
+
+::banner{type="warning"}
+This section is intended for DipDup maintainers only! If you're a regular contributor, you don't need to read it (but welcome to do so).
+::
+
 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).
 
 ### General
 
 - All code in this repository MUST be licensed under the [MIT License](#mit-license).
-- Python code in this repository MUST run on Python 3.11. Using modern language features is encouraged.
-- Python code in this repository MUST run in Linux, macOS, Docker, and environments on `amd64` and `arm64` architectures.
-- We use the PDM package manager to set up the development environment. You SHOULD install it and run `pdm run -l` to see available shortcuts.
-- Have fun!
+- Python code in this repository MUST run on Python 3.12. Using modern language features is encouraged.
+- Python code in this repository MUST run in Linux, macOS, and Docker environments, and on `amd64`, `arm64` architectures. CI will help you with that.
 
 ### Git workflow
 
-- Branch names MUST follow `prefix/short-description` format. Prefixes currently in use: `feat` for features, `fix` for bugfixes, `docs` for documentation, `exp` for experiments, `ci` for GHA and Docker stuff, `aux` for everything else.
+- Default branches are `next` for the latest release and `current` for the previous one. `next` is the default branch for pull requests.
+- Branch names SHOULD follow the `prefix/short-description` format. Prefixes currently in use: `feat` for features, `fix` for bugfixes, `docs` for documentation, `exp` for experiments, `ref` for refactoring, `ci` for GitHub Actions, scripts and Docker stuff, `aux` for everything else.
 - Commits in pull requests MUST be squashed when merging to `next`.
 - Issues and pull requests MUST have a descriptive title; they SHOULD be linked to each other, appropriately labeled, and assigned to maintainers while in progress.
 
 ### Codestyle
 
-We use several tools to enforce codestyle and code quality: `black` for autoformatting, `ruff` for linting, and `mypy` for typechecking. All checks MUST pass before merging the code to the default branch. Everything not enforced by these tools is up to the developer. But here are some recommendations:
+We use several tools to enforce the code style and decent code quality: `black` for autoformatting, `ruff` for linting, and `mypy` for type checking. All checks MUST pass before the code is merged to the default branch. Anything not enforced by these tools is up to the developer. But here are some recommendations:
 
-- Consistency is the key. If you see a pattern in the codebase, follow it.
-- Use `NOTE`, `TODO`, and `FIXME` prefixes for meaningful comments. They help a lot to navigate the codebase.
-- Lazy imports are important to keep startup time low for tiny commands. We also do it for project imports, so not a big deal.
-- Some methods and attributes are made private to avoid polluting the public API. Feel free to access them from the outside if you know what you are doing.
-- Finally, about exact language features. f-string formatting is preferred over other syntax. Be careful with the walrus operator. Don't forget else in conditional expressions. Listen to your mom. We have no consensus about the match-case yet.
+- Consistency is the key. If you see a pattern in the codebase, follow it. Use meaningful names for variables, and avoid abbreviations.
+- Use `NOTE/TODO/FIXME` prefixes for meaningful comments, Avoid inline comments. It helps a lot in navigating the codebase.
+- Lazy imports are important to keep startup time low for tiny commands. We also do this for project imports.
+- Some methods and attributes are made private to avoid cluttering the public API. Feel free to access them from the outside if you know what you are doing.
+- Finally, about exact language features. f-string formatting is preferred over other syntax. Be careful with the walrus operator. Don't forget `else` in conditional expressions. Listen to your mom. We do not yet have a consensus on match-case.
 
 ### Changelog
 
-- All changes that affect user (developer) experience MUST be documented in the CHANGELOG.md file.
-- Changes that significantly affect DipDup maintainers' experience MAY be documented in the CHANGELOG.md file.
-- The changelog MUST conform to the "Keep a Changelog" specification (CI will break otherwise). Group order we use: Added, Fixed, Changed, Deprecated, Removed, Performance, Security, Other.
-- Lines describing changes MUST be sorted and begin with the component name (usually Python module name).
+- All changes that affect the user (developer) experience MUST be documented in the CHANGELOG.md file.
+- The changelog MUST follow the "Keep a Changelog" specification (CI will break otherwise). Group order we use: Added, Fixed, Changed, Deprecated, Removed, Performance, Security, Other.
+- Lines describing changes MUST be sorted and start with the component name (usually the Python module name).
 
 ### Documentation
 
-- A page in "Release notes" section MUST accompany all major releases. Minor releases SHOULD be documented as well. Avoid includes in Release notes pages as they are not intended to change over time.
-
-## Maintainer Guide
+- We have a pretty complex process of building and deploying docs. It starts with Markdown files in the `docs` directory. Then `scripts/docs.py` script generates several dynamic pages, API references, processes custom Cookiecutter-style macros, and so on. The resulting Markdown is pushed to the private frontend repository via the `docs.yml` GitHub Action. `docs.py` script code should answer most of your questions.
+- All public APIs MUST be documented using docstrings. We use the reStructuredText (reST) syntax.
+- A page in the "Release notes" section MUST accompany all major and minor releases. Avoid using `#include` macro in Release notes as they should not change after the publication.
 
 ### Dependencies
 
-- All dependencies MUST be declared in `pyproject.toml` file and pinned to non-breaking versions (e.g. `~1.2`).
+- All dependencies MUST be declared in `pyproject.toml` file and pinned to non-breaking versions. We are more of an application than a library, so no asterisks, please.
 
 ### Security
 
@@ -69,38 +87,32 @@ We use several tools to enforce codestyle and code quality: `black` for autoform
 - Docker images for stable releases MUST be published on Docker Hub and GitHub Container Registry.
 - Maintainers MAY publish arbitrary images on GHCR and remove them when not needed.
 
-### Installer
-
-- Installer module MUST depend on Python stdlib only.
-
 ### Scaffolding
 
 - Project templates SHOULD cover all index types available in DipDup.
 - They also MAY contain additional features and integrations.
 
 ### Demo projects
 
-- Demos are stored in `src` directory. They MUST be generated automatically from project templates using replay files.
+- Demos are stored in the `src` directory. They MUST be generated automatically from project templates using replay files.
 - Maintainers SHOULD run `pdm demos` command regularly to ensure that demo projects are up to date.
 
 ### Releases
 
 - Release versions MUST conform to [Semantic Versioning](https://semver.org/). Releases that introduce breaking changes MUST be major ones.
-- Only the latest major version is supported in general. Important fixes SHOULD be backported to the previous major release (currently, 6.5)
+- The latest major version is the only one supported in general. Important fixes SHOULD be backported to the previous major release.
+
+### Release process
 
 Releasing a new version currently requires some manual actions:
 
 1. Ensure that all GH issues and PRs are closed and linked to the milestone.
-2. Checkout to `aux/X.Y.Z` branch from `next` (or `master` for 6.5). Update DipDup version in `pyproject.toml`.
+2. Checkout to `aux/X.Y.Z` branch from `next` (or `current` for backports). Update DipDup version in `pyproject.toml`.
 3. Run `make before_release` to lock dependencies, dump `requirements.txt` files, generate demo projects etc.
 4. Commit and push all changes with msg like `Bump version X.Y.Z`. Open a PR, and link it to the milestone.
 5. Now you may want to switch Docker images of demos we host to `aux-X.Y.Z` tag as a smoke test.
 6. Merge the PR, then `git tag X.Y.Z && git push origin X.Y.Z`. Wait for `release.yml` and `docs.yml` pipelines to finish.
-
-### 6.5 branch
-
-- DipDup 6.5 is supported until March 2024. Maintainers MUST backport bugfixes from the main branch until then. All Tezos and TzKT-related code was synced with `next`, so it should be a relatively easy task.
-- 6.5 docs and installer are hosted on GH Pages at `docs.dipdup.io`.
+7. Don't forget an announcement on Twitter and Discord.
 
 ## MIT License
 

docs/7.references/3.context.md

@@ -75,7 +75,7 @@ description: "Context reference"
 <dl class="field-list simple">
 <dt class="field-odd" style="color: var(--txt-primary);">Parameters<span class="colon">:</span></dt>
 <dd class="field-odd"><ul class="simple">
-<li><p><strong>kind</strong> (<em>Literal</em><em>[</em><em>'tezos'</em><em>] </em><em>| </em><em>~typing.Literal</em><em>[</em><em>'evm'</em><em>]</em>) – Either ‘tezos’ or ‘evm’ allowed</p></li>
+<li><p><strong>kind</strong> (<em>Literal</em><em>[</em><em>'tezos'</em><em>, </em><em>'evm'</em><em>]</em>) – Either ‘tezos’ or ‘evm’ allowed</p></li>
 <li><p><strong>name</strong> (<em>str</em>) – Contract name</p></li>
 <li><p><strong>address</strong> (<em>str</em><em> | </em><em>None</em>) – Contract address</p></li>
 <li><p><strong>typename</strong> (<em>str</em><em> | </em><em>None</em>) – Alias for the contract script</p></li>