bugfix: make sure nym-api can handle non-cw2 (or without detailed build info) compliant contracts

[jstuczyn]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
nym-explorer	⬜️ Ignored (Inspect)			Jun 11, 2024 4:39pm
nym-next-explorer	⬜️ Ignored (Inspect)			Jun 11, 2024 4:39pm

[tommyv1987]

Testing Completion Date: [12/06/2024]

Testing Steps Performed:

1. Use the latest release/chomp contracts and deploy these to QA
2. If the contract was not found, the API would complain of invalid contracts, thus not starting the rest of the operations of the API (network monitor / rewarding etc)

Jun 11 16:27:34 qa-v2-nym-api bash[1352642]: 2024-06-11T16:27:34.551Z ERROR nym_api::nym_contract_cache::cache::refresher > Failed to refresh validator cache - Abci query failed with code 6 - address n14y2x8a60knc5jjfeztt84kw8x8l5pwdgnqg256v0p9v4p7t2q6eswxyusw: no such contract: unknown request

This fixes the issue (even if some contracts aren't uploaded on chain it doesn't prohibit the api from working - caveat, the essential vesting and mixnet contract are required)

Validation:

• ✅ Test Passed
• [ 🔴 ] Issues Found

Notes (if any):
N/A

Attachments (if applicable):
N/A