You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am running safe-transaction-service instances for multiple Avalanche L1s and I don't understand how the ERC-20 token list is indexed.
For example, the Safe Transaction Service instance I deployed for the Lamina1 blockchain has successfully parsed this ERC-20 event:
This result in the ERC-20 not showing in the "Assets" tab of the Safe Wallet UI.
I can always create the token manually but what I don't understand is that using the same setup on some other Avalanche L1s (e.g.: Meld), the tokens related to the indexed ERC-20 events are automatically created in the database and thus visible in the Safe Wallet UI.
Describe the bug
I am running
safe-transaction-service
instances for multiple Avalanche L1s and I don't understand how the ERC-20 token list is indexed.For example, the Safe Transaction Service instance I deployed for the Lamina1 blockchain has successfully parsed this ERC-20 event:
This corresponds to this Tx: 0xcadb7277052db61d3da45d3db4c4984142592a3506a772fc2fe77d102af266b0 which is indeed a Safe Smart Account receiving 1 ERC-20 token.
But no token has been created in the database:
This result in the ERC-20 not showing in the "Assets" tab of the Safe Wallet UI.
I can always create the token manually but what I don't understand is that using the same setup on some other Avalanche L1s (e.g.: Meld), the tokens related to the indexed ERC-20 events are automatically created in the database and thus visible in the Safe Wallet UI.
AFAIK all necessary JSON-RPC are available on the configured RPC.
Is there something I'm missing here?
The text was updated successfully, but these errors were encountered: