Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indexer-agent cannot close an allocation for an unsupported network #894

Open
madumas opened this issue May 10, 2024 · 1 comment
Open

Comments

@madumas
Copy link

madumas commented May 10, 2024

Closing an allocation for a network that isn't officially supported by the network results in an error. Here for bsc:

{"level":20,"time":1715351792424,"pid":1,"hostname":"indexer-agent-6cdd4d69df-d88q7","name":"IndexerAgent","component":"ActionManager","function":"executeApprovedActions","protocolNetwork":"eip155:42161","results":[{"actionID":3672,"failureReason":"Failed to prepare tx call data: Failed to resolve CAIP2 ID from the provided network alias: bsc","protocolNetwork":"eip155:42161"}],"msg":"Completed batch action execution"}

This appears to be caused by the method Caip2ByChainAlias that uses hardcoded mappings. This is problematic because with sunrise, indexers are expected to create allocations for unsupported networks, and handle queries for them. Without the ability of closing the allocations, indexers cannot collect query fees.

@jhjhjh94
Copy link

Ref : #836

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants