44 migrate to new nabla contracts

[TorstenStueber]

Closes #44

This PR implements the indexer changes for Nabla.

The changes are inspired by the according changes of the Ethereum based indexer for Nabla (see this PR: https://github.com/0xamberhq/subgraph-mumbai/pull/11).

However, there are quite a lot of necessary differences that mainly are caused by the fact that the Nabla contract addresses are hard coded in the subgraph indexer whereas we want to avoid hard coded address.

For that reason we need to reliably recognize what contracts are Nabla contracts. In the past we merely probed some methods to heuristically identify whether a contract event is caused by a specific contract type (router, swap pool, backstop pool, etc). However, this proved to be very unreliable and the indexer generated many errors.

Instead we decided to monitor Contracts.Instantiated events (see here) and then check the hash of the event causing the event and compare it with the contract metadata to correctly identify the type of contract.

Other differences are to avoid some vulnerabilities that are in the subgraph indexer code:

• correctly identify swap pools that have been added to routers (see this message)
• correctly assign swap pools for specific tokens (see https://github.com/0xamberhq/subgraph-mumbai/issues/12)

Tests

I implemented a test suite in wasm deploy (see this PR: https://github.com/pendulum-chain/wasm-deploy/pull/40).

This test suite required to run the wasm deploy test runner and foucoco-standalone locally. This also required to run the indexer (and the graphql server) locally. For that reason I added another configuration option local (otherwise subsquid will lookup the configuration for one of our chains in its archive and expects a specific genesis block – which will be different in foucoco-standalone). I am not sure whether this is the right approach

[ebma]

@TorstenStueber I pushed a new commit that updates the ABI files of the Nabla contract to the ones compiled with a later version of Solang ie. v0.3.3 instead of v0.3.2. Please be aware that this now requires you to compile your Nabla contracts with the same version of Solang before using wasm-deploy to deploy them again.

I only switched to v0.3.3. because it was the latest version available of Solang when I started testing everything one week ago. We can also roll it back if you want, but I guess it's good to stay up-to-date with the latest versions.

[TorstenStueber]

@ebma we would either need to roll it back or deploy Nabla again on Foucoco. At least the current Nabla instance we use for all testing would not work with this version of the indexer anymore.

[ebma]

Then let's deploy a new version of Nabla on Foucoco again or do you think this causes too much extra effort? AFAIK we'd would just need to change some hard-coded addresses in the portal and the rest can stay the same.

[TorstenStueber]

@pendulum-chain/devs I addresses the comments from earlier reviews.

This PR can now be properly reviewed.

[ebma]

Let's merge @TorstenStueber?