# LN-Symmetry Project Recap

**URL:** <https://delvingbitcoin.org/t/ln-symmetry-project-recap/359>\
**Category:** Protocol Design\
**Tags:** softfork, lightning, mempool\
**Created:** [January 5, 2024, 5:13pm UTC](https://delvingbitcoin.org/t/ln-symmetry-project-recap/359 "2024-01-05T17:13:05Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![rustyrussell](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/rustyrussell/32/154_2.png) [@rustyrussell](https://delvingbitcoin.org/u/rustyrussell)\
**Post date:** [February 27, 2024, 6:21am UTC](https://delvingbitcoin.org/t/ln-symmetry-project-recap/359/15 "2024-02-27T06:21:18Z")

</div>

> [@instagibbs](#):
>
> Might be talking past each other, but the counter-party may play an old update state to which you’ve forgotten the opening of the taproot commitment to your update. You could remember O(n) fields rather than use the annex, of course.

If they play an old update, you spend it with the new update? Wasn’t that the entire trick? Obviously I’m missing something (I’m guessing some Taproot detail?)

---

_[View the full topic](https://delvingbitcoin.org/t/ln-symmetry-project-recap/359)._