search

sygmaprotocol / sygma-explorer-indexer

Backend service that collects bridging events for bridging explorer ui
GNU Lesser General Public License v3.0
3 stars 2 forks source link

Release Explorer v1.0.9 #170

Closed MakMuftic closed 6 months ago

MakMuftic commented 7 months ago

Details

This version brings a few smaller bug fixes.

Full changelog for specific changes

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/153 fix is now done by https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/168 & https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/156

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/152 fixed for existing duplicates; Only 2 new entries after removal image.png

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/161 - not for QA. Notifications are working as is

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/164 - fixed behavior and fixed the issue that caused fees to fail. Cannot be tested

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/166 - indexing now starts after txHash block + 10 image.png

LyonSsS commented 7 months ago

https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/156 is now fixed image.png

image.png
LyonSsS commented 7 months ago

Issue https://github.com/sygmaprotocol/sygma-explorer-indexer/pull/168 is still not optimal and it should be closed after implementing https://app.zenhub.com/workspaces/sygma-protocol-62f126a54b7d5a55203732f0/issues/gh/sygmaprotocol/sygma-explorer-indexer/178 This is the last open issue on this epic

tcar121293 commented 6 months ago

We decided that we will skip the implementation of https://app.zenhub.com/workspaces/sygma-protocol-62f126a54b7d5a55203732f0/issues/gh/sygmaprotocol/sygma-explorer-indexer/178 for now, since this will cause only an issue on our testnet, because only there we have this specific case where one resourceID has different decimals on different networks

LyonSsS commented 6 months ago

Thanks for letting me know. Then this ticket is considered as closed from QA view.