Five steps to send Arbitrum staking rewards to a treasury

To route staking rewards to a treasury on Arbitrum, check who can claim them, set the treasury as the recipient where possible, and verify the transfer on-chain. The exact route depends on the staking contract: some let a claimant choose a destination, while others send rewards to the account that staked. A treasury is a wallet used to hold funds for a group or project.

What should you check before routing rewards?

Start by identifying the staking contract, reward token and treasury address. Confirm the contract is on Arbitrum One, whose chain ID is 42161, and check the treasury address on that same network. A matching address on another network does not mean the funds are in the right place.

Read the contract’s claim rules before sending anything. Look for a recipient setting or a claim function that accepts a destination address. If rewards can only be claimed by the staking account, the process may need an authorized wallet to claim first and then transfer the tokens. For more detail on how ParaSwap relates to routing staking rewards, see this fuller guide to ParaSwap and treasury reward routing.

How do you route the rewards in five steps?

Use this sequence to set up and check the flow:

• 1. Confirm the asset and contract. Check the reward token address and the staking contract against the project’s trusted records.
• 2. Confirm treasury control. Make sure the treasury address is correct and that the people or group responsible for it approve the change.
• 3. Choose the claim path. If the contract supports a recipient, set that address to the treasury. If it does not, use an authorized claiming wallet and plan a separate transfer.
• 4. Make a small test, then set the routine. Claim or transfer a small amount, verify receipt, then repeat on the agreed schedule and check each transaction.

5. Record the result. Keep the transaction links, amount, token and date with the treasury’s records. If rewards are claimed by one wallet and sent on, record both transactions so the trail is clear.

What can go wrong, and how do you check?

The main failure points are a wrong network, a mistyped treasury address, or assuming the claim function supports a recipient when it does not. Before approving a transaction, check the network and destination in the wallet. After it confirms, check the transaction on an Arbitrum block explorer and make sure the treasury balance changed by the expected token amount.

Arbitrum transactions also require ETH for fees. The fee covers both execution on Arbitrum and the transaction data posted to Ethereum, so the amount can vary. A small test helps catch routing errors, but it does not replace checking who can change the destination or move funds later. For most groups, the clearer setup is a treasury address set directly as the claim recipient; it avoids an extra transfer and keeps fewer funds in an individual wallet.