In https://github.com/anoma/namada-interface/pull/897, we added the ability to deserialize Tx bytes in the extension. However, since the extension is currently responsible for persisting these once they are fetched, it is possible that a site to provide invalid hashes for a particular chain ID, which would prevent Tx details from displaying.
Look into a better way of providing these to the extension. It could be added to connect(), or simply invoke addTxWasmHashes(...)after a successful connection by an interface, but we would remove the getTxWasmHashes() call from the extension, meaning the interface would persist these instead
Update namadillo atom service for checksums to remove the check inside fetchWasmHashes, and persist the response from the SDK (soon to be the indexer API)
In https://github.com/anoma/namada-interface/pull/897, we added the ability to deserialize Tx bytes in the extension. However, since the extension is currently responsible for persisting these once they are fetched, it is possible that a site to provide invalid hashes for a particular chain ID, which would prevent Tx details from displaying.
connect(), or simply invokeaddTxWasmHashes(...)after a successful connection by an interface, but we would remove thegetTxWasmHashes()call from the extension, meaning the interface would persist these insteadfetchWasmHashes, and persist the response from the SDK (soon to be the indexer API)