Properly Index Relayer Stats and Collator Reward Indexing#271
Conversation
|
@dharjeezy Let's also add these fixes to this PR |
introduce request commitment in asset teleport per transaction indexing for relayer rewards and collator rewards schema renaming changes
@dharjeezy missing fixes for the issue linked in this comment |
they are actually in my last commit |
Wizdave97
left a comment
There was a problem hiding this comment.
Let's remove TokenList indexing and it's services
remove redundant checks and type
|
@dharjeezy, let's write a migration function that would execute a migration function over multiple blocks. This handler should only be added to the hyperbridge yaml. This function should migrate the valid relayer chain stats from the old schema to the new one. The valid relayer stats can be gotten like this You can migrate it likely 10 at a time, the total count is about 572 items |
|
Also let's stop fetching the reputation token balance when indexing relayer rewards, but don't modify the entity |
remove reputation asset balance indexing
|
@dharjeezy we've decided to reindex so you can revert the relayer migration changes |
|
Let's keep this open until we are ready to reindex |
|
@dharjeezy David, [6 Mar 2026 at 09:27:40 (6 Mar 2026 at 09:27:57)]: You need to update the sdk to reflect these changes in the GraphQL queries for these RequestV2 ResponseV2 GetRequestV2 AssetTeleportedV2 TokenGatewayAssetTeleportedV2 RelayerV2 I also added a migration script But currently it doesn't migrate RelayerChainPerstat You need to restore the previous entity name and just add the V2 suffix so the script can also migrate it In the script, when copying the relayer chain per stat, only copy the items where the chain is EVM |
update sdk
b243661 to
5dad735
Compare
…ts in intentGatewayV2.service.ts
…2.service.ts imports accordingly
…umns during row insertion
|
This PR introduces proper indexing for relayers via Post Request and Response handled event. It also introduces Collator reward indexing.
closes #273