### Algorand Indexer 2.14.0-rc4

Support for miscellaneous fixes to catchup and state proof totals calculation in go-algorand.

### What’s Changed

- Devops: Bump go-algorand submodule to v3.9.2-beta by @onetechnical in [Pull Request #120](https://github.com/algorand/indexer/pull/1203)

---

### Algorand Indexer 2.12.4 and 2.11.2

We are providing the 2.11.2 version because there are additional implementation requirements introduced in 2.12.x. Please refer to documentation for details:

#### Overview

Bugfix to ignore malformed resources.

#### What’s Changed

- Bugfix: filter malformed resources

---

### TestNet and MainNet Update: 3.8.1

MainNet and TestNet were updated to 3.8.1 Fri Jul 8, 2022 9:00PM EDT (1:00AM +1d UTC).

#### Overview

Remove prefetch optimization.

#### Changelog

- Bugfix: Disable resource prefetch optimization

#### Protocol Upgrade

This release does not contain a protocol upgrade.

---

### Upgrade Algorand Indexer 2.10.0 along with Algorand 3.5.1

The archival node is necessary for normal indexer operation, so I wouldn’t disable archival mode or shut down the node. The config you mention appears to be for the algod node, so I would leave that as is. Indexer can be started and pointed to the archival node to catch up.

---

### Indexer error: overflowed subtracting rewards for block

Hmm, unfortunately I think this is broken because the database seems to be in an inconsistent state. For data integrity, I’d unfortunately recommend re-indexing, because the block evaluator is getting a different answer on the indexer side.

---

### TestNet and MainNet Update: 3.5.1

MainNet and TestNet will be updated to 3.5.1 Wed Mar 23, 2022 10:30AM EDT (2:30PM UTC).

IMPORTANT This release requires a protocol upgrade. This release contains a consensus protocol upgrade, which implements the following spec: [GitHub - algorandfoundation/specs at d5ac876d7…](https://github.com/algorandfoundation/specs/tree/d5ac876d7ede07367dbaa26e149aa42589aac1f7)

---

### Algorand Indexer Update 2.10.0

A database migration is included in this release. This has been timed to a few minutes on testnet and about half an hour for mainnet (on a db.r5.xlarge RDS instance). We recommend running this upgrade in a non-live environment to allow the migration to finish before proceeding.

---

### Algorand Indexer Update: 2.9.0-rc2

#### Highlights

An update to indexer to match the update to go-algorand.

#### Changes

Update go-algorand submodule.

---

### Algorand Indexer Update: 2.9.0-rc1

This release enables support for the V31 go-algorand consensus upgrade.

#### What’s New

- Contract to contract support
- Support for StateProof

---

### Algorand Indexer Update: 2.8.3

You cannot upgrade from indexer versions less than 2.8.0. Please see [indexer 2.8.0 release notes](https://github.com/algorand/indexer/releases/tag/2.8.0) for details. Upgrading from 2.8.0 to 2.8.3 is fully supported. We will not be supporting indexer < 2.8.0 in future consensus releases.

---

### Algorand Indexer Update: 2.8.0

NOTE: This release of the indexer REQUIRES a full rebuild with a new database. Indexer 2.8.0 is NOT backward compatible with 2.6.5 and must be rebuilt with a new database. This release contains significant changes to unify the accounting logic used by Indexer and Algorand.

---

### Fast Catchup not working for our node on MainNet

We adjusted relay records to remove some that were showing errors at the end of the month, so I would be interested to hear if this is still an issue for people.

---

### MainNet and TestNet Upgrade: v2.1.3

There is a one time accounts db migration that will take a few minutes. It should start up normally once this is complete.
