16:31:10 <br-m> <jberman> In the MRL meetings where we discussed that proposal, we reached general agreement to ignore all timelocks that are newly created after May 1st, 2025: https://github.com/monero-project/research-lab/issues/125#issuecomment-2448077632 > <tevador> What is the status of this proposal? https://github.com/monero-project/research-lab/issues/125
16:31:24 <br-m> <jberman> I thought I recalled that an announcement was posted on reddit, but can't find it. @jeffro256:monero.social  says he made a post on monero.town, which is down.
16:31:40 <br-m> <jberman> So imo, our formal messaging has not been clear on that date, unfortunately. I take responsibility for not following up on it. We can discuss how best to proceed on that in MRL on Wednesday
16:34:23 <br-m> <jberman> fwiw, it's possible to have plaintext timelocks with FCMP++, but it adds complications that marginally add some cost to scanning time. I wrote up the full context on it here: https://github.com/monero-project/research-lab/issues/78#issuecomment-2415324570 > <UkoeHB> @tevador afaik it's mandatory since there is no way to enforce timelocks without a redesign. jberman ?
16:35:26 <br-m> <jberman> currently there is code that deprecates the plaintext timelocks at consensus after the FCMP++ fork > <@jwinterm:matrix.org> did any of the timelock changes for FCMP get implemented? Is there relevant code related to thus, or just issues discussing it?
16:42:22 <br-m> <jeffro256> @jberman: I should have pushed for a blog post on getmonero.org, that's my bad 
16:43:01 <br-m> <jeffro256> I don't think that we should change the v17 time lock rule