feat/592: Validate length and checksum of fetched masp param

[jurevans]

Resolves #592

This PR validates the fetched MASP param before storing it. This will reject the promise and prevent an invalid param from being stored should length or checksum not match.

TESTING

• In packages/shared/lib/src/sdk/mod.ts

  namada-interface/packages/shared/lib/src/sdk/mod.ts

  Lines 21 to 40 in e160a31

  	const MASP_PARAM_ATTR: Record<
  	MaspParam,
  	{ length: number; sha256sum: string }
  	> = {
  	[MaspParam.Output]: {
  	length: 16398620,
  	sha256sum:
  	"ed8b5d354017d808cfaf7b31eca5c511936e65ef6d276770251f5234ec5328b8",
  	},
  	[MaspParam.Spend]: {
  	length: 49848572,
  	sha256sum:
  	"62b3c60ca54bd99eb390198e949660624612f7db7942db84595fa9f1b4a29fd8",
  	},
  	[MaspParam.Convert]: {
  	length: 22570940,
  	sha256sum:
  	"8e049c905e0e46f27662c7577a4e3480c0047ee1171f7f6d9c5b0de757bf71f1",
  	},
  	};

  modify these values to invalidate them (either length or hash, length is checked first!)
• Rebuild the shared package: yarn wasm:build (Even though these changes are 100% TS, they are a part of shared lib and will not auto-reload in dev mode)
• Start Namadillo with yarn dev:proxy (bypasses CORS issue with localhost)
• If you have already successfully downloaded MASP params, just comment out the lines below in useSdk to force a download on next refresh:

  namada-interface/apps/namadillo/src/hooks/useSdk.tsx

  Lines 60 to 62 in e160a31

  	if (hasMaspParams) {
  	return masp.loadMaspParams("").catch((e) => console.error(`${e}`));
  	}

• You should see errors for each param that has issues. Currently if any one of these fails, hasMaspParams() will return false, so it will retry all of them on next refresh.
• Also, you can run yarn dev locally (without the proxy) which will trigger the retry behavior, it is currently configured to retry a total of 3 times with 3 second intervals in between before failing

TODO

• How should we respond to a MASP param validation failure? One option would be to simply prompt the user to try again, perhaps we could have a warning modal with a Retry button that invokes the download again.

NOTES

• What could cause an invalid MASP param download?
  • If a download is interrupted due to connectivity issues, the promise will likely just hang
  • If the user is running this locally and overrides the trusted setup params URL, they could be loading invalid params
    • If the length is valid, it will then check the checksum, which must match our constants
  • This feature is for piece of mind, so that the user can be sure they are using the trusted params. Only the trusted params will successfully be stored in IndexedDB

[pedrorezende]

LGTM!

[pedrorezende]

Nitpick, but more an idea. What do you think of using QueryStatus type from @tanstack/react-query instead? So we can make this loading state type standard across the app

[jurevans]

Done!

[pedrorezende]

Can we add a comment telling from where these numbers / hashes come from?

[jurevans]

Yep, thanks!