MASP indexer integration

[mateuszjasiuk]

I don't think there is an easy way to test this for now :/ But I think as long as this does not break other features we can merge it.

Okay!
Make sure you test against 0.44.0
So to test shielded sync w/o masp indexer you can:

• shield some nam using CLI(localnet example)

target/debug/namada wallet gen --shielded --alias albert-shielded --base-dir .namada/validator-0
target/debug/namada wallet gen-payment-addr --alias albert-pa1 --key albert-shielded --base-dir .namada/validator-0
target/debug/namada client shield --source albert --target albert-pa1 --token nam --amount 1000  --base-dir .namada/validator-0
# To get the viewing key
target/debug/namada wallet find --alias albert-shielded --base-dir .namada/validator-0

• Add this to App.tsx in namadillo(with missing imports)

  useEffect(() => {
    const shieldedSync = async (): Promise<void> => {
      const vk =
        "YOUR_VK";
      const sdk = await getSdkInstance();
      await sdk.rpc.shieldedSync([vk]);
    };

    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    (window as any).shieldedSync = shieldedSync;
  });

• run await window.shieldedSync() in namadillo console, you should see progress logged
• 👀

To test with masp indexer you can do the same setup but also run masp_indexer locally.

• running instructions
• if you want to run masp indexer alongsinde indexer(it's a bit of a headache for now) you need to change ports :/ I will change ports in regular indexer soon so there are no conflicts during development

    command: ["postgres", "-c", "listen_addresses=0.0.0.0", "-c", "max_connections=200", "-p", "5433"]
    expose:
      - "5433" # Publishes 5432 to other containers but NOT to host machine
    ports:
      - "5433:5433"
# AND
    ports:
      - 5000:5001
 # AND ALL
      DATABASE_URL: postgres://postgres:password@postgres:5433/masp_indexer_local

• paste MASP indexer url
  
• wait for commitment tree to get indexed
• retest

❗CLEAR CONTEXT MANUALLY BETWEEN TESTS, JUST REMOVE IT FROM IDB ❗
ALSO currently I;m getting this :(

Caused by:
    Could not deserialize the notes map JSON response at height 3017: error decoding response body: missing field `batch_index` at line 1 column 89

[jurevans]

thanks, I thought I had updated all of these :D

[mateuszjasiuk]

I've recently setup clippy, it shows all that stuff :D

[jurevans]

What do you think about mapping this to the types/args before we release? I could do a follow-up PR that adds any potential args we may want soon to our types package, that way we wouldn't have to worry about any breaking APIs after we publish. Unless there's not a use-case we'll need for this. I can look into that!

[mateuszjasiuk]

I think we can add it when we start testing transfers

[jurevans]

Weird, I'm now getting a build warning on this file, though not sure why it's happening on this branch:

warning: field `0` is never read
  --> src/crypto/zip32.rs:15:27
   |
15 | pub struct ExtSpendingKey(pub(crate) ExtendedSpendingKey);
   |            -------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |            |
   |            field in this struct

Not sure that we're using that type any more. Not a big deal on this PR, just noting!

[jurevans]

Code LGTM! Was able to test this locally, works great! I think it's fine to point to that rev for now, we can later point to the next tag that has the fixes we need.