Nova comunidade Monero Brasil, no Clouthub.

Doomberg asking Saylor if he would be able to reveal Microstrategy's bitcoin public wallet addresses 😅

I understand his reasoning as a business and not saying he should have to reveal the details. Pretty funny though to hear him say how he wants to keep that private.. well no shit

"we wouldn't want people looking at our transactions"

Classic moment

well of course..

It triggers me that George doesn't have a real Austrian on his channel to debunk his Monetarist/Friendmanite views

George is fractional reserve believer

my node is saying 2781242 (2 minutes behind) but the blockheight at xmrchain is at 2781307 which is like 60 blocks ahead what gives?

* at xmrchain.net is

your node is behind

actually nevermind I'm looking at the tail of monerod.logm, monerod status is showing the right numbers relative to web explorers

s/logm/log/, s//`/, s//`/

hey

who[xmpp]: hi, i'm not too familiar with xmr (only used it for like a year or so). wanted to ask, based on my understanding of ring signature cryptography used, I need to send my funds across multiple wallets to increase my anonymity set?

who[xmpp]: so i'd be making new wallets and passing the funds around to them?

who[xmpp]: and if yes, would it work the same if i just used a subaddress rather than generating a whole new wallet?

who[xmpp]: apologies in advance if i have any misconeptions or anything, would be happy if someone could correct me :)

you don't even have to use different subaddresses, just send from whatever address/subaddress you have back to itself

this is called "churning"

its effectiveness is still debated, and there are some pitfalls/caveats to watch out for - doing it badly can actually make it easier to associate outputs together

but the general idea is that (if done properly) it can indeed increase the set of possible paths that your funds have taken

who[xmpp]: > its effectiveness is still debated, and there are some pitfalls/caveats to watch out for - doing it badly can actually make it easier to associate outputs together

ah okay, do you know what those pitfalls/caveats you mentioned are?

who[xmpp]: with my caveman understanding of things i just figured i'd just be sending it to the same address like 7-8 times

That's kind of excessive, even in the most extreme threat/paranoid scenarios

2-3 times is plenty

But you have to be careful about associating outputs together, as well as the timing of each churning operation

churning 7-8 times in quick succession is a sure way to be visible

churn 2-3 times with random intervals, ranging from several hours to several days

who[xmpp]: > But you have to be careful about associating outputs together, as well as the timing of each churning operation

hmm, so if i receive xmr from various different wallets i shouldn't just combine them all when churning (assuming thats what you mean by associating them with each other)?

depends on your threat scenario, for a caveman it would seem that churning is not necessary :)

probably the same for most people

Question. When trying to mine p2pool using Monero GUI, is it normal that it downloads block again, and again, and it finishes and then its back to download blocks again and never do anything else but download blocks after just finishing downloading blocks?

@who[xmpp] correct. Ideally, you would churn each output individually at first, and only combine them at the end (if necessary)

Anyone has used uquid.com? Is it trustworthy?

uquid.com/monero-debit-card

seems like a scam to me and i wouldn't trust some random service on the internet to hold my money on it. There is also no way to get your money back in any case where you aren't satisfied with your payments as this is crypto.

You can check the sites with some other crypto currencies such as uquid.com/bitcoin-debit-card or uquid.com/ethereum-debit-card -- quite unserious how they also pasted the same text everywhere.

All Countries approver? srsly? Smell scammy considering most crypto card issuers pulled in 2017-2018 then put them back but with big limitation (like EU only, Russia than USA). Most/all majority world countries excluded.

s/approver/approved/

Seed nodes for clearnet are hardcoded into the monerod source, does that mean that old versions may not work without an existing p2pstate.bin, because the hardcoded seed nodes might no longer exist?

dANBs[m]: When churning, don't do it immediately (maybe wait a few days between transactions, at least; longer could be better), and try to avoid doing so with the same amount each time, to reduce similarity between transactions or close correlations in time with the same address showing up. Doing it between different addresses should in theory be slightly better, I think. This is based on my

understanding, and I'm not exactly an expert.

dANBs[m]: The sooner you have to move money, the more important it probably is to make it a substantially different quantity, I'd think. It's also probably a good idea to move things after a significant protocol change (again, according to my understanding).

<amoe> "Seed nodes for clearnet are..." <- If you're talking about older versions as in previous hardforks, they're not gonna be compatible with the current network anyway. They'll just get rejected (and they'll reject the hardcoded seed nodes themselves)

is it safe to share transaction id with the receiving party?

yes (they will know the transaction id when the funds arrive)

wait holy shit scan_block is in?

amoe: you can always specify for own seed node with `--seed-node`

*your own

oh its still scan_tx , not scan_block

i was wondering if scan_block was undocumented

yeah scan_tx has been improved/fixed by jberman - my testing the past month (including background scanning with view-key only has found no issues)