# Core development notes and updates

**URL:** <https://forum.thegraph.com/t/core-development-notes-and-updates/2648>\
**Category:** Research & Development\
**Created:** [October 19, 2021, 1:55pm UTC](https://forum.thegraph.com/t/core-development-notes-and-updates/2648 "2021-10-19T13:55:37Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![adamfuller](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@adamfuller](https://forum.thegraph.com/u/adamfuller)\
**Post date:** [December 10, 2021, 5:57pm UTC](https://forum.thegraph.com/t/core-development-notes-and-updates/2648/6 "2021-12-10T17:57:44Z")

</div>

## 2021-12-10

Some more notes on recent core development.

**GIP-0020 Implemented** : [this is now supported](https://forum.thegraph.com/t/gip-0020-unattestable-indexer-responses/2607/4) across all core components, unlocking more graceful handling of unattestable queries by indexers and the gateway.

**Indexer components 0.18.4** : this was released yesterday, across [indexer-service](https://www.npmjs.com/package/@graphprotocol/indexer-service), [indexer-agent](https://www.npmjs.com/package/@graphprotocol/indexer-agent) and [indexer-cli](https://www.npmjs.com/package/@graphprotocol/indexer-cli)

**Firehose integration & testing** : this continues to be a key focus area, with progress in a few areas ([ensuring sync status compatibility](https://github.com/graphprotocol/graph-node/issues/3047), addressing bugs in callhandlers, establishment of a [dedicated block ingestor](https://github.com/graphprotocol/graph-node/pull/3041), and [research into contract filtering](https://github.com/graphprotocol/graph-node/issues/2980) for improved performance)

**Graph Node performance and robustness** : improving Graph Node’s performance is a key current focus area, with a range of optimisations in flight ([skip block pointer updates](https://github.com/graphprotocol/graph-node/issues/3028), [blockstream pipelining](https://github.com/graphprotocol/graph-node/issues/2581), [automatic subgraph retries](https://github.com/graphprotocol/graph-node/issues/2945), [parallel receipt ingestion](https://github.com/graphprotocol/graph-node/issues/3018) and more). In addition there is work to establish an easier setup for performance benchmarking (e.g. [introducing a stop block variable](https://github.com/graphprotocol/graph-node/issues/3033))

**NEAR support** : `graph init` [was extended](https://github.com/graphprotocol/graph-cli/pull/783) to support `--protocol near`, so NEAR developers can easily bootstrap their subgraphs. Meanwhile NEAR testnet indexing support on the Hosted Service is targeted for the coming weeks.

**Tendermint integration** : the [GIP was published in the forum](https://forum.thegraph.com/t/gip-0022-tendermint-indexing-for-graph-node/2815), for review & comment.

**Change block filtering** : when querying subgraphs, users will often want to fetch any new entities, since they last queried. [Work is in progress](https://github.com/graphprotocol/graph-node/pull/3014) to support this functionality for all subgraphs, via a new “\_change\_block” filter argument.

**GraphQL API Versioning** : specification of this feature is [in progress](https://github.com/graphprotocol/graph-node/issues/3024), which will enable breaking API improvements, as well as guaranteeing client-defined query determinism

**Subgraph forking** : the `subgraph debug` feature by Limechain has evolved to improve the developer experience, [PR in progress](https://github.com/graphprotocol/graph-node/pull/2995)

---

_[View the full topic](https://forum.thegraph.com/t/core-development-notes-and-updates/2648)._