Fetch client for Indexer

Generated IndexerClient for Algorand based on the OpenAPI Specification. See the upstream repository for more information.

npm install @awesome-algorand/indexer-fetch --save

import {IndexerClient} from '@awesome-algorand/indexer-fetch';

const client = new IndexerClient({
    BASE: 'https://testnet-idx.algonode.cloud/',
})

Indexer 3.1.0 uses Conduit for data loading. This is a change from the 2.x version, which managed data loading internally. See our Using Conduit to Populate an Indexer Database tutorial for more information on how to use Conduit.

This release adds a signature to the checksum file to help verify the integrity of a build.

1. Install the Algorand signing key from keys.openpgp.org or . Using GnuPG this is done with the following command:

   gpg --keyserver keys.openpgp.org --search-keys [email protected]

2. Refresh keys if necessary. In the event of a security breech, we will revoke the key. To account for this, simply refresh the key:

   gpg --keyserver keys.openpgp.org --refresh-keys

3. Download checksums.txt.sig and checksums.txt and verify the signature:

   gpg --verify checksums.txt.sig checksums.txt

4. Download one or more release archives and verify the checksum:

   sha256sum -c < checksums.txt

• 8f347f7 Add gpg signature to checksum file. (#1573)
• f3e54d6 Mention Conduit in DB open error message. (#1569)
• e47b81f Update goreleaser release notes. (#1568)
• d9c41d9 ci: fix release notes template formatting. (#1571)

Full Changelog: https://github.com/algorand/indexer/compare/v3.1.0...v3.2.0

Docker images for this release are available on Docker Hub.