[tracking] MASP integration readiness

[cwgoes]

dependencies:

• Remove hardcoded tokens from MASP rewards #2283
• MASP validity predicate #56
• Shared MASP Transaction Code #302
• Integrate Inflation Model with MASP Burn and Mint #303
• Add E2E Tests for MASP Wallet #305
• Handle MASP Transactions Across Epoch Boundaries #307
• spec: document masp storage key layout #480
• spec: clean up masp spec #483
• client transfer check --signer or --signing-key for shielded transfer #862
• Missing MASP Transaction Validation #1373
• Unsafe MASP Transaction Validation #1374
• MASP CI False Positives and Negatives #1376
• Separate accounting for shielded rewards #1730
• MASP CI False Positives and Negatives #1376
• Refactor transfer transaction creation and WASM to split shielded and transparent transfers #1677
• Masp/Base boundary conditions #1962
• Unable to query shielded balances of tokens received over IBC after updating epoch #2087
• Wallet updates (doesn't check the latest epoch scanned) /cc @Fraccaman is there an issue for this?
• MASP epoch boundary issue /cc @Fraccaman is there an issue for this? do we know the underlying problem?
• MASP VP needs to be converted to native code /cc @Fraccaman is there an issue for this?

---

This issue tracks feature-completeness of the MASP integration, including shielded set rewards. The MASP integration is feature-complete if and only if:

• Users can send transparent-to-shielded, shielded-to-shielded, and shielded-to-transparent transactions with any token on Namada
• The ledger correctly computes rewards as per the specs
• Users can claim rewards
• The client and SDK handle all MASP-related transactions correctly and consistently, including claiming rewards
• All related code is tested, believed to be complete, and internally audited by at least two people other than the author.

Please add any dependencies that you believe are necessary to meet these requirements in the list above.