# LIP: Delegated Reward Calling Discussion Thread

**URL:** <https://forum.livepeer.org/t/lip-delegated-reward-calling-discussion-thread/3278>\
**Category:** Governance\
**Created:** [July 3, 2026, 4:27pm UTC](https://forum.livepeer.org/t/lip-delegated-reward-calling-discussion-thread/3278 "2026-07-03T16:27:01Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![rickstaa](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.livepeer.org/rickstaa/32/917_2.png) [@rickstaa](https://forum.livepeer.org/u/rickstaa)\
**Post date:** [September 29, 2026, 12:24pm UTC](https://forum.livepeer.org/t/lip-delegated-reward-calling-discussion-thread/3278/20 "2026-09-29T12:24:06Z")

</div>

**Update: LIP-118 now supported in go-livepeer**

Reward caller support has shipped in [go-livepeer v0.9.3](https://github.com/livepeer/go-livepeer/releases/tag/v0.9.3), so you can now set up a reward caller directly from the client. The [orchestrator docs](https://docs.livepeer.org/network/guides/orchestrator-activate) have been updated with the recommended setup, including a cold orchestrator wallet and a separate reward caller. We strongly recommend all orchestrators follow it. For more context on why, see our [post on protocol security](https://forum.livepeer.org/t/protocol-security-in-2026-report-volume-incidents-and-cost/3364).

We are aware the new functions still do not show up on the [BondingManager Arbiscan contract page](https://arbiscan.io/address/0x35bcf3c30594191d53231e4ff333e8a770453e40#readProxyContract). Arbiscan does not pick up our proxy contracts automatically, and we are working with their team directly to resolve it. In the meantime, the functions can be called through the client or directly against the contract, as shown in the [earlier update](https://forum.livepeer.org/t/lip-delegated-reward-calling-discussion-thread/3278/15).

---

_[View the full topic](https://forum.livepeer.org/t/lip-delegated-reward-calling-discussion-thread/3278)._