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

New streamed Ordinals Activities are not POST to endpoint #378

Open
tegaget opened this issue Dec 8, 2024 · 0 comments
Open

New streamed Ordinals Activities are not POST to endpoint #378

tegaget opened this issue Dec 8, 2024 · 0 comments
Assignees

Comments

@tegaget
Copy link

tegaget commented Dec 8, 2024

I have been testing this extensively. If I manually scan blocks, it will post to end point:
$ ordhook scan blocks --interval 767430:767753 --post-to=http://localhost:3000/api/events --config-path=./Ordhook.toml

This works as expected. My node js listens to endpoint and successfully processes. Great.

However, when I run ordhook as service to process realtime live ordinal data, the POST is never made and my node js never sees it to process.

$ ordhook service start --post-to=http://localhost:3000/api/events --config-path=./Ordhook.toml

My ordhook is fully synced and working well. It successfully detects ZMQ from my node and processes automatically new ordinal data. I see it in console. However, I believe ordhook service is never POST to HTTP endpoint /api/events like the "ordhook scan blocks" does.

Any ideas on what is going on here? I am almost tempted to make my own console listener and process new blocks by spawning a "ordhook scan blocks" process to get this processed to POST.

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

No branches or pull requests

2 participants