00:35:55 <Elon_Sat0shi> no problemo
00:38:36 <Elon_Sat0shi> How well does Monero protect one's privacy without tor?
00:44:35 <as2333> how well does tor protect privacy?
00:49:34 <Febo> Monero makes sure that transactions cant be linked. That is all. While you use Monero you show your IP to network. I dont really know who can see it. But that is all. They cant link transactions with it. To hide IP, using TOR is probably helpful.
01:17:03 <Elon_Sat0shi> ah
01:18:08 <Elon_Sat0shi> When I make a transaction with monero, what is known about my transaction?
01:23:15 <louipc> nothing
05:32:12 <bigslim[m]> somehow I managed to not update my monero gui snce 14.1 release
05:32:42 <bigslim[m]> that 15.2 is interesting. USD price does not work though when enabled on OSX
05:33:00 <bigslim[m]> and coingeko
06:03:55 <selsta> bigslim[m]: What does not work exactly?
09:07:38 <wuzhe> hello, community! i want to build a monero randomX mining pool service but i dont have a lot of hash, where should i start? https://github.com/jtgrassie/monero-pool?
09:12:48 <wuzhe> Or, can i start a proxy service link between worker and pool exists, and statistic the contribute for every worker? i need some experience, thanks
14:48:14 <moneromooo> Does anyone have a non working rpc payment setup here ? IIRC someone reported it wasn't working. I've just tried to repro here, and it's working fine. If anyone has a non working one and is willing to run with, and share, logs, please let me know.
14:49:35 <moneromooo> Note that with randomx, there's a definite temporary hang while it inits the data set, so rpc_payments in the wallet will hang till that's finished, and it can take like a minute.
14:50:21 <moneromooo> That's something I might be able to fix by settings atomic flags in the general area so I don;t have to lock...
14:50:57 <moneromooo> gingeropolous: that might have been you ? You seem the type to try it :)
14:55:57 <Copenhagen_Bram> hello
14:56:23 <q9fmc> hi
14:56:49 <Copenhagen_Bram> If I'm running Monero on a Tails persistant volume that's only 8gb, should I run a pruned node or connect to a remote node?
14:57:10 <moneromooo> The pruned node will be about 25 GB, so too large.
14:57:32 <Copenhagen_Bram> oh kay
14:57:38 <moneromooo> You can run the daemon on a separate non TAILS machine, since it has no access to your keys. Then connect to that.
14:58:48 <Copenhagen_Bram> Okay. But that kills Tor's anonymity unless others are also connecting to your node
14:59:50 <moneromooo> If your node is on your home connection, then yes.
15:00:08 <moneromooo> Depends what you want to guard against really.
15:05:18 <moneromooo> What do you want to guard against ? :)
15:05:27 <Copenhagen_Bram> What kind of threat can a remote node pose even if you're connecting to it via tor?
15:06:04 <moneromooo> They can DoS you. They can send you blocks which are not on the chain. If they know your address (or know your address is within a set of possible ones), they can fake payments do you.
15:06:20 <moneromooo> The attack surface is larger (all the RPC).
15:06:44 <Copenhagen_Bram> ah
15:06:52 <moneromooo> Not running your own node means the network is less strong than it'd otherwise be.
15:07:20 <moneromooo> What is something you can't live with here:
15:07:38 <moneromooo> - run a monerod hidden service from your home connection
15:07:54 <moneromooo> - connect to it with TAILS from wherever you are (possibly your home connection too)
15:08:29 <moneromooo> I guess your ISP could perform traffic analysis to know it's you since they see both in and out and Tor is realtime.
15:08:40 <moneromooo> I think that's pretty much it.
15:09:12 <moneromooo> But if you connect from home, you can connect to monerod via localhost anyway.
15:09:45 <moneromooo> So if you connect from outside, there's not much I see that's leaking (but then that's from a first approiximation, please list what you can think of).
15:10:50 <Copenhagen_Bram> A hidden service node? Hmm, that might prevent someone from seeing the IP of your node
15:10:57 <moneromooo> I'm not even sure the ISP can tell you're running monero. Maybe by statistical analysis of packet sizes and access timing.
15:12:39 <moneromooo> Define "seeing the IP of your node", because it's the canonical thing bandied by people with a clue who've heard of IP addresses before.
15:12:47 <moneromooo> without a clue.
15:13:12 <moneromooo> Do you mean "my ISP will know the subscriber at this IP address is running a monero node" ? Other ?
15:13:47 <moneromooo> If the former, it won't know unless it performs that kind of statistical analysis I think. I don't know how involved it'd need to be.
15:14:25 <moneromooo> I expect that with enough time and enough variation in tx volume/block size, it might be fairly easy if the tor node isn't used for somehting else...
15:14:50 <Copenhagen_Bram> I mean if my node isn't a hidden service, it will have an address, be it a domain name or an IP, and exit nodes can see connections to it
15:14:55 <moneromooo> Though vtnerd added some noise feature for this.
15:15:27 <moneromooo> Ah. An exit node would be able to see someone connecting to a monerod daemon, yes.
15:15:28 <Copenhagen_Bram> And I don't know how hidden services work exactly so I'm not sure if someone sees connections to hidden services
15:16:01 <moneromooo> They don't go through exit nodes, but rendezvous nodes, the connection is not plaintext at the handoff.
15:16:09 <moneromooo> I don't know the details either.
15:16:46 <moneromooo> But an exit node can get a list of monerod nodes around by running monerod itself. It'll get a list much faster too.
15:17:36 <Copenhagen_Bram> Is there a remote node address that redirects to a random remote node?
15:17:44 <moneromooo> If you don't want anyone to know there is a monerod node running on your IP (ie, you're in a country where using a cryptocurrency is a crime), then you'd need a hidden service. Though running tor would likely also be illegal I'd guess.
15:17:57 <moneromooo> Yes. I won't help you with that though.
15:19:25 <moneromooo> Oh, I forgot: thre's also a proxy-through mode for monerod, where it doesn't download the chain and auto uses another public RPC daemon, the list of which can get fetched via P2P.
15:19:44 <moneromooo> So if you need to use a stranger's daemon despite the possible drawbacks, that's the best way to do it.
15:20:58 <Copenhagen_Bram> You mean the client can pick a random public daemon in a p2p way?
15:22:09 <moneromooo> Yes.
15:22:37 <moneromooo> You use "--bootstrap-daemon address" IIRC, and address can now be "auto". Plus --no-sync.
15:22:54 <Copenhagen_Bram> Huh
15:34:56 <Copenhagen_Bram> I don't see a --no-sync option in monero-wallet-cli --help
15:35:22 <asymptotically> it's an option for monerod
15:35:59 <Copenhagen_Bram> Oh
15:37:39 <Copenhagen_Bram> What does --no-sync have to do with --boostrap-daemon auto?
15:37:43 <Copenhagen_Bram> What does --no-sync have to do with --boostrap-daemon-address auto?
15:39:05 <asymptotically> mooo mentioned it above. you can use the bootstrap feature to connect to a random public node
15:39:29 <asymptotically> so your wallet connects to the "--no-sync --bootstrap-daemon auto"'d local daemon, which connects to a public daemon for you
15:40:27 <Copenhagen_Bram> Oh okay
15:41:41 <Copenhagen_Bram> Maybe I want to run --public-node on my node and run my wallet with --bootstrap-daemon-address auto
15:42:40 <Copenhagen_Bram> Can a remote node see what addresses I have?
15:47:25 <moneromooo> As in monero addresses ? No.
16:05:51 <Copenhagen_Bram> oh neat
16:14:12 <bigslim[m]> @selesta when you select the coin conversion it does not show any conversions anywhere that I could find
17:31:26 <Copenhagen_Bram> For some reason, my monero syncing has halted
17:33:46 <nioc> turn it off and on again
17:39:58 <Copenhagen_Bram> I think I've tried that
17:40:11 <Copenhagen_Bram> I'm trying it again, but I noticed that I keep getting this error:
17:40:27 <Copenhagen_Bram> https://termbin.com/nst1
17:41:10 <moneromooo> You got bitten by the corruption bug. The only known fix is... delete db and resunc :(
17:41:56 <moneromooo> Are you using a pruned db ? Are you using --block-notify or --tx-notify ? What version of libunbound is monerod using ?
17:41:59 <hyc> wish we could reproduce whatever's causing that
17:43:15 <Mochi101> How can I resunc my db moneromooo ?
17:44:28 <Mochi101> ;)
17:44:54 <moneromooo> delute it and run monerod agaun.
17:45:32 <Mochi101> :D
17:55:57 <Copenhagen_Bram> nope i'm not pruning my db
17:56:04 <Copenhagen_Bram> that's the only fix?
17:56:55 <hyc> pretty much. you might try starting up with --db-salvage and see if it gets pastthat error
17:57:35 <hyc> but it seems unlikely. the damage usually is in a block too far in the past for -slavage to bypass it
18:07:14 <Copenhagen_Bram> there i did the delet on the blockchain
18:07:28 <Copenhagen_Bram> now we're back to 0%
18:07:47 <Copenhagen_Bram> is there anything i can do to avoid this dreaded corruption?
18:08:00 <Copenhagen_Bram> it might have something to do with my terrible internet connection
18:19:31 <gingeropolous> moneromooo, i got rpc payments to work. some dude on reddit is having trouble with it
18:22:38 <gingeropolous> hyc, what would we need to capture that bug properly?
18:23:06 <gingeropolous> i.e., if we had n machines, all set to just sync on loop, with the hopes of hitting the bug
18:23:25 <gingeropolous> just your standard gdb on a debug build?
18:23:47 <hyc> yes
18:23:56 <hyc> with the debug patches I gave you
18:24:32 <gingeropolous> ok
18:24:51 <gingeropolous> u think it would manifest in a VM? or should I attempt full metal
18:25:09 <hyc> I really have no idea what env conditions it needs
18:25:14 <gingeropolous> hrm
18:25:34 <hyc> you're the one who had it happen once - what was that running?
18:25:53 <gingeropolous> full metal on ubuntu 18 with a spinny
18:26:03 <hyc> so Iguess, keep trying that
18:26:57 <gingeropolous> does it only happen on IBD or does it happen at steady state?
18:27:11 <gingeropolous> i forget where my machine was. the case above seems like IBD
18:56:14 <qiwiss> hey, does the official node use TCP or UDP for p2p?
18:57:04 <hyc> everything is TCP
18:57:09 <qiwiss> thanks
19:02:30 <qiwiss> i need to change my p2p port. tried --p2p-bind-port, but it either seems to have no effect
19:02:47 <qiwiss> or it doesnt show in the following message
19:03:31 <qiwiss> using 0.15.0.1, tested it on debian an windows
19:07:18 <moneromooo> What message ?
19:16:41 <qiwiss> Binding on 127.0.0.1 (IPv4):18081
19:23:43 <moneromooo> That's the RPC socket, no ?
19:24:04 <moneromooo> Use netstat to see what it's listening on.
19:38:13 <qiwiss> nah, its not rpc. I am currently running windows and will check if it's just the message that doesn't update, but that would be very strange
19:39:37 <moneromooo> Did you use -p2p-bind-port 18081 ?
19:42:13 <moneromooo> I tried here, and I don't get such a message for P2P. You claim it's not RPC. How sure are you of that claim ?
19:43:59 <qiwiss>  Core initialized OK
19:43:59 <qiwiss>  Initializing p2p server...
19:43:59 <qiwiss>  p2p server initialized OK
19:43:59 <qiwiss>  Initializing core RPC server...
19:43:59 <qiwiss>  Binding on 127.0.0.1 (IPv4):18081
19:43:59 <qiwiss>  Generating SSL certificate
19:43:59 <qiwiss>  core RPC server initialized OK on port: 18081
19:44:00 <qiwiss>  Starting core RPC server...
19:44:00 <qiwiss>  core RPC server started ok
19:44:01 <qiwiss>  Starting p2p net loop...
19:44:16 <qiwiss> there are different messages for rpc and p2p
19:45:15 <qiwiss> i tried "--p2p-bind-port 10000"
19:46:19 <moneromooo> Re-read your logs.
19:53:37 <qiwiss> ia m using the cli, the logs are the outout in the terminal i just posted
19:57:29 <moneromooo> The logs you posted show the RPC port in both cases.
20:01:10 <qiwiss> ah! damn, I don't know how I got that wrong... thanks
20:01:21 <nonie> open cmd and try netstat -a -n -o
20:05:31 <nonie> should show something like 0.0.0.0:10000   PID
20:10:52 <qiwiss> yeah, just looked into it and everything works fine. sorry, for some reason I totally got that cli output wrong...
20:11:04 <qiwiss> thanks
22:03:27 <coppa> what would be the official link for the randomx release ? it is to reference the update of the mining algo in the wikipedia page
22:04:51 <asymptotically> as a source of it using randomx? or just a page for randomx
22:05:06 <asymptotically> you could link to the v0.15.0.0 release announcement, or to the github repository of randomx
22:05:22 <coppa> okay thx
22:05:36 <asymptotically> https://web.getmonero.org/2019/11/12/monero-0.15-released.html
22:07:03 <coppa> ah great perfect
22:10:13 <Guest_63> Hello:  monerod_1  | 2019-12-14 22:09:15.971	W [IP:PORT INC]  peer claims higher version that we think (12 for 474305 instead of 11) - we may be forked from the network and a software upgrade may be needed --- Do I need to upgrade and how is the best practice do upgrade ?
22:13:38 <coppa> cant update the english one though (say semi protected)
22:14:10 <coppa> ah ok, will create wikipedia account
22:14:18 <moneromooo> You need to upgrade. Exit monerod (it should have told you there is a new version around with a link), download that version, check it's the correct one (it'll have told you the expected hash), unpack the archive, run the new monerod binary, wait.
22:14:37 <moneromooo> Every 12 hours, it checks for an update, cyan text.
22:14:40 <Guest_63> Thanks!
22:15:03 <Guest_63> Does the monero-rpc also needs and update ?
22:15:24 <moneromooo> Yes, it's also included in the tarball monerod will point you to.
22:15:46 <moneromooo> It should be 0.15.0.1. See "version" in monerod, or monerod --version.
22:16:25 <moneromooo> After upgrading, you'll likely those messages again with version 60, or 13. These are broken nodes, the current version is 12.
22:16:56 <Guest_63> Good to know, thanks! :)
22:17:38 <coppa> argh (is at least four days old and has made at least ten edits to Wikipedia)
22:19:31 <coppa> did only in my language sorry guys
22:27:53 <assratatouille[m> dont know if this is the right channel to ask this stuff, but is there a way for me to pay a bill smaller than 0.001 btc? xmr.to wont allow me
22:30:04 <moneromooo> Make a bitcoin wallet, send 0.01 or whatever xmr.to allows to that wallet, send 0.001 btc to whoever, keep the bitcoin wallet and the remainder for next bill.
22:30:36 <moneromooo> Or complain to the recipient for not asking for monero :P
22:36:30 <assratatouille[m> guess ill just have to pay for two months instead of one on my next pool payout
22:40:49 <assratatouille[m> cause i dont have enough rn
23:06:28 <coppa> was thinking, after bulletproof and the small fees, there could be an opportunity for stripe integration no ?
23:19:52 <q9fmc> no
23:32:59 <ndorf> it's really a shame that mullvad still doesn't accept monero payments
23:53:41 <btgjoseph> fluffypony: hey, are you there?