Oracles like Switchboard or Pyth need to update price data on-chain. However, the oracle itself cannot push data without a transaction. A crank is initialized with a schedule (e.g., "update BTC/USD every 5 seconds"). Keepers run crank instructions continuously, earning rewards for pushing fresh prices.
Open-source blockchains thrive on contributions. If you have found a bug or want to add a feature (like priority fee adjustment or compute unit optimization), here is the contribution workflow:
The core data structure is the Crank account. It stores: crankv2 github
Network failures happen. When they do, tasks often get stuck or run twice. Crank v2 enforces strict idempotency keys, ensuring that even if a retry is triggered, the job executes exactly once, preserving data integrity.
Even with the source code in hand, deploying Crankv2 can be tricky. Here are the top issues discussed on GitHub Issues: Oracles like Switchboard or Pyth need to update
To contribute to Crank v2, follow these steps:
For those looking to run their own infrastructure, the open-source code provides the actual bot logic required to "turn the crank." This involves a continuous loop of: It stores: Network failures happen
When you visit the official crankv2 repository on GitHub (e.g., from Switchboard or a community fork), you will typically find a Rust-based Solana program structured into several key components.