Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

Add gossip notifications / cluster node notifications to geyser #32934

Closed
linuskendall opened this issue Aug 22, 2023 · 5 comments
Closed

Add gossip notifications / cluster node notifications to geyser #32934

linuskendall opened this issue Aug 22, 2023 · 5 comments
Labels
community Community contribution stale [bot only] Added to stale content; results in auto-close after a week.

Comments

@linuskendall
Copy link

Problem

To avoid having lite clients like (https://github.com/blockworks-foundation/lite-rpc) participate in gossip and causing further # of gossip clients increasing we would like to be able to get notifications via geyer on gossip data / gossip updates.

This would be required to replace the getClusterNodes RPC call.

Proposed Solution

Add a geyser notification for gossip update notifications.

@linuskendall linuskendall added the community Community contribution label Aug 22, 2023
@buffalu
Copy link
Contributor

buffalu commented Aug 26, 2023

+1

do you need raw gossip stream, what's inserted into table, or just access to the data structures for gossip?

@lijunwangs
Copy link
Contributor

Can you elaborate on the requirements of "gossip data" and "gossip updates"?

@godmodegalactus
Copy link
Contributor

We just need node information for all the nodes in the cluster especially those who will produce blocks during an epoch. Same as information we get by using the method 'getClusterNodes' on Solana Json rpc. We would also like to know epoch stakes for each validator but that is optional. Epoch stakes will be used to recalculate the leader schedule.

@musitdev
Copy link

musitdev commented Jan 2, 2024

I've created a POC to test the cluster node notification with geyzer in this PR #34618.

@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Jan 2, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2025
@behzadnouri
Copy link
Contributor

I reopened this on agave side: anza-xyz#4413
@gregcusack is working on this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community Community contribution stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

6 participants