Skip to content

Conversation

MohammedAlabd
Copy link
Member

No description provided.

magdhz and others added 12 commits June 26, 2025 12:35
made some edits

---------

Co-authored-by: MohammedAlabd <[email protected]>
Co-authored-by: pbillingsby <[email protected]>
Co-authored-by: PBillingsby <[email protected]>
changed some definitions in terminology, updated some language in index.
**Problem**
We would like to differentiate between instances of restaking cranker
running against different Solana clusters but lack the ability to do so.

**Solution**
- Wire through the `cluster` arg to `datapoint_info!` calls as a tag

---------

Co-authored-by: Aoi Kurokawa <[email protected]>
…to-foundation#245)

- While running cranker on devnet, I've noticed some errors like below:


[2025-06-01T23:27:29Z ERROR jito_vault_cranker::vault_handler]
Transaction failed after 10 retries: Error { request:
Some(SendTransaction), kind: RpcError(RpcResponseError { code: -32002,
message: "Transaction simulation failed: Error processing Instruction 1:
custom program error: 0x3ff", data:
SendTransactionPreflightFailure(RpcSimulateTransactionResult { err:
Some(InstructionError(1, Custom(1023))), logs: Some(["Program
ComputeBudget111111111111111111111111111111 invoke [1]", "Program
ComputeBudget111111111111111111111111111111 success", "Program
Vau1t6sLNxnzB7ZDsef8TLbPLfyZMYXH8WTNqUdm9g8 invoke [1]", "Program log:
Instruction: CrankVaultUpdateStateTracker", "Program log:
VaultOperatorDelegationUpdate is not needed", "Program
Vau1t6sLNxnzB7ZDsef8TLbPLfyZMYXH8WTNqUdm9g8 consumed 13514 of 202850
compute units", "Program Vau1t6sLNxnzB7ZDsef8TLbPLfyZMYXH8WTNqUdm9g8
failed: custom program error: 0x3ff"]), accounts: None, units_consumed:
Some(13664), return_data: None, inner_instructions: None,
replacement_blockhash: None }) }) }


- To avoid sending failed transaction, we should check the state of
`VaultOperatorDelegation` before cranking
- Add checking `vault_operator_delegation.check_is_already_updated`
before sending crank ix

https://github.com/jito-foundation/restaking/blob/8469519a42205b8609f08b5734746635ddd8692f/vault_core/src/vault_operator_delegation.rs#L63-L77

---------

Co-authored-by: Coach Chuck <[email protected]>
…undation#237)

- can deploy `jito-restaking-cli`, `jito-shank-cli` (in the future)
- support `x86_64-unknown-linux-gnu`, `x86_64-apple-darwin`,
`x86_64-pc-windows-msvc`

---------

Co-authored-by: Coach Chuck <[email protected]>
- being able to set `fee_admin` to new_admin

---------

Co-authored-by: Christian Krueger <[email protected]>
Co-authored-by: Evan B <[email protected]>
…LI (jito-foundation#238)

- `jito-tip-router`, `ncn-template` use mostly same logic for generating
IDL, so after publishing `jito-shank-idl` crate, we can remove these
code from each repo.
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.

5 participants