02:29:16 <m-relay> <s​hortwavesurfer2009:monero.social> Unofficial XMRBazaar SimpleX
02:29:17 <m-relay> <s​hortwavesurfer2009:monero.social> https://simplex.chat/contact#/?v=2-7&smp=smp%3A%2F%2FPtsqghzQKU83kYTlQ1VKg996dW4Cw4x_bvpKmiv8uns%3D%40smp18.simplex.im%2FsBdaFdTh8qCzSuVdYqI7J9XhZAV5BDbq%23%2F%3Fv%3D1-3%26dh%3DMCowBQYDK2VuAyEA9deQfu1cIy26Z5rgKQkuoSsUTYaT6FAynZghG9OMZgk%253D%26srv%3Dlyqpnwbs2zqfr45jqkncwpywpbtq7jrhxnib5qddtr6npjyezuwd3nqd.onion&data=%7B%22type%22%3A%22group%22%2C%22groupLinkId%22%3A%22XIEwZOBLi7wg<clipped
02:29:19 <m-relay> <s​hortwavesurfer2009:monero.social> RMUQhqsotA%3D%3D%22%7D
08:00:04 <revuoxmr> Revuo Monero Issue 213: October 3 - 10, 2024. https://www.revuo-xmr.com/weekly/issue-213/
09:14:55 <m-relay> <f​alcon8:matrix.org> I'm always chill bro :)
19:37:02 <m-relay> <j​effro256:monero.social> Me too. Thankfully, I don't see it not being ready by February
19:39:34 <m-relay> <s​yntheticbird:monero.social> Me too. If its not ready by february I might find all the devs and dox them 👍️ (no pressure guys) /s
19:44:50 <m-relay> <3​21bob321:monero.social> Hashtag first
19:45:01 <m-relay> <k​ayabanerve:matrix.org> And by December, the soft target?
19:46:08 <m-relay> <j​effro256:monero.social> Definitely doable
19:46:12 <m-relay> <3​21bob321:monero.social> Is this like saying multi sig by march ?
19:49:14 <m-relay> <j​effro256:monero.social> Tbf the record shows that I said that the "temporary" non-multisig solution would become more permanent than other people thought
19:49:50 <m-relay> <j​effro256:monero.social> But no, should be realistically achievable in the stated timeframe
19:55:07 <plowsof> can we learn anything from this 6 person multisig wallet that was drained https://rekt.news/wazirx-rekt/
19:55:56 <plowsof> (phishing was the eventual downfall of it , after 2 keys where compromised) but still a scary case 
19:59:01 <m-relay> <s​yntheticbird:monero.social> I consider that any multisig setup that requires n =< total_participant/2 votes is a liability.
20:05:42 <ofrnxmr> 3/100 lfg
20:06:13 <ofrnxmr> Jeffro, we know. But ccs would still be RIP if we didnt accept the "temporary" solution 
20:07:18 <ofrnxmr> It was pretty clear to me that strange ppl showed up and fought to keep it down. (1/4 of the year)
20:07:46 <geonic> multisig just gives plausible deniability, like in the fluffy/luigi scenario
20:08:32 <plowsof> geonic exactly. if we could see which signer actually signed the transaction that would be ideal 
20:09:36 <m-relay> <s​yntheticbird:monero.social> i guess having both would be ideal
20:11:55 <m-relay> <3​21bob321:monero.social> So knowing who signed or 2500xmr missing. Tough choice
20:12:03 <ofrnxmr> Neither 
20:12:26 <ofrnxmr> dont know who signed, and lose 2500xmr
20:12:37 <geonic> yep, that's the multisig scenario
20:12:45 <geonic> as long as one person holds the keys and we know they'd be responsible in the event of a breach, that's fine I think
20:13:00 <ofrnxmr> yeah, okay lol
20:13:05 <geonic> split it among different people if the amount gets too big
20:13:08 <m-relay> <3​21bob321:monero.social> Ahahah
20:13:19 <ofrnxmr> worked out fine last time
20:13:29 <geonic> we had 1/2 multisig last time
20:13:49 <ofrnxmr> 😆
20:14:00 <m-relay> <3​21bob321:monero.social> No sig
20:14:12 <geonic> effectively
20:14:23 <ofrnxmr> I tried to split the funds (bsx ccs) but was rejected 
20:14:26 <m-relay> <s​yntheticbird:monero.social> should have been 2/2 from the start
20:14:32 <m-relay> <3​21bob321:monero.social> At the end of the day “its plowsof’s fault”
20:14:33 <ofrnxmr> Cest la vie
20:14:40 <m-relay> <s​yntheticbird:monero.social> n =< total/2 is just adding attack surface
20:14:48 <geonic> yep
20:14:58 <m-relay> <3​21bob321:monero.social> Asking to many questions sir
20:15:00 <ofrnxmr> 2/2 makes it possible to burn the wallet
20:15:26 <m-relay> <s​yntheticbird:monero.social> wdym burn the wallet?
20:15:28 <ofrnxmr> All it takes is for 1 signer to "disappear".. or lose key
20:15:40 <m-relay> <s​yntheticbird:monero.social> ah ok in that sense
20:15:47 <ofrnxmr> Funds locked forever 
20:15:56 <m-relay> <3​21bob321:monero.social> Like having shamir key with 2 not 7 shards
20:16:04 <m-relay> <s​yntheticbird:monero.social> yeah well they better find a third one them lmao
20:16:18 <ofrnxmr> 2/3 and 3/4 was my suggest
20:16:30 <ofrnxmr> Other ppl wanted to larp on abiut 7/12 and shit
20:16:32 <m-relay> <s​yntheticbird:monero.social> make sense
20:16:43 <m-relay> <3​21bob321:monero.social> 2/3 and monero court for arbitration
20:16:50 <m-relay> <s​yntheticbird:monero.social> more than 5 people => Absolute chaos
20:16:54 <ofrnxmr> 2/3 for payout wallet, 3/4 for donation wallet
20:17:18 <m-relay> <3​21bob321:monero.social> They way we like it
20:18:35 <m-relay> <3​21bob321:monero.social> Anyways tob has alpha,beta,delta feather multisig
20:32:44 <m-relay> <j​effro256:monero.social> In this hack, supposedly 2 people were directly hacked. Not much to learn from this outside of general OPSEC. However, the core trick of the hack appears to be that the UI did not show the correct contents of the transaction being signed. The signers thought they were authorizing a routine transfer to a known address, when in reality the signers were authorizing a change in the wa<clipped message>
20:32:45 <m-relay> <j​effro256:monero.social> llet contract. If your signing hardware doesn't do *correct* and *local* interpretations of the data that it is being signed, then the user can't trust that anything they sign will do what they think it is authorizing it to do
20:33:33 <m-relay> <j​effro256:monero.social> This is significantly less of a problem in Monero because we don't do smart contracts and all transactions mainly look the same. There's fewer chances that an honest software dev will screw up interpreting the data that is to be signed
20:34:17 <plowsof> thanks for reviewing jeffro
20:34:21 <m-relay> <j​effro256:monero.social> But some Monero HW wallets still can't display integrated address *cough* ledger *cough*
20:35:07 <m-relay> <s​yntheticbird:monero.social> cough *this review is sponsored by trezor* cough cough
20:36:30 <m-relay> <3​21bob321:monero.social> You both need cough lollies
21:57:23 <m-relay> <d​iego:cypherstack.com> Hi guys, I was requested to make a light version of the design I made for consideration a couple of months back. I was also asked to remove the circle buttons, and another couple touch ups. I did so. Find them here: https://www.figma.com/design/OuY892nD4zD1CEQDvC2Kty/Monero-Website-Redesign-2024-(Copy)?node-id=0-1&t=TC6izgJAIuay80OP-1
21:57:31 <m-relay> <d​iego:cypherstack.com> Please get me feedback. The sooner the better.
22:22:20 <m-relay> <k​ewbit:matrix.org> Hey guys, important milestone update on the Haveno Multiplatform:
22:22:21 <m-relay> <k​ewbit:matrix.org> https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_26721