Jason Dreyzehner

Chaingraph currently maintains a single, undifferentiated "block buffer" of blocks which are waiting to be saved to the database. When a block is saved successfully, it is removed from the...

This will probably be solved by #18, but somehow block downloads are occasionally completing with a negative duration... We're just ignoring statistics from those downloads, but we should track down...

Right now we basically leave pod assignments up to chance – we should assign pods more intelligently, probably with [Affinity and Anti-Affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity). Ideally, the Postgres process should go to the...

It'd be nice to setup 1-click installs on DigitalOcean: https://github.com/digitalocean/marketplace-kubernetes/blob/master/CONTRIBUTING.md

Currently a production Chaingraph instance requires storage for the Postgres database (~600GB) as well as storage for at least one archival node (~200GB). Depending on your provider, that 200GB of...

Right now the agent pulls the version from `package.json`, which isn't necessarily a useful version value: https://github.com/bitauth/chaingraph/blob/ad0797a2b8399ef01244e2afbdf09d66113f3e12/src/config.ts#L12 https://github.com/bitauth/chaingraph/blob/ad0797a2b8399ef01244e2afbdf09d66113f3e12/src/config.ts#L307-L314 It would be better to use the docker image tag for the...

We should update a `CHANGELOG.md` using [`conventional-changelog`](https://github.com/conventional-changelog/conventional-changelog) before every chart release. (No need to add a check for pull requests to use conventional commit messages, I/other maintainers will probably squash...

We should run `helm lint` and [`helm test`](https://helm.sh/docs/topics/chart_tests/) in continuous integration before releasing new chart versions, see: - https://github.com/helm/kind-action - https://github.com/helm/chart-testing-action - https://github.com/helm/charts-repo-actions-demo It would be great to test the...

To implement and test support for very large blocks, Chaingraph should add default support for [`scalenet`](https://bitcoincashresearch.org/t/testnet4-and-scalenet/148), which currently uses a 256 MB maximum block size. (It should be as easy...

Chaingraph currently supports only a single mode of syncing which we'll call "maintenance mode". In maintenance mode the agent maintains: - a list of block header hashes according to each...