Revuo Monero Issue 191: October 26 - November 2, 2023. revuo-xmr.com/issue-191.html

<i​ntr:envs.net> johnfoss68: hey, do you mind if I dm you regarding the monero moon?

hello i just read this wired.com/story/monero-privacy

hoping these issues have been improved upon

this is from like 5 years ago

<p​lowsof:matrix.org> from 2018, lets see

<g​fdshygti53:monero.social> That already mentionned one that got fixed in 2017

<j​effro256:monero.social> Yes, I believe that they are referring to the paper by Miller et al. The decoy selection algorithm has changed many times since then to more accurately capture the “real” distribution of spends

monero's privacy has had multiple improvements over the years

<s​tnby:kernal.eu> matrix.monero.social/_matrix/media/…/kernal.eu/EdhCMBKjCqNrJoEfVrnEfEex

<s​tnby:kernal.eu> Hungarian National Museum

<n​aphtha:kyun.host> oh my science

<n​aphtha:kyun.host> first it was trianon

<n​aphtha:kyun.host> and now this???????

<r​ucknium:monero.social> GrapeJuice9000: Read Ye, C., Ojukwu, C., Hsu, A., & Hu, R. 2020. "Alt-coin traceability." moneroresearch.info/index.php?action=resource_RESOURCEVIEW_CORE&id=18

<r​ucknium:monero.social> and Vijayakumaran, S. 2021. "Analysis of cryptonote transaction graphs using the Dulmage-Mendelsohn decomposition." moneroresearch.info/index.php?actio…n=resource_RESOURCEVIEW_CORE&id=156

<r​ucknium:monero.social> Those papers analyze how improvements to Monero reduced or eliminated the effectiveness of those anti-privacy attacks.

<7​csedok7tk0q8mkp> que?

<7​csedok7tk0q8mkp> cdn.discordapp.com/attachments/6204…b0e78791961fc318a60e5ae815a783f9d7&

<o​frnxmr:monero.social> Lmao

<o​frnxmr:monero.social> PSA: WE NEED TO STOP OUR NODES

<7​csedok7tk0q8mkp> that was from was one of the posts in the CCS issue

<7​csedok7tk0q8mkp> wtf is she even on about

<7​csedok7tk0q8mkp> again

<7​csedok7tk0q8mkp> que?

<7​csedok7tk0q8mkp> cdn.discordapp.com/attachments/6204…e855f7105ded89469df8e1fdca13e64a6d&

<7​csedok7tk0q8mkp> reminds me of trader university

Good evening to everyone just updated my gut wallet while I spent three or four days synchronizing in the mean while I've mined thru xim-rig my wallet stoiò 0,00000 why? Nothing was mined?

<o​frnxmr:monero.social> Context matters

<o​frnxmr:monero.social> Offloadng 400k in xmr is A LOT more noticable than offloading 5m in btc

<o​frnxmr:monero.social> Any swap, any cex, even bisq, atomic swaps. Whatever

marco: did you mine to a pool?

<o​frnxmr:monero.social> youre the _only_ person doing it

<o​frnxmr:monero.social> So yes, being a big fish in a small pond makes you an easy target

<p​lowsof:matrix.org> is bridgerton talking to chatgpt and pasting the output here?

<o​frnxmr:monero.social> Pbly

<i​ntr:envs.net> why was the CCS github issue deleted lmao

<o​frnxmr:monero.social> Better than drived

<o​frnxmr:monero.social> Huh?

<o​frnxmr:monero.social> 916

<i​ntr:envs.net> nvm I think github is shitting itself

<p​lowsof:matrix.org> link to the ccs github issue interloper?

<p​lowsof:matrix.org> lol

<i​ntr:envs.net> it said 404, but it's doing it for all issues I'm subscribed to

<o​frnxmr:monero.social> monero-project/meta #916

<o​frnxmr:monero.social> Looking at it rn

<i​ntr:envs.net> sorry for false alarm

<r​ucknium:monero.social> ofrnxmr: Don't reload

<i​ntr:envs.net> yeah ^

<r​ucknium:monero.social> I am getting 404 for all GitHub repos

<i​ntr:envs.net> the power of microsoft

<p​lowsof:matrix.org> bill gates is fixing something, please hold

<i​ntr:envs.net> forgot the booster shot for the servers

<p​lowsof:matrix.org> its back now, thanks bill

<i​ntr:envs.net> is tayvano some e-celeb or something

<p​lowsof:matrix.org> monero wont hit the news cycle guys.. there was a hack for over 2 million rekt.news/onyx-protocol-rekt

<p​lowsof:matrix.org> phew

lost to a well-known vulnerability

.hmmm

<i​ntr:envs.net> thanks onyx guys, very cool!

400k stolen doesn't make headlines these days, sorry guys :D

<l​ouipc:matrix.org> still a troubling security fail

<g​fdshygti53:monero.social> We did ;)

<g​fdshygti53:monero.social> image.png

<g​fdshygti53:monero.social> web3isgoinggreat.com

<o​frnxmr:monero.social> always got 1 in the chamber :P haha

<o​frnxmr:monero.social> faster to just switch guns anyway

<o​frnxmr:monero.social> Offtopic 🙃

<i​ntr:envs.net> ah yes, monero is totally web3

selsta yes

marco: did you login to the pool website?

no

well try that first to see your balance

Ok thanx

selsta o think I need help , if you can it will be very kind of you

I'm not the best to ask about mining since I don't do mining myself

<o​frnxmr:monero.social> Hi, selsta here. How may i assist?

generally if you mine to a pool you will need to hit the payout limit first

<o​frnxmr:monero.social> Selstagpt*

and then you can request a payout

mining 3 days likely won't be enough

Ah...ok

This is a good new

<o​frnxmr:monero.social> Go to pool website > read FAQ

yes

I'm checking

<o​frnxmr:monero.social> Go to pool website > go to earnings OR settings > view limit to cash out (should show a minimum)

<o​frnxmr:monero.social> Or

<o​frnxmr:monero.social> Tell me what pool you use, and ill tell you the limit

<o​frnxmr:monero.social> I am selstagpt, after all

<o​frnxmr:monero.social> minerstat.com/coin/XMR/pools

Bye and thanks for your help

<s​needlewoods_xmr:matrix.org> is it expected behavior, that when visiting localhost:18082 in browser it breaks zmq server?

<s​needlewoods_xmr:matrix.org> monerod with default log level said "ZMQ RPC Server Error: thrown at zmq_server.cpp:161: Resource temporarily unavailable"

sech1: ^

<v​tnerd:monero.social> SNeedlewoods @sneedlewoods_xmr:matrix.org: does the zmq shut down, or just display that one error

<s​needlewoods_xmr:matrix.org> p2pool is instantly complaining about not being able to connect to zmq and it works after restart of monerod, so I'd assume it shuts down

Interesting

It's monerod bug then

<s​needlewoods_xmr:matrix.org> I was just fiddling around and found it by accident, thought maybe I'm just supposed to not visit it through a browser

<v​tnerd:monero.social> I cant duplicate this though

Is port 18082 always enabled when only zmq-pub is enabled in command line?

It shouldn't be, right? vtnerd

<v​tnerd:monero.social> 18082 is always enabled afaik, even without zmq-pub. There's no default port/path for zmq-pub

<v​tnerd:monero.social> 18082 is the rpc port for zmq

Then it's technically a DoS attack vector

If it's so easy to break it

<s​needlewoods_xmr:matrix.org> ./monerod --zmq-pub tcp://127.0.0.1:18083 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --disable-dns-checkpoints --enable-dns-blocklist

<s​needlewoods_xmr:matrix.org> that's how I run it

<v​tnerd:monero.social> I cant dupe this, at least on testnet where the only difference should be port number

Is 18082 bound only to localhost by default?

<v​tnerd:monero.social> Yes

snee

Do you run official binary, or self-compiled

<s​needlewoods_xmr:matrix.org> self compiled v0.18.3.1

<s​needlewoods_xmr:matrix.org> but could also dupe this with official binary for v0.18.2.2

There have been a few reports of issues with self compiled binaries

sech1: so far no other report since your issue and xmrvsbeast, i've asked multiple people who run self compiled binaries

<s​needlewoods_xmr:matrix.org> I can recreate this with official release too

monero-project/meta #916 - I recommend recurring to moderation at this point. Tayvano's soymilk cryptotwitter army full of theft victims started to raid the thread.

fluffypony: It was a bad idea from the beginning to summon Tayvano. He is a known toxic troll trying to cope with being pwned in the past by raging at Monero and other privacy-oriented technologies.

 

Current pwned raging bros army: @termermc @elibroftw @tayvano but there will be more if this continues.

tellingu has left the channel

<e​libroftw> Huh

elibroftw why are you in the raging bros army!

<e​libroftw> Just trying to think of different ways the seed was compromised

<1​23bob123:matrix.org> Need to make a room #monerodatabreach

<1​23bob123:matrix.org> You have 90 days too disclose!

* #monero-data-breach