# LIP-118 secured one side of the network. The other side still has one key holding everything **URL:** \ **Category:** Research & Protocol Improvements\ **Created:** [August 31, 2026, 10:49am UTC](https://forum.livepeer.org/t/lip-118-secured-one-side-of-the-network-the-other-side-still-has-one-key-holding-everything/3349 "2026-08-31T10:49:18Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:33pm UTC](https://forum.livepeer.org/t/lip-118-secured-one-side-of-the-network-the-other-side-still-has-one-key-holding-everything/3349/3 "2026-09-29T12:33:54Z")
Hey @chrishobcroft, thanks for driving this forward. Reducing the funds at risk on gateways is an important next step for network security, and the recent [Inc-node key compromise](https://forum.livepeer.org/t/protocol-security-in-2026-report-volume-incidents-and-cost/3364#p-7929-recent-incidents-3) made that even clearer. The amended proposal, with a cap on what a signing key can commit, is a strong direction. We just opened a [forum post](https://forum.livepeer.org/t/protocol-security-in-2026-report-volume-incidents-and-cost/3364#p-7929-what-we-are-doing-5) on protocol security to start a broader discussion on security as AI tooling makes attacks faster and cheaper. It references this thread as a next step for the gateway side. Since the gateway/signer side might change with Livepeer 2.0, it might makes sense to pick this up once the 2.0 litepaper is out. In the meantime, the protocol team is happy to work with you directly to move it forward, so gateways can get the same kind of protection LIP-118 gave orchestrators. --- _[View the full topic](https://forum.livepeer.org/t/lip-118-secured-one-side-of-the-network-the-other-side-still-has-one-key-holding-everything/3349)._