Skip to content

feat: SubscribeNodeGroupStatus RPC for per-node-group chain status #166

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.

Sign up for GitHub

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

Closed
l0gun0v wants to merge 2 commits into from
Closed

feat: SubscribeNodeGroupStatus RPC for per-node-group chain status #166

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd4025c
feat: SubscribeNodeGroupStatus for per-node-group chain status
Jul 28, 2026
c9d08cf
Merge remote-tracking branch 'origin/master' into separation-nodecore
Sep 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions proto/blockchain.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ service Blockchain {
rpc NativeCall (NativeCallRequest) returns (stream NativeCallReplyItem) {}
rpc NativeSubscribe (NativeSubscribeRequest) returns (stream NativeSubscribeReplyItem) {}
rpc SubscribeChainStatus (SubscribeChainStatusRequest) returns (stream SubscribeChainStatusResponse) {}
rpc SubscribeNodeGroupStatus (SubscribeNodeGroupStatusRequest) returns (stream SubscribeChainStatusResponse) {}

rpc Describe (DescribeRequest) returns (DescribeResponse) {}
rpc SubscribeStatus (StatusRequest) returns (stream ChainStatus) {}
Expand Down Expand Up @@ -314,6 +315,13 @@ message ExistsSelector {
message SubscribeChainStatusRequest {
}

// SubscribeNodeGroupStatus streams the same ChainDescription events per node
// group instead of the merged per-network view: full responses and deltas are
// tagged with node_group_id, and a group's ChainStatus going unavailable is
// its removal signal. SubscribeChainStatus is unaffected.
message SubscribeNodeGroupStatusRequest {
}

message SubscribeChainStatusResponse {
ChainDescription chain_description = 1;
BuildInfo build_info = 2;
Expand All @@ -323,6 +331,10 @@ message SubscribeChainStatusResponse {
message ChainDescription {
ChainRef chain = 1;
repeated ChainEvent chain_event = 2;
// Opaque node-group id ("<client_type>:<methods_hash8>"), set on
// SubscribeNodeGroupStatus streams; always empty on SubscribeChainStatus.
// Clients must not parse it.
string node_group_id = 3;
}

message HeadEvent {
Expand Down