-
m-relay
<monero.arbo:matrix.org> qubic mining is very permissioned
-
tbot
wdym arbo
-
m-relay
<gogo2464:matrix.org> Can i buy moneros from my online bank or should I convert it to solana first with uniswap?
-
m-relay
<sbt:nope.chat> Better use retroswap.
-
m-relay
<sbt:nope.chat> Your bank would probably flag you for buying XMR.
-
m-relay
<alexandre:uii.pt> having a local p2pool node and using a remote one have the same likelyhood of getting shares?
-
m-relay
<alexandre:uii.pt> Got mine running but for almost a day didn't get any share on the mini chain with ~5KH/s
-
m-relay
<ofrnxmr:xmr.mx> Yes
-
m-relay
<alexandre:uii.pt> I see, then i guess i was just unlucky, should get less shares than on a "normal" pool? or it would depend on the pool?
-
m-relay
<ofrnxmr:xmr.mx> Yes, less than a normal pool
-
m-relay
<alexandre:uii.pt> gotcha, thanks
-
m-relay
<ofrnxmr:xmr.mx> Normal pools send low difficulty shares to help track your hashrate, and pay you for the hashes youve submitted
-
m-relay
<ofrnxmr:xmr.mx> P2pool has higher difficulty shares because there are max 2160 payouts per block
-
m-relay
<alexandre:uii.pt> overall payout should be similar, even with higher difficulty?
-
m-relay
<ofrnxmr:xmr.mx> Yes
-
quantum`
-
quantum`
I am running my own monerod node with a systemd service and my own config file. Gupaxx does not seem happy about that. IIRC there is a setting in Gupaxx to allow for this?
-
m-relay
<alexandre:uii.pt> did you enable rpc and zmq?
-
quantum`
zmq-pub=tcp://127.0.0.1:18083 -- but not rpc.
-
m-relay
<ofrnxmr:xmr.mx> Rpc is enabled by default, assuming its running on the same host
-
quantum`
I've disabled the systemd service and tried to use the Gupaxx node, but the > is grayed out in Node, and starting P2Pool crashes.
-
quantum`_
Anyone know what Gupaxx runs in the xmrig tab? Personally I thought it is xmrig, but setting sudoers does not work.
-
quantum`_
pete localhost = NOPASSWORD: /usr/bin/xmrig
-
quantum`_
Still asks for password.
-
quantum`_
miner speed 10s/60s/15m n/a n/a n/a H/s max n/a H/s
-
quantum`_
It's using 6% of one thread... and I have 64 threads.
-
m-relay
<17lifers:matrix.org> try disabling numa
-
m-relay
<gogo2464:matrix.org> thank I will use it?
-
m-relay
<gogo2464:matrix.org> how that?
-
m-relay
<sbt:nope.chat> If you use any popular exchange. With retroswap, you will exchange directly so your bank wouldn't know.
-
m-relay
<gogo2464:matrix.org> sure. Indeed is it really worst than bying bitcoin and ethereum indeed? I could still say I was going to speculate.
-
m-relay
<gogo2464:matrix.org> lol
-
m-relay
<gogo2464:matrix.org> #maximalist
-
quantum`_
17lifers:matrix.org: --randomx-no-numa, no change. That must not be it.
-
quantum`_
huh, running xmrig manually and all CPUs are slammed. Something about Gupaxx.
-
quantum`_
Also Gupaxx ignores my sudoers setting for no password, but CLI does not.
-
Guess65
in theory when wallet a sends an amount smaller than an amount received to wallet b after a random time and then to wallet c yet another random amount after a random time - wallers b and c are unlinkable to wallet a?
-
m-relay
<ofrnxmr:xmr.mx> not entirely. There is a path from c to the change output from b, and from b to the change output from a
-
moneromooo
Ah, the joya of ambiguous languages.
-
m-relay
<ofrnxmr:xmr.mx> example. If i have 1 output in wallet a, and use it to make weekly purchases from a service b (while using a new ip addr etc), service b can deduce that the same wallet is making those purchases and is spending their change outputs repeatedly.
-
Guess65
ok then use sweep all?
-
m-relay
<ofrnxmr:xmr.mx> Depends on your threat model
-
Guess65
from a to c then to b c will wait b will wait before spending
-
Guess65
we are talking about monero anonimity
-
Guess65
max anonimity monero can provide as a protocol
-
m-relay
<ofrnxmr:xmr.mx> Well the only way to get rid of the graph is to use different monero
-
m-relay
<ofrnxmr:xmr.mx> You can churn (send-to-self) the change to lower the likelyhood
-
Guess65
then. wallet a splits its total into smaller totals. random numbers 1.33445 etc that all add up to total. wait. step 2 new tor identity. send outputs to wallet b sweep all. wait. new tor identity outputs to wallet c.
-
Guess65
i have made one mistake
-
Guess65
each wallet ought to re randomise before re sending
-
m-relay
<ofrnxmr:xmr.mx> That is easy to see on chain
-
m-relay
<ofrnxmr:xmr.mx> randomizing amounts doesnt make an difference in regarda to on-chain tracing
-
m-relay
<ofrnxmr:xmr.mx> Are yoy the owner of wallet a b and c?
-
m-relay
<hbs:matrix.org> buy hashrate with XMR to mine on p2pool, get fresh XMR
-
m-relay
<ofrnxmr:xmr.mx> P2pool outputs are public 🫡
-
m-relay
-
m-relay
<ofrnxmr:xmr.mx> This is an xy problem. W/o knowing what the point of this exercize is, cant advise on "best practices"
-
Guess65
its untraceable
-
Guess65
100% anon
-
Guess65
are there even public tracing challenges? with some prizes :) then it is easy to see
-
Guess65
split amount to random sub totals same wallet. send outputs to b c etc. re split total after each step randomly. random delays. new tor identity for each step.
-
m-relay
<ofrnxmr:monero.social> Yeah, useless
-
Guess65
-
Guess65
monero is untraceable and unlinkable
-
m-relay
<321bob321:monero.social> Yeah our monero board of director
-
m-relay
<321bob321:monero.social> We have 16 of them currently