# State minimization in MuSig2 signing sessions

**URL:** <https://delvingbitcoin.org/t/state-minimization-in-musig2-signing-sessions/626>\
**Category:** Implementation\
**Tags:** musig2, taproot, wallet\
**Created:** [March 1, 2024, 9:07am UTC](https://delvingbitcoin.org/t/state-minimization-in-musig2-signing-sessions/626 "2024-03-01T09:07:44Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![salvatoshi](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/salvatoshi/32/72_2.png) [@salvatoshi](https://delvingbitcoin.org/u/salvatoshi)\
**Post date:** [March 7, 2024, 11:09am UTC](https://delvingbitcoin.org/t/state-minimization-in-musig2-signing-sessions/626/8 "2024-03-07T11:09:06Z")

</div>

When you complete a signature (Phase 2 above), that `session_id` has already been destroyed (beginning of Phase 2). A new PSBT with the same `session_id` would have to start again from Phase 1, and a new session with fresh randomness (`rand_root` in my post above) would be created (even if it has the same `session_id`).

The only malleability in the PSBT while a session is “active” is after the session is created in Phase 1, and before signatures are produced in Phase 2, which is what I was commenting about in the last post.

Perhaps I should make it more explicit in the description that Phase 2 fails immediately if a corresponding active `session_id` is not found.

---

_[View the full topic](https://delvingbitcoin.org/t/state-minimization-in-musig2-signing-sessions/626)._
