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

Websocket API always returns empty events #2167

Closed
CyrusVorwald opened this issue Nov 15, 2024 · 1 comment
Closed

Websocket API always returns empty events #2167

CyrusVorwald opened this issue Nov 15, 2024 · 1 comment
Assignees

Comments

@CyrusVorwald
Copy link

I think there is a bug in the websocket API. When subscribing to address transactions using address_tx_update, the response includes event_count. Even if event_count is greater than 0, It seems to always return empty events: [] array in the transaction data. This can be reproduced by monitoring contract call transactions that emit events via the websocket API.

@zone117x
Copy link
Member

Events are not included in the transaction object. The number of events are often too large to reasonable fit. You can use the /extended/v1/tx/events endpoint to fetch and filter/paginate through transaction events.

@zone117x zone117x closed this as not planned Won't fix, can't repro, duplicate, stale Nov 19, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in API Board Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants