Skip to content

fix(serve): handle new spec block-structure changes#504

Open
lancevincentsalera wants to merge 12 commits intotxpipe:mainfrom
lancevincentsalera:fix/block-structure-spec-change
Open

fix(serve): handle new spec block-structure changes#504
lancevincentsalera wants to merge 12 commits intotxpipe:mainfrom
lancevincentsalera:fix/block-structure-spec-change

Conversation

@lancevincentsalera
Copy link
Copy Markdown
Contributor

@lancevincentsalera lancevincentsalera commented May 19, 2025

This PR addresses spec block structure changes from utxorpc/spec#155 and utxorpc/spec#154.

CC: @SebastienGllmt, @scarmuega

@lancevincentsalera lancevincentsalera changed the title fix(serve): new spec block structure changes related errors fix(serve): handle new spec block-structure changes May 19, 2025
Comment thread src/serve/grpc/watch.rs
.intersect
.iter()
.map(|x| ChainPoint::Specific(x.index, x.hash.to_vec().as_slice().into()))
.map(|x| ChainPoint::Specific(x.slot, x.hash.to_vec().as_slice().into()))
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR properly adds the changes in the output, but isn't handling the new behavior in the input. The goal of #154 is that you should be able to create requests on more than just the slot number (since you might only know the block height, or only know the block hash)

Copy link
Copy Markdown
Contributor Author

@lancevincentsalera lancevincentsalera May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @SebastienGllmt , thanks for this. I made changes to the fetchBlock endpoint, can you check if the implementation has more to improve or looks good already? I tested this on my side and it works fine now. Many thanks!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, LGTM!

@scarmuega scarmuega force-pushed the main branch 2 times, most recently from 295b558 to 09d0b81 Compare January 28, 2026 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants