# \[Proposal\] Update \`tx\_claim\_rewards\`
**URL:** https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704
**Category:** Governance Ops
**Created:** [6 June 2025 17:00 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704 "2025-06-06T17:00:51Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@brentstone](https://forum.namada.net/u/brentstone)
#### Post date: [6 June 2025 17:00 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/1 "2025-06-06T17:00:51Z")
Proposing to update the `tx_claim_rewards` wasm on-chain.
There is a known issue with the current transaction that results in asymptotic iteration within a specific code path in the presence of many redelegations. As a result, some users with many redelegations have been unable to successfully claim their rewards from certain validators. This proposal should unblock those claimers.
The new WASM has been deployed and tested on Housefire testnet with [Proposal #33](https://interface.housefire.tududes.com/governance/proposal/33).
The code used to generate the WASM for the proposal that was placed on Housefire testnet and that will be used for mainnet can be found [here](https://github.com/anoma/namada-governance-upgrades/blob/6da3b4b1835ae531589bcef65602bf3a803e1de3/update-tx-claim-rewards-2/src/lib.rs). The new `tx_claim_rewards` wasm file included in the proposal and to be written to the Namada storage was generated from [namada#4666](https://github.com/anoma/namada/pull/4666) and can be specifically found in the CI artifacts from [here](https://github.com/anoma/namada/actions/runs/15438603310/artifacts/3257474982). This is the same `claim-rewards` logic that is present in the new namada release [v101.1.1](https://github.com/anoma/namada/releases/tag/v101.1.1).
In the opinion of Heliax, it is important to update this wasm and vote this proposal through before beginning Phase 5.
---
### Author:  [@Gavin](https://forum.namada.net/u/Gavin)
#### Post date: [6 June 2025 17:08 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/2 "2025-06-06T17:08:46Z")
Knowable supports this. Keep going! ๐
---
### Author:  [@brentstone](https://forum.namada.net/u/brentstone)
#### Post date: [6 June 2025 17:38 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/3 "2025-06-06T17:38:35Z")
[Proposal #23](https://interface.namada.tududes.com/governance/proposal/23) is now on-chain!
---
### Author:  [@sirouk](https://forum.namada.net/u/sirouk)
#### Post date: [6 June 2025 17:52 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/4 "2025-06-06T17:52:13Z")
> [@brentstone](#):
>
> for mainnet
TuDudes supports this too! Thank you ๐
---
### Author:  [@zenodeapp](https://forum.namada.net/u/zenodeapp)
#### Post date: [6 June 2025 19:32 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/5 "2025-06-06T19:32:45Z")
Hashes match โ
!
Proposal on-chain:
`94b466692129203af0d794e9f0ca83143a69587f6771413fb24345eaa5aa8989`
Building `update_tx_claim_rewards_2.wasm` from commit [6da3b4b](https://github.com/anoma/namada-governance-upgrades/blob/6da3b4b1835ae531589bcef65602bf3a803e1de3/update-tx-claim-rewards-2/src/lib.rs) using `earthly +build`: `94b466692129203af0d794e9f0ca83143a69587f6771413fb24345eaa5aa8989`
---
### Author:  [@Gavin](https://forum.namada.net/u/Gavin)
#### Post date: [6 June 2025 19:37 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/6 "2025-06-06T19:37:37Z")
hey! i really appreciate this, @zenodeapp
it may not seem like a big deal, but it is, and could easily go overlooked
---
### Author:  [@Rigorous](https://forum.namada.net/u/Rigorous)
#### Post date: [6 June 2025 20:02 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/7 "2025-06-06T20:02:44Z")
Technically we also ought to verify the code inside the embedded tx\_claim\_rewards.wasm
---
### Author:  [@Rigorous](https://forum.namada.net/u/Rigorous)
#### Post date: [6 June 2025 20:42 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/8 "2025-06-06T20:42:50Z")
Verify that the source code does not drain everyone or some other funny stuff:
Download the wasm artifacts from the Checks tab \> Lint ๐งน Build ๐ Test ๐ฆ (quickly, before the link expires):
Open the zip and compare the checksum with the one in the proposal:
---
### Author:  [@EmberStake](https://forum.namada.net/u/EmberStake)
#### Post date: [6 June 2025 21:23 UTC](https://forum.namada.net/t/proposal-update-tx-claim-rewards/1704/9 "2025-06-06T21:23:16Z")
We verified that `update_tx_claim_rewards_2.wasm` from the CI artifact matches the on-chain hash:
`94B466692129203AF0D794E9F0CA83143A69587F6771413FB24345EAA5AA8989`.
We also confirmed that the hash inside the proposal file matches the CI artifact for `tx_claim_rewards.wasm`:
`e62fbbbb5de5ddb822439795234bac61e2cdbd70b5cb5015caca17ad210b7f96`.
So voted yes.
However, one thing is still unclear to us:
How can we verify that the changes in [PR #4666](https://github.com/anoma/namada/pull/4666) are the **only** ones affecting this WASM file (`tx_claim_rewards.e62fbbbb5de5ddb822439795234bac61e2cdbd70b5cb5015caca17ad210b7f96.wasm`), and that no other files or modifications are influencing this build?