# Livepeer Testnet Implementation Proposal

**URL:** <https://forum.livepeer.org/t/livepeer-testnet-implementation-proposal/3322>\
**Category:** Protocol\
**Created:** [July 31, 2026, 6:03pm UTC](https://forum.livepeer.org/t/livepeer-testnet-implementation-proposal/3322 "2026-07-31T18:03:49Z")\
**Posts on this page:** 1\
**Showing post:** 12

<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, 9:07am UTC](https://forum.livepeer.org/t/livepeer-testnet-implementation-proposal/3322/12 "2026-09-29T09:07:01Z")

</div>

Hey @strykar, thanks for testing this end to end on real hardware, and for taking the fixes upstream. These are exactly the kinds of things that are easy to overlook when shipping new features.

We discussed this with the team and agree with the suggestion. It is a small addition and fits well into the existing process:

- **Release checklist:** For any protocol change that alters what the stake-holding key needs to sign, add a step to run the call with a real hardware signer on a Type 3 fork.
- **Testnet docs:** Document that signing workflow in the protocol-updates repo so it becomes part of the standard process rather than something people have to discover independently.

If you have other suggestions don’t hesitate to reach out. Thanks again for all your support in getting this feature released.

On behalf of the protocol team.

---

_[View the full topic](https://forum.livepeer.org/t/livepeer-testnet-implementation-proposal/3322)._