03:03:29 <endogenic> Be excellent to each other.
03:03:50 <endogenic> i say we need weekly cryptography memes in the topic as well
04:55:10 <koe> hi, protocol question: is the 'dummy encrypted payment id' that appeared in v10 a protocol change, or just part of the core wallet software?
05:00:58 <selsta> koe: AFAIK just core wallet
05:01:07 <koe> The original pull request #5001 doesn't imply a protocol change, but later pull requests may have. Anyone know?
05:01:15 <koe> thanks selsta
05:01:39 <selsta> enforcing it would mean parsing tx_extra on consensus level which we want to avoid
05:01:44 <koe> #5008 sry
05:02:01 <koe> true
05:02:20 <selsta> you back again? :)
05:02:54 <koe> just chipping away at 2nd edition, need to update list of changes at minimum
05:15:44 <koe> this mentions need to decide a long-term solution https://www.reddit.com/r/Monero/comments/aj21yt/big_bang_attack_on_xmr/
05:16:10 <koe> is that the 'change to the block median used to calculate penalty' implemented in recent v12?
05:33:43 <koe> I'm wondering about this 'forbid old RingCT transaction format' at protocol v10/11. It doesn't look like there were new RCTTypes added (other than for bulletproofs), and the CURRENT_TRANSACTION_VERSION is still 2.
05:33:59 <koe> how was it enforced?
05:38:12 <selsta> koe: RCTTypeBulletproof2
05:38:27 <selsta> https://github.com/monero-project/monero/blob/3531cc5fd2889ec5cdd3aecd0e3ba6672fec2e02/src/cryptonote_core/blockchain.cpp#L2806
05:38:52 <koe> oh ok,did RCTTypeBulletproof consolidate RCTTypeFull and RCTTypeSimple? or was one eliminated?
05:40:08 <selsta> not sure if I understand
05:41:49 <koe> previous to bulletproofs there were two kinds of transactions, RCTTypeFull and RCTTypeSimple. Full was for transactions with a single input, and Simple for multiple inputs.
05:42:07 <selsta> ok, after bp hardfork only RCTTypeBulletproof exists
05:42:19 <selsta> and now RCTTypeBulletproof2
05:43:17 <selsta> but someone else has to explain the details I guess :P don’t know if all inputs are now treated as multiple inputs
05:44:02 <koe> ah looking back it seems the difference was down to amount hiding, which bulletproofs took over
05:50:56 <koe> or maybe TypeFull was just abandoned, since it wasn't really used much from the beginning
07:21:40 <Isthmus> Is ban on unencrypted PIDs at consensus level or also honor system?
07:24:28 <selsta> no ban
07:24:37 <selsta> wallet ignores them
07:35:06 <koe> 'unsupported by core wallet software' accurate?
11:25:43 <moneromooo> Full is now unused. I had kept it originally because it saved like 32 bytes or so (not sure). But it also added a fair amount of extra code.
11:26:13 <moneromooo> Bulletproof txes only use the "simple" scheme.
17:09:05 <sarang> Nearly finished with CLSAG preprint revisions and major reorganization
17:09:33 <sarang> It's tricky to build a straightforward narrative leading from the unforgeability definition and forking lemma to the final proof
17:14:04 <sarang> suraeNoether: I'm going to work the unforgeability master algorithm description into the proof... I think this is more consistent with the structure of the other proofs, and hopefully more clear
17:14:18 <sarang> I kept the forgery and forking algorithm descriptions separate, as you had before
18:52:16 <sarang> suraeNoether: my reorganization is complete; please review (reorg.tex is the file)
18:52:34 <sarang> Note any edits as review comments, if you please, to avoid any confusion or conflicting edits
18:52:37 <sarang> I will do the same
18:52:42 <sarang> Then we can release to IACR