07:54:09 why the effort to write for nakamoto.com? 13:11:34 I was thinking it would be cool to mention Monero :- ) I've still some doubts that my articles will be accepted 16:41:55 I just applied to give a talk about fungibility at the MCC. Hopefully I'm selected 17:02:21 I need some help revising some of the wording for an article on the auditability of Monero 17:02:58 It's difficult to accurately describe the risks of implementation risks while keeping touch with reality 17:03:11 Here is the whole post so far: 17:03:33 https://www.irccloud.com/pastebin/NGTQdhT4/ 17:04:30 I'm especially interested in updating line 21. I have considered a few wordings 17:04:59 I think it's important to acknowledge that there are honest-to-goodness cryptographic hardness assumption breaks (which at present are exceptionally unlikely), implementation/consensus bugs that are detectable (e.g. the Bitcoin inflation bug, the Monero key image bug), and then there are bugs that would not be detectable (e.g. Zcash's soundness bug) 17:05:15 The former is IMO not something to keep you up at night 17:05:28 My current best thought is to add "Certain classes of flaws could lead to undetectable supply tampering or tampering that is only noticeable after the flaw is discovered." to the end of line 21 but I don't love it 17:06:07 I think the reader should leave with the understanding that there are risks to a transparent asset and other risks to an opaque asset 17:06:28 and that the choice should depend on use case and an understanding of the risks 17:16:57 I just applied to give a talk about fungibility at the MCC. Hopefully I'm selected <-- nice! My impression was a rather poor Monero/privacy/fungibility presence last year 17:17:54 binaryFate: Brandon was there on a panel, but I think we need a good talk where people can actually see the implications of fungibility first-hand 17:18:31 don't reshare this outside of the channel yet please, but I finally have my recording of the talk I gave in late August at Andreas's conference 17:19:16 I opened with an activity where people traded tainted funds around, and it was pretty well-received I think and got the point across much better than a high-level discussion 17:19:18 https://www.youtube.com/watch?v=NwieiDS10mc 17:19:18 [ BTC2019: Institutions & Individuals Need Effective Privacy Solutions | Justin Ehrenhofer - YouTube ] - www.youtube.com 17:46:29 Note that there is a Konferenco meeting in 1.25 hours in #monero-konferenco 17:46:45 And an MRL meeting in 0.25 hours in #monero-research-lab 17:52:07 sgp_: for the blag post, would it be useful to specifically enumerate those categories of risks? (hardness assumption break, detectable flaw, undetectable flaw) 17:53:15 It's not possible to specifically quantify the risk (although the risk of an underlying hardness assumption break seems faaaar lower), but at least it can help drive the discussion that not all risks are created equal 17:54:13 sarang: I would need further explanation on what you're getting at 17:55:22 It could be useful to discuss how a hardness break, while negligible risk at present, could affect _any_ cryptographically-secured ledger 17:55:43 A detectable flaw can arise from many things, and that class can (and has) affected different ledger types 17:56:12 While an undetectable flaw is more unique to opaque ledgers... and perhaps that's where the idea of balancing risks is most relevant 18:54:31 helo! 18:55:21 hey parasewX. the konferenco meeting is in #monero-konferenco in 5 mins if you are about? 18:55:32 and for anyone else.... 18:55:35 who is interested 18:55:47 https://github.com/monero-project/meta/issues/426 18:56:26 yes of course! great to be back, c3 was a bit exhausting, i am officially back from now on :) 21:20:00 so then...