19:10:15 There are also very significant scaling issues here with respect to. 19:10:15 1) Turnstiles. The need to move the entire blockchain through the turnstile in a reasonable amount of time. The issue especially of the turnstile is being rushed and users competing to get first through the turnstile. 19:10:15 What I see here is the need for a significant surge capacity over a matter of a few months. [... more lines follow, see https://mrelay.p2pool.observer/e/-IKvr8wKeF82Q1dH ] 19:13:49 My point here is that a robust and fast growing peer to peer on chain adoption of Monero together with a very strong reserve surge capacity is a critical component of the defense. 19:15:27 Typo I meant BS not VS 20:25:42 @articmine: for 1, we can add special scaling for the turnstile if/when we code in the turnstile, there is no point planning our scaling for that now. 20:37:04 1. Txs expiring after 72hrs 20:37:04 2. 600mb txpool default size limit 20:37:28 These are the problems for turnstile, not scaling imo 20:39:35 Because you can increase the txpool size to infinity, but txs will still expire if there are too many submissions. 20:39:35 fun fact (i think): if you flush_txpool, you can reset the tx seen time, and extend the72hrs. I dont think this is supposed to happen :P 21:07:08 ugh. i think i've blissfully forgotten that there's probably a turnstile in our future 21:22:22 CARROT attempts a PQ recoverable framework so all that's necessary is moving to a post-CARROT wallet, not moving across the PQ barrier itself. 21:22:46 If done successfully, it'll give _years_ of time for the turnover 21:23:39 Even if it culminates in one final explicit time period before invalidation of historical outputs 21:28:50 The sooner we prepare today, the less of a rush we'll be in tomorrow 21:29:12 Fund PQ research now 21:29:22 Spend $10m on several research teams 21:29:47 *or a reasonable amount to qualified individuals like people @ CS