Repository navigation
BUG: Unable to get past events #744
Description
Describe the bug
Unable to get past events for a stream when starting a new node up on another computer.
To Reproduce
I have one ceramic-one node running which is issuing events to a stream.
On another computer I spin up a ceramic-one node and indicate interest in that streamID
I can call curl -v http://localhost:5101/ceramic/experimental/interests and see that there is some data.
But when I call curl -v http://localhost:5101/ceramic/experimental/events/model/<stream_id> It returns {"events":[],"resumeOffset":0,"isComplete":true}.
Expected behavior
I expect it to return the latest events in chronological order.
All I am trying to do is have one ceramice node issuing events. Then anyone can spin up a node and listen to those events and get past events too from latest to oldest.
Ceramic versions
0.56.0
Machine, OS, browser information (please complete the following information):
Macbook, Sequoia 15.6.1
Activity
m0ar commentedon Dec 2, 2025
Hey @TheGreatAlgo! 👋
The
/ceramic/experimental/interestsroute returns which models the node is interested to sync with other peers, so what you're seeing aren't MIDs (Model Instance Documents, i.e., streams implementing the model).Not sure what's going on with the other route though, but honestly I've never used it as it's not really practical. What I would recommend is using the FlightSQL API instead, which is probably what you want because it actually decodes the data!
Here is an example where one of our projects is using the FlightSQL API through the
@ceramic-sdk/flight-sql-clientNPM package to stream incoming events: https://github.com/desci-labs/desci-codex/blob/main/packages/node/src/events.tsYou can also try the FlightSQL API out locally with the
rust-ceramicbinary. The syntax is a bit gnarly, but here is an example where I query for events in our model for academic publishing: https://gist.github.com/m0ar/1e5a80d889fb427f5b880a72c079c72c