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

Add HeadId to "Greetings" message #1557

Closed
Quantumplation opened this issue Aug 10, 2024 · 0 comments · Fixed by #1622
Closed

Add HeadId to "Greetings" message #1557

Quantumplation opened this issue Aug 10, 2024 · 0 comments · Fixed by #1622
Assignees
Labels
api Items related to the Hydra client API 💭 idea An idea or feature request

Comments

@Quantumplation
Copy link
Contributor

Why

When connecting to a head, it is often helpful to know the headId. This is present in the HeadIsOpen, TxValid, etc. messages.

However, it's not in the Greetings message; That means that if we connect with ?history=no, we have no reliable message that tells us the headId.

What

Update the Greetings message to include the headId; if the hydra head is managing multiple heads, group the snapshot UTXOs by headId.

How

N/A

@Quantumplation Quantumplation added the 💭 idea An idea or feature request label Aug 10, 2024
@ch1bo ch1bo added the api Items related to the Hydra client API label Aug 28, 2024
@ffakenz ffakenz self-assigned this Sep 11, 2024
@ffakenz ffakenz closed this as completed Sep 11, 2024
@ch1bo ch1bo reopened this Sep 11, 2024
ffakenz added a commit that referenced this issue Sep 12, 2024
<!-- Describe your change here -->

Closes #1557

---

<!-- Consider each and tick it off one way or the other -->
* [x] CHANGELOG updated or not needed
* [x] Documentation updated or not needed
* [x] Haddocks updated or not needed
* [x] No new TODOs introduced or explained herafter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Items related to the Hydra client API 💭 idea An idea or feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants