Avalanche Builder Hub published a practical flow for native AVAX staking on the P-Chain using Fireblocks. Fireblocks does not provide a dedicated Avalanche staking feature, but its Raw Signing API can sign arbitrary P-Chain transactions. That makes it possible to construct the staking workflow while keeping keys inside an existing custody setup.
The process starts by placing AVAX on the required chain. Funds can be exported from the C-Chain and imported to the P-Chain before the staking transaction is assembled. The unsigned payload is then sent through Fireblocks Raw Signing, and the signed transaction is submitted to the Avalanche network.
The same approach can be used for delegation or for creating a validator transaction. The Builder Hub article includes a working TypeScript flow, targeting infrastructure teams that need direct P-Chain access while preserving enterprise custody and signing controls.
The practical point is that the lack of a dedicated staking button in Fireblocks does not prevent native Avalanche staking operations. Raw Signing acts as the low-level interface, while transaction construction, staking parameters and validation remain the responsibility of the integration and its operators.