02:09:41 <plowsof> ccs wallet incident blog post up for review https://github.com/monero-project/monero-site/pull/2208
08:00:21 <m-relay> <e​rc:cryptoriot.org> let's wait for an input from core
10:01:52 <binaryFate> I think it makes sense to publish as is. We had already spent some time finding info and discussing that post.
13:17:57 <m-relay> <e​rc:cryptoriot.org> plowsof are you around to fix those two minor issue in the pr?
13:18:19 <m-relay> <e​rc:cryptoriot.org> after that's done we can merge and deploy straight away. This should be out as soon as possible
13:18:36 <m-relay> <e​rc:cryptoriot.org> especially because media will be on this soon if they are not already
13:19:04 <m-relay> <e​rc:cryptoriot.org> if plowsof is not around i would just merge and deploy.
13:33:38 <plowsof> hi
13:34:04 <plowsof> checking
13:39:12 <m-relay> <e​rc:cryptoriot.org> plowsof. I see the edits, only needs to be squashed and then it's ready imo
13:39:21 <m-relay> <p​lowsof:matrix.org> should be ready for squashing now ErC
13:39:29 <m-relay> <p​lowsof:matrix.org> ok thanks! apologies, i was asleep
13:40:07 <m-relay> <e​rc:cryptoriot.org> no worries no problem
13:40:48 <m-relay> <p​lowsof:matrix.org> squashed x
13:49:04 <m-relay> <e​rc:cryptoriot.org> I'm having a moment where i'm not completely sure we should post that message as a blog post. It assumes people already know terminology like ccs and mentions fluffypony's arrest, which could be confusing and give a wrong impression. Maybe would be better to write a shorter blog post with an explanation in simpler words of what happened and clarify that this doesn't imply a proble<clipped message>
13:49:04 <m-relay> <e​rc:cryptoriot.org> m in Monero itself?
13:49:52 <m-relay> <e​rc:cryptoriot.org> it's just a thought i'm having right now and i would be fine to go with the post as it is. But this is a very sensitive matter and we should definitely be sure we are as clear as possible without possibility of misunderstanding and confusion
13:50:06 <fluffypony> yeah I know, I thought the same
13:50:26 <m-relay> <e​rc:cryptoriot.org> we would link to the github issue from the blog post, but i'm not sure about posting that entire text
13:50:30 <fluffypony> maybe it's better to write something and say there was an incident, and here's the GitHub issue
13:50:33 <fluffypony> that details it
13:50:48 <m-relay> <e​rc:cryptoriot.org> yeah
13:51:21 <plowsof> somethin happened, everything is fine, we're actively working on a solution , heres the details kinda things?
13:56:55 <m-relay> <e​rc:cryptoriot.org> yeah a clear simple communication from core that points to the github issue for details.
15:13:48 <plowsof> i've pushed the shorter version 
15:14:28 <plowsof> i have added "The General Fund (which remains intact) will be used to cover this loss. Contributors with [in-progress](https://ccs.getmonero.org/work-in-progress/) CCS proposals will remain uneffected. " 
15:14:55 <plowsof> this statement needs to be confirmed and or edited by core 
15:17:36 <m-relay> <p​lowsof:matrix.org> preview http://127.0.0.1:4000/2023/11/03/ccs-wallet-incident.html
15:18:33 <m-relay> <p​lowsof:matrix.org> lol localhost https://deploy-preview-2208--barolo-time-757cf9.netlify.app/2023/11/03/ccs-wallet-incident
15:25:58 <m-relay> <e​rc:cryptoriot.org> Fluffypony are you working on a statement from core?
15:26:47 <m-relay> <e​rc:cryptoriot.org> If not we can come up with something like plowsof suggested (but in that case i would suggest some changes)
15:32:21 <m-relay> <p​lowsof:matrix.org> my only requirement is for the clarification on work in progress proposals being unaffected, very important
16:22:17 <fluffypony> oh apologies - I've not been working on anything, other than just bouncing the idea around here 
16:46:55 <m-relay> <e​rc:cryptoriot.org> what about:
16:47:06 <m-relay> <e​rc:cryptoriot.org> Today, during a routine transfer, we noticed the '[Community Crowdfunding System](https://ccs.getmonero.org/)' (CCS) main Wallet was drained of 2,675.73 XMR (the entire balance) on September 1, 2023. The hot wallet, used for payments to contributors, is untouched; its balance is ~244 XMR. We have thus far not been able to ascertain the source of the breach. An internal investigati<clipped message>
16:47:06 <m-relay> <e​rc:cryptoriot.org> on is ongoing and further details will be released once we have them.
16:47:07 <m-relay> <e​rc:cryptoriot.org> The General Fund (which remains intact) will be used to cover this loss. Contributors with [in-progress](https://ccs.getmonero.org/work-in-progress/) CCS proposals will remain unaffected. 
16:47:07 <m-relay> <e​rc:cryptoriot.org> Further details and discussion can be found on this [issue on GitHub](https://github.com/monero-project/meta/issues/916).
16:47:22 <m-relay> <e​rc:cryptoriot.org> plowsof ^ added a couple of details and changed a couple of lines
16:49:12 <plowsof> thanks
16:50:44 <m-relay> <e​rc:cryptoriot.org> it's just a suggestion tho
16:50:54 <m-relay> <e​rc:cryptoriot.org> don't know what core thinks about it
16:50:57 <m-relay> <e​rc:cryptoriot.org> fluffypony?
16:54:28 <m-relay> <p​lowsof:matrix.org> "today we noticed" would have been 28th september
16:55:08 <m-relay> <p​lowsof:matrix.org> otherwise seems perfect
16:55:25 <m-relay> <e​rc:cryptoriot.org> ah ok let's drop it then
17:07:41 <fluffypony> looks good to me, thanks for doing this!
17:15:47 <m-relay> <p​lowsof:matrix.org> final review ErC
17:17:25 <m-relay> <e​rc:cryptoriot.org> i would leave the link to the css website plowsof. So people know what we are talkingabout
17:18:18 <m-relay> <e​rc:cryptoriot.org> beside that i'd just squash and get it merged
17:48:22 <m-relay> <p​lowsof:matrix.org> yep (link was dropped during copying, will add)
17:51:51 <m-relay> <e​rc:cryptoriot.org> looks good
18:14:58 <m-relay> <e​rc:cryptoriot.org> binaryfate blog post ready to be merged and deployed: https://github.com/monero-project/monero-site/pull/2208