The advantage of this approach would be saving an on chain call on the UI, the disadvantage being this implies a smart contract deployment + not sure about how computationally heavy the added logic is. The UI approach is faster in terms of going live with the fix, but I don't think this is an urgent issue so we can decide based on the other criteria.
Description
Alternative for UI multicall https://github.com/NexusMutual/frontend-next/pull/1049 to support https://github.com/NexusMutual/frontend-next/issues/1044.
The advantage of this approach would be saving an on chain call on the UI, the disadvantage being this implies a smart contract deployment + not sure about how computationally heavy the added logic is. The UI approach is faster in terms of going live with the fix, but I don't think this is an urgent issue so we can decide based on the other criteria.
Testing
NexusViewer implementation address: 0x6874ABAf1c8a1694b08066e5bB38487D680fa38d NexusViewer implementation ABI:
getClaimableNXM
call should returnstakingPoolManagerIsNXMLockedForMV
in the resultOR
HARDHAT_NETWORK=localhost node scripts/get-claimable-nxm.js
Checklist