https://github.com/anza-xyz/solana-rpc-client-extensions
Rust and JS code to perform Solana RPC's GetStakeActivation client-side
https://github.com/anza-xyz/solana-rpc-client-extensions
Last synced: about 2 months ago
JSON representation
Rust and JS code to perform Solana RPC's GetStakeActivation client-side
- Host: GitHub
- URL: https://github.com/anza-xyz/solana-rpc-client-extensions
- Owner: anza-xyz
- License: apache-2.0
- Created: 2024-08-07T14:06:35.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-03-10T15:52:35.000Z (3 months ago)
- Last Synced: 2025-03-19T05:48:38.896Z (2 months ago)
- Language: TypeScript
- Size: 112 KB
- Stars: 12
- Watchers: 1
- Forks: 8
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome - anza-xyz/solana-rpc-client-extensions - Rust and JS code to perform Solana RPC's GetStakeActivation client-side (TypeScript)
- awesome-svm - GitHub
README
# solana-rpc-client-extensions
Rust and JS code to perform Solana RPC calls on the client-side. Currently
covers the following RPC calls and packages:
| RPC Call | Rust Package | JS Package | JS v1 Package |
| --- | --- | --- | --- |
| `GetStakeActivation` | `solana-rpc-get-stake-activation` | `@anza-xyz/solana-rpc-get-stake-activation` | `@anza-xyz/solana-rpc-get-stake-activation-v1` |
## Other Languages
Any language with libraries to interact with Solana RPC nodes also needs this
additional client-side logic, but the Anza team only maintains Rust and JS
packages.
Here are other supported languages, and their associated repositories.
| Language | Repository |
| --- | --- |
| Go | https://github.com/skport/solana-rpc-client-extensions-go |
## Motivation
The `GetStakeActivation` RPC code is being removed in Agave 2.0, but users may
still need to get access to stake activation data.
The RPC method was removed because it's possible to get calculate the status of
a stake account on the client-side.
This repo contains Rust and JS code for mimicking `GetStakeActivation` on the
client-side. See the `examples/` in each repo to see how to use them, or read
the source code!