Namespace Range Endpoint Integration#328
Namespace Range Endpoint Integration#328Sneh1999 wants to merge 9 commits intocelo-integration-rebase-14.1from
Conversation
There was a problem hiding this comment.
Pull request overview
This PR integrates the Namespace Range endpoint from the Espresso SDK to enable faster and more efficient HotShot block fetching. The implementation replaces the previous streaming API approach with a batch range fetching mechanism.
Changes:
- Upgraded Espresso SDK from v0.3.2 to v0.3.4
- Replaced streaming API with FetchNamespaceTransactionsInRange for batch block fetching
- Removed Rust dynamic library dependencies from Docker build process (no longer needed in v0.3.4)
- Updated Espresso dev node Docker image to release-20251120-lip2p-tcp-3855
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| go.mod | Updated Espresso SDK dependency to v0.3.4 |
| go.sum | Updated checksums for new SDK version |
| espresso/streamer.go | Replaced streaming API with FetchNamespaceTransactionsInRange for batch fetching; removed streamHotShotRange function |
| espresso/streamer_test.go | Updated mock implementation to support FetchNamespaceTransactionsInRange; removed FetchTransactionsInBlock mock |
| ops/docker/op-stack-go/Dockerfile | Removed Rust library fetching (no longer required) |
| kurtosis-devnet/enclaver/Dockerfile | Removed Rust library fetching (no longer required) |
| kurtosis-devnet/enclaver/Dockerfile.nonEnclave | Removed Rust library fetching (no longer required) |
| espresso/docker/op-stack/Dockerfile | Removed Rust library fetching (no longer required) |
| espresso/docker/op-geth/Dockerfile | Removed Rust library fetching (no longer required) |
| justfile | Updated Espresso dev node image reference |
| espresso/.env | Updated Espresso dev node image reference |
| espresso/environment/optitmism_espresso_test_helpers.go | Updated Espresso dev node image reference |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
d15809d to
168426e
Compare
3a1310c to
b96622c
Compare
README_ESPRESSO.md
Outdated
|
|
||
|
|
||
| ## Generating alloc.json file | ||
| First go to `espresso-network` repo and from inside `espresso-dev-node` folder run: |
There was a problem hiding this comment.
Can't we do this with the existing espresso-dev-node docker image we are already downloading?
There was a problem hiding this comment.
I tried it, didnt work for me! Only the cargo binary prints out the allocs.json it seems
There was a problem hiding this comment.
docker run -it --rm ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:release-fix-cors /bin/espresso-dev-node --sequencer-api-port 24000 --l1-deployment dump --path .There was a problem hiding this comment.
This command seems to output JSON for me without issue. Give it a try?
There was a problem hiding this comment.
Thanks Theo, it works. I will update the README
Description
Integrates the Namespace Range endpoint for faster hotshot block fetching