14:58:40 <m-relay> <c​haser:monero.social> BTW, what this too would enable is building a risk profile on an on-going basis. it doesn't give us an answer to the original question, which I'd frame as this: "is it safe to *irreversibly* reduce the lock depth?" that's because it involves dynamic variables external to the chain (XMR price, hash power price curve), which can change such that, for the same double spend attack suc<clipped message>
14:58:41 <m-relay> <c​haser:monero.social> cess probability, we would somehow (hard forks? oracles? another pain point) need to increase the lock depth back.
17:01:31 <m-relay> <c​haser:monero.social> the question is actually "by how much is it safe to irreversibly reduce the lock depth?", and the approach does give an answer. it's just not one that I expected or that I like: zero.
23:01:37 <m-relay> <a​ck-j:matrix.org> Rucknium: Wish granted. https://moneroresearch.info/index.php?action=resource_RESOURCEVIEW_CORE&id=239
23:02:19 <m-relay> <a​ck-j:matrix.org> Can you increase the file size allowed on moneroreseach. The PDF is 2.5MB but the max filesize is 2MB
23:20:59 <m-relay> <b​asses:matrix.org> can be compressed?
23:24:11 <m-relay> <r​ucknium:monero.social> No, we don't need to compress it. I didn't figure out how to put the limit higher after it reset when I upgraded WIKINX. I will fix in a few minutes.