Make use of NEAR indexer framework if/where necessary

[Thesephi]

In line with the initiative of caching certain data in a separate db so that we don't have to directly query on-chain data every time, there's the official NEAR indexer framework that might help as a starting point: https://github.com/near/near-indexer-for-explorer#shared-public-access

Let's see if we can make use of this framework at all, or not.

[khanetor]

In line with the initiative of caching certain data in a separate db so that we don't have to directly query on-chain data every time, there's the official NEAR indexer framework that might help as a starting point: https://github.com/near/near-indexer-for-explorer#shared-public-access

Let's see if we can make use of this framework at all, or not.

This is meant as a snapshot of the blocks on the explorer, and it is read-only, so we cannot store custom data on it.

Regarding a separate db, I intend to use Supabase if necessary. Regarding search feature, Algolia seems to fit nicely there. Supabase Edge function will push the update to Algolia. Later on, we can use Supabase to interact with the contract for consistency as well.

[Thesephi]

Yeah, the idea was to query on-chain data without having to directly query against the chain itself. Probably suitable for:

• transactions (signer, contract-chain, final result)
• quick account checkup esp. when we only need to display some account info without doing any manipulation or token transfer

Re. Superbase and Algolia: all sound good, maybe we'll want to make it extra explicit to the users as some may (rightfully) expect that we retrieve everything directly from chain.

[khanetor]

Yes, we will want to display all those tech stacks in the README. This can be a pioneer in how to use Blockchain in existing application.