# Rewards Tree Spec v10

**URL:** <https://dao.rocketpool.net/t/rewards-tree-spec-v10/2937>\
**Category:** Governance\
**Created:** [20 April 2024 03:04 UTC](https://dao.rocketpool.net/t/rewards-tree-spec-v10/2937 "2024-04-20T03:04:10Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![Valdorff](https://dao.rocketpool.net/user_avatar/dao.rocketpool.net/valdorff/32/319_2.png) [@Valdorff](https://dao.rocketpool.net/u/Valdorff)\
**Post date:** [4 May 2024 05:27 UTC](https://dao.rocketpool.net/t/rewards-tree-spec-v10/2937/25 "2024-05-04T05:27:28Z")

</div>

I understand why O(1) is useful for your application. It is not, however, part of RPIP-31 at all. RPIP-31 talks about who can initiate RPL claims, but it does not talk about aggregating them or not in any way. (Eg, if a withdrawal address was used for 5 nodes and needed to make one claim for each, that strategy could fulfill the spec). This is also true for O(1) smoothing pool claims – ETH is mentioned exactly once in RPIP-31 to say that claiming RPL will also distribute smoothing pool ETH for that NO. Again - no mention one way or the other about aggregation. I think it’s important to clarify that the thing you’re describing as critical to Nodeset is _not_ something that the pDAO has at any time voted in. Again, I totally get why it’s useful to your application, but from a governance perspective this is not something that has been committed to in any way.

Fwiw, I think my preference remains v10 simply as being most pragmatic, though item #1 in [Houston Specification Discrepancies](https://dao.rocketpool.net/t/houston-specification-discrepancies/2958) does give me some pause.

---

_[View the full topic](https://dao.rocketpool.net/t/rewards-tree-spec-v10/2937)._
