Skip to content

Report this build as Cookie 4.1.3 - #7

Merged
sense112 merged 5 commits into
cookie/4.1.2from
cookie/4.1.3-client-14
Nov 10, 2026
Merged

sense112 merged 5 commits into
cookie/4.1.2from
cookie/4.1.3-client-14

Conversation

@sense112

Copy link
Copy Markdown
Collaborator

Summary

  • Cargo version is 4.1.3. ClientId::this_client() is Cookie.
  • Agave main already uses client ids 8 through 13 (Rakurai, HarmonicFiredancer, HarmonicAgave, HarmonicFrankendancer, FireBAM, Raiku). Cookie is 14, the next free id. Those upstream names are in the enum too, so a later rebase matches main.
  • solana --version, getVersion, and gossip show 4.1.3 with client Cookie. A stock 4.1.2 node shows client Unknown(14).

Test plan

  • cargo test -p solana-version --features agave-unstable-api --lib for the client id tests
  • Build from this branch and confirm solana --version shows 4.1.3 and client:Cookie
  • Confirm solana gossip shows client Cookie

sense112 and others added 5 commits November 10, 2026 23:14
…tring"

This reverts commit f8a0c3b, reversing
changes made to ca378e0.
Gossip, getVersion, and solana --version all read this Cargo version.

Co-authored-by: Cursor <cursoragent@cursor.com>
Gossip, getVersion, and solana --version all read this version. The cookie release number rides in the client id, because Agave's prerelease tag cannot store it.

Co-authored-by: Cursor <cursoragent@cursor.com>
The Cargo version is a normal patch bump. The client id is Cookie, which is the field gossip already carries for Jito and the other clients.

Co-authored-by: Cursor <cursoragent@cursor.com>
Agave main already assigns 8 through 13 to Rakurai, Harmonic, FireBAM, and Raiku.

Co-authored-by: Cursor <cursoragent@cursor.com>
@sense112
sense112 merged commit bd2ae21 into cookie/4.1.2 Nov 10, 2026
1 check passed
@sense112
sense112 deleted the cookie/4.1.3-client-14 branch November 10, 2026 21:48
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