Title: feat: Catchup vs follow · Issue #2803 · evstack/ev-node · GitHub
Open Graph Title: feat: Catchup vs follow · Issue #2803 · evstack/ev-node
X Title: feat: Catchup vs follow · Issue #2803 · evstack/ev-node
Description: In ev-node once we integrate directly with celestia-node then we should separate catchup from follow. This means that we should use the subscribe API on celestia node. When we notice that there is a new blob at a higher height then we ha...
Open Graph Description: In ev-node once we integrate directly with celestia-node then we should separate catchup from follow. This means that we should use the subscribe API on celestia node. When we notice that there is ...
X Description: In ev-node once we integrate directly with celestia-node then we should separate catchup from follow. This means that we should use the subscribe API on celestia node. When we notice that there is ...
Opengraph URL: https://github.com/evstack/ev-node/issues/2803
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: Catchup vs follow","articleBody":"In ev-node once we integrate directly with celestia-node then we should separate catchup from follow. This means that we should use the subscribe API on celestia node. When we notice that there is a new blob at a higher height then we have in our store, then we start catchup, go from local da height to highest da height. This would be the same with p2p, except that with the event driven approach we are treating catchup and follow as the same. \n\n\nblocked by https://github.com/evstack/ev-node/issues/2796\n\n\n","author":{"url":"https://github.com/tac0turtle","@type":"Person","name":"tac0turtle"},"datePublished":"2025-11-03T10:34:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2803/ev-node/issues/2803"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:a1d110e5-8ccd-6ed9-b127-30fa6046e043 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C8F6:3F7AE:ED81E:14AEE3:6980E8F8 |
| html-safe-nonce | 874c9abe4ef4802367ef9356455e96cc69192eaf5cd2516e5a94690ccb34b942 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDOEY2OjNGN0FFOkVEODFFOjE0QUVFMzo2OTgwRThGOCIsInZpc2l0b3JfaWQiOiI4NzgyOTk3MzAzNjIwMzMxNzY4IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 553a8d45f25eee7cf83291d8414f4266af4f4e09b572e0ca9505cd56cb0278ab |
| hovercard-subject-tag | issue:3581462928 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/evstack/ev-node/2803/issue_layout |
| twitter:image | https://opengraph.githubassets.com/97bef087a5f47599a6d8c2a793e0ee238121bb89fb70b02972cb475e819570d4/evstack/ev-node/issues/2803 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/97bef087a5f47599a6d8c2a793e0ee238121bb89fb70b02972cb475e819570d4/evstack/ev-node/issues/2803 |
| og:image:alt | In ev-node once we integrate directly with celestia-node then we should separate catchup from follow. This means that we should use the subscribe API on celestia node. When we notice that there is ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | tac0turtle |
| hostname | github.com |
| expected-hostname | github.com |
| None | aaf8d4a8e86300179375c44c83488bc74585c21f81b72377699d5e6c4b00d1b1 |
| turbo-cache-control | no-preview |
| go-import | github.com/evstack/ev-node git https://github.com/evstack/ev-node.git |
| octolytics-dimension-user_id | 120482652 |
| octolytics-dimension-user_login | evstack |
| octolytics-dimension-repository_id | 335571729 |
| octolytics-dimension-repository_nwo | evstack/ev-node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 335571729 |
| octolytics-dimension-repository_network_root_nwo | evstack/ev-node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 0b50c4d33bc796ea7d05dba2f7cf29956c2e8265 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width