01:05:31 <rottenwheel> sgp_: finally, at least one lol.
01:05:44 <sgp_[m]1> rottenwheel: 🎉
01:05:47 <rottenwheel> space is fugged though.
01:05:52 <rottenwheel> rip.
02:22:17 <h2017> hi
02:22:27 <donkeydonkey[m]> yo
02:23:03 <angrymonkeyboi[m> sup
02:23:21 <h2017> chilling
06:09:54 <omega> hello. if i use systemctl start monero ----   how do i use the status command to see in/out connections on my daemon?
06:10:08 <omega> the daemon is detached
06:11:12 <omega> i'm using tail -n100 /var/log/monero/monero.log -   but i want to see -status
06:17:09 <omega> i want to see the total in/out connections
06:18:11 <omega> how to get -status when daemon is detached?
06:57:45 <donkeydonkey[m]> monerod status
07:13:39 <omega> monerod: command not found
07:14:04 <omega> is this why people complain about systemd?
07:14:40 <omega> there is something about systemctl
07:14:57 <mnt_grrrl> sethsimmons, this does not look right HiddenServicePort 18089 127.0.0.1:18089" | sudo tee -a /etc/tor/torrc
07:15:05 <mnt_grrrl> and tor barfs on it
07:15:47 <donkeydonkey[m]> try find where the binary is and run ./path/to/monerod status
07:18:57 <omega> thank you. i get /opt/monero/monerod status
07:18:58 <omega> 2021-02-17 07:18:44.894	I Monero 'Oxygen Orion' (v0.17.1.9-release)
07:18:58 <omega> Error: Problem fetching info-- rpc_request:
07:35:51 <omega> i had to remove rpc login from .conf to get monerod status to work
07:36:08 <omega> probably can pass the login detail with status request somehow
07:36:55 <omega> thanks so much for your help.
07:41:04 <donkeydonkey[m]> no prob. here is some docs https://monerodocs.org/interacting/monerod-reference/
07:41:38 <omega> thanks!
07:42:46 <omega> i am following this guide: https://monerodocs.org/running-node/open-node-tor-onion/   works good.
07:55:04 <DisBotXMR> <Ageless> what channel is best to post in about storing monero securely?
07:56:56 <DisBotXMR> <Ageless> I'm advised to only store small amounts of monero in the GUI under "simple mode"
07:57:37 <DisBotXMR> <Ageless> I want to use my hardware wallet to store all my monero, don't want to do the downloading the blockchain / syncing
07:58:18 <dEBRUYNE> You can use a hardware wallet with simple mode or a dedicated remote node
07:59:10 <DisBotXMR> <Ageless> So, the dedicated remote node, I could set one up on a VPS is it and then connect to that?
07:59:24 <DisBotXMR> <Ageless> that way I could trust the node
07:59:41 <DisBotXMR> <Ageless> and wouldn't have the headache of syncing the blockchain on my laptop every time I want to open the GUI
08:00:14 <DisBotXMR> <Ageless> are my funds ever in danger in simple mode when sending funds? A malicious node cannot steal my funds right?
08:03:02 <steinex> Hi, i have a problem with the Monero GUI. I Choose in the Interface that the current amount of my wallet is shown in the interface, however it just doesn't work. Neither if I choose Kraken or the other options. Any hints?
08:03:14 <steinex> monero-gui-0.17.1.9
08:03:34 <steinex> (I mean in EUR of course, sorry)
08:04:10 <steinex> oh seems i must do a klick. Nevermind then :D
08:09:19 <dEBRUYNE> Ageless: Yes, that would work
08:09:32 <dEBRUYNE> No, the node cannot steal your funds
08:13:46 <DisBotXMR> <Ageless> ok, so it's just as safe to store all my Monero in simple mode with the hardware wallet as it is using my hardware wallet to store bitcoin, can you just confirm that? sorry if its a bit noobish I just need to be told told and told again to feel comfortable about it
08:14:56 <DisBotXMR> <Ageless> I also think the "about simple mode description" is a bit confusing by advising to just use it for small amounts
08:15:22 <DisBotXMR> <Ageless> it seems to be the most convenient secure way to store Monero?
09:15:32 <int6xi3> hey all!
09:15:48 <int6xi3> I'm in trouble...
09:16:34 <int6xi3> The terminal window (Linux) where I'm running monerod from, it's now stuck in some weird resize loop
09:16:43 <int6xi3> it's some UI issue in Debian
09:17:01 <int6xi3> how can i safely quit monerod from a different terminal without corrupting monero's data?
09:17:22 <int6xi3> is it safe to just "kill" it?
10:32:13 <angrymonkeyboi[m> probably 🤷‍♂️
10:33:05 <angrymonkeyboi[m> try just kill, not kill -9
10:36:11 <Infinity8> he d/ced
10:58:00 <grc001[m]> .usd
10:58:22 <grc001[m]> woops my bad, wrong room
11:24:37 <colordungeon> hi everybody, I'm coming in from r/moneromining and have a couple questions about building a miner
11:24:59 <colordungeon> is b-die RAM irrelevant if I'm not overclocking?
11:26:21 <colordungeon> and I see posts here and there on r/moneromining saying not to overclock- what's the reason for this? because overclocking requires a disproportionate amount of power to provide a small amount of additional hashrate? or something else
11:27:18 <moneromooo> Try #monero-pools ?
11:29:42 <colordungeon> can do!
11:33:50 <colordungeon> other question for this channel then: what on-ramp does everyone use to get from fiat to XMR? localmonero is obviously the method most aligned with the principles of Monero, but sending cash through the mail makes me nervous
11:34:33 <moneromooo> I believe kraken is the most well regarded. There's also bitfinex and binance.
12:16:26 <duso> How long have you had to log in to use shapeshift?
12:27:40 <gingeropolous> full block alert: https://xmrchain.net/block/1316df6346f595f1a3b9655294273cc31e1d8d457819b9c9647ec619086431a0
12:32:23 <DisBotXMR> <Ageless> I am having issues sending my monero using trezor with the GUI
12:32:24 <DisBotXMR> <Ageless> https://cdn.discordapp.com/attachments/620459189097201669/811575773110206474/Screenshot_2021-02-17_at_20.29.26.png
12:32:48 <DisBotXMR> <Ageless> I downloaded the latest firmware before using it with the gui
12:35:56 <DisBotXMR> <Ageless> I think I have 2.3.4, still get prompted to do 2.3.5 and 2.3.6
12:36:53 <DisBotXMR> <Ageless> supposedly it was fixed in 2.1.7 https://www.reddit.com/r/Monero/comments/dm0zqx/trezor_transaction_failure_code99_message/f4wia95/
12:52:55 <DisBotXMR> <Ageless> nvm it didnt update it to the latest firmware for whatever reason ill try again
13:28:24 <al> is there any way to run monerod on v6-only?
13:29:05 <al> --p2p-use-ipv6 doesn't seem to do anything
13:37:27 <moneromooo> --p2p-use-ipv6 enables it, but does not prevent ipv4. I don't think you can do v6 only.
14:05:54 <al> moneromooo, I don't want to prevent v4, I just don't have v4 on this machine
14:25:17 <ndorf> hm, there are only ipv4 seed nodes. maybe you need to specify ipv6 peers manually?
14:25:43 <pyu> World Econimic Forum's musing on "Crypto, what's good for": http://www3.weforum.org/docs/WEF_Cryptocurrency_Uses_Cases_2020.pdf
14:26:34 <ndorf> the seed nodes are here: https://github.com/monero-project/monero/blob/b731f7dca2590ade73e42425d421a47857e1a9bc/src/p2p/net_node.inl#L696 maybe try converting one or more to ipv6 notation and passing the result to --add-peer ?
14:26:40 <blaeks[m]> truth is within your enemy \m/
14:27:22 <blaeks[m]> <pyu "World Econimic Forum's musing on"> the truth is within your enemy \m/
14:27:34 <moneromooo> al: then try --p2p-ignore-ipv4
14:34:17 <al> ndorf, moneromooo, thanks. the issue is indeed that all seed peers are v4 only
14:34:49 <al> the notation isn't the issue though, this machine simply doesn't have ipv4 connectivity
14:35:19 <moneromooo> Oh I see. Let me see if I can find an IPv6 peer somewhere...
14:35:19 <al> I'll try starting my own seed on a dual stacked machine and try --add-peer'ing that one
14:36:22 <moneromooo> Does --add-peer 2a01:4f8:c0c:7b27::1:18080 work ?
14:36:46 <moneromooo> The issue you will have is that I think most known IPv6 peers are assholes :)
14:36:56 <moneromooo> As in, they lie to you.
14:37:12 <moneromooo> So you'll have a tenuous connection to the monero network without IPv4 or tor.
14:39:16 <al> unsurprising if ipv6 p2p is disabled by default :=
14:44:50 <al> moneromooo, --add-peer with an ipv6 doesn't seem to do anything, I tried --add-peer '[2a01:4f8:c0c:7b27::1]:18080' as well, but don't see any connection or log lines at log level 2
14:46:09 <moneromooo> Can you ping the IP ?
14:48:47 <al> 64 bytes from 2a01:4f8:c0c:7b27::1: icmp_seq=1 ttl=48 time=12.0 ms
14:49:12 <al> I also checked with tcpdump, there were no packets to that IP
14:49:47 <moneromooo> Then --add-peer  '[2a01:4f8:c0c:7b27::1]:18080' --log-level 1,net*:TRACE
14:49:56 <moneromooo> Then paste the relevant log to paste.debian.net
14:50:21 <moneromooo> (after, say, 30 seconds to be sure)
14:56:39 <al> hitting the 150 kb limit :)
14:56:50 <al> https://paste.debian.net/1185831/ is from the top, https://paste.debian.net/1185832/ bottom
14:57:20 <al> 2a01:4f8:c0c:7b27::1 doesn't show up in the log
14:58:50 <moneromooo> Try --add-exclusive-node instead of --add-peer
14:59:22 <moneromooo> Though: Network is unreachable when trying an IPv6 address. Doesn't look good.
15:00:34 <moneromooo> You might wnat to try --p2p-bind-ip N with N being an interface with an IPv6 address. Kind of a shot in the dark though.
15:00:54 <moneromooo> My machine does not have IPv6 so I can't debug that. Someone else will have ot.
15:16:07 <DisBotXMR> <Fyse> is this a two-way chat?
15:16:41 <moneromooo> almost certain it is.
15:16:57 <moneromooo> Well...
15:17:11 <moneromooo> Actually N-way with varying N, usually > 2.
15:17:17 * moneromooo pedantic
15:22:57 <DisBotXMR> <Fyse> makes sense
15:33:45 <al> moneromooo, where did you see network unreachable for an IPv6? I think these were related to IPv4
15:37:42 <al> with exclusive node I get:
15:37:42 <al> 2021-02-17 15:35:55.810 E Failed to resolve 2a01:4f8:c0c:7b27::1
15:37:42 <al> 2021-02-17 15:35:55.810 I 0[priority]Connect failed to [2a01:4f8:c0c:7b27::1]:18080
15:38:06 <al> and no packets put on the wire
16:40:44 <moneromooo> al:
16:40:45 <moneromooo> 2021-02-17 14:53:03.260 D Trying to connect to ::ffff:66.70.207.166:3280, bind_ip = 0.0.0.0
16:40:50 <moneromooo> 2021-02-17 14:53:03.261 T Some problems at connect, message: Network is unreachable
16:43:06 <al> moneromooo, that's not really an IPv6 though, that's an IPv4 in SIIT notation
16:43:44 <al> it's odd that monerod sometimes uses this and sometimes plain IPv4 notation
16:45:58 <moneromooo> AFAIK these are IPv6. "Not really" is not a good description. Either they are IPv6 or not.
16:47:19 <moneromooo> And I said before, a known asshole added these to the peer lists to try and snare more people into using his lying nodes.
16:47:46 <moneromooo> So peer lists have both the IPv4 and the IPv6 corresponding to the same host.
16:48:23 <moneromooo> Now, maybe the boost network code uses IPv4 to connect to those, I cannot say.
16:50:16 <moneromooo> One thing I know is that my node can connect to those IIRC, and it's not set up for IPv6.
16:50:27 <moneromooo> But the addresses are IPv6 for sure.
16:51:03 <moneromooo> Anyway, you might want to consider tor instead ?
16:52:11 <ndorf> can't sync over tor right? only relay tx?
16:54:05 <gingeropolous> ndorf, i think you *could* sync over tor. i imagine it would take a while
16:54:27 <moneromooo> With torsocks, you can do everything.
16:54:39 <moneromooo> Though historical chain sync is not a good idea :)
16:55:03 <ndorf> makes sense
17:02:28 <moneromooo> Anyo coder around set up with IPv6 who wants to investigate this ? :)
17:05:03 <ndorf> i kind of do want to investigate this but none of my nodes have ipv6
18:42:29 <jivan> moneromooo: You're better off asking in ##networking, but since you're here
18:43:08 <jivan> That notation is for IPv6-address aware apps to use. The OS still needs to translate it under the hood into an IPv4 address and use its IPv4 stack (if it exists) to communicate with the IPv4 host that the address refers to
18:44:04 <jivan> For example, my ISP only provides IPv4 support (idiots), so if you want to talk to me from an IPv6 host, you need an IPv4 connection also
18:44:10 <jivan> If you don't have one, tough luck, you can't talk to me
18:45:14 <jivan> If you do, then you can tell IPv4-aware programs that my address is 1.2.3.4, or you can tell IPv6-aware programs that my address is ::ffff:1.2.3.4, or ::ffff:102:304
18:45:41 <jivan> Then your OS will talk to me using IPv4
18:47:04 <ndorf> there is NAT64, if the IPv6-only host's gateway supports it. it uses some other prefix though
18:47:30 <jivan> Indeed, there are a bunch of tunneling protocols to work around this issue, but none of them mean that either host is actually speaking the other protocol
18:47:42 <jivan> It's just middlemen doing the translation for you
18:48:20 <jivan> It's basically proxying
19:08:23 <moneromooo> Thanks, makes sense.
19:58:06 <M1312test1312[m]> What are you using instead of xmr.to since it stopped working? I pay many things in BTC where XMR is not available and I don't want to reinstall electrum after years without it...
20:01:17 <ndorf> don't think there is any real replacement for xmr.to. there are other instant exchanges, but they have both much higher minimum amounts and commissions than xmr.to. plus i don't think any of them do zero conf, so exchanges take much longer.
20:01:49 <sech1> I switched to Kraken, but it's far from instant
20:01:51 <sech1> and has kyc
20:02:26 <sech1> I don't trust other instant exchanges, they might give you tainted BTC from other users
20:02:53 <binaryFate> do you spend an equal time reaching out to your merchants and insist they accept XMR?
20:03:11 <ndorf> heh.
20:03:18 <ndorf> i've been trying to convince mullvad to accept XMR for like 3 years
20:03:32 <ndorf> ended up switching to IVPN.
20:03:34 <binaryFate> same, until I left them
20:03:36 <binaryFate> lol same
20:03:40 <ndorf> high five
20:04:04 <ndorf> better yet, high <unknown amount>
20:04:28 <kinghat[m]> why do they accept cash and BTC but not xmr. pretty dumb.
20:04:35 <ndorf> they accept BCH for crying out loud
20:04:47 <ndorf> i even tried using that once just to pay them. took like 5 hours to confirm a single block
20:05:06 <ndorf> never again lol
20:07:52 <sech1> binaryFate my favorite merchants use Bitpay, it's a lost cause
20:09:45 <DatBotXMR> moooooooo
20:11:26 <DisBotXMR> <Bananaboat> swapzone.io
20:11:43 <DisBotXMR> <Bananaboat> they show you all the swap exchanges that trade for XMR no KYC
20:19:35 <ndorf> yeah. and i'd definitely think twice before using any of them to pay an invoice directly
20:20:09 <ndorf> usually it's something like "send X BTC to Y address in 15 minutes" what happens when the exchange takes 20 minutes?
20:20:34 <DisBotXMR> <Bananaboat> oh for sure
20:20:45 <DisBotXMR> <Bananaboat> i wouldnt use it to pay an invoice
20:20:45 <Quotes> peanut butter jelly time!
20:20:45 <ndorf> bonus points if the merchant just auto-refunds to the sending BTC address. oops!
20:21:32 <ndorf> new bot who dis
20:22:36 <nioc> moooooooo
20:42:09 <moneromooo> mooooooo
21:07:02 <fluffydonkey[m]> I have a node fully set up on a (ubuntu) computer with the wallet working on that computer too. I'm trying to connect to it from another computer on the same local network, but the wallet is refusing to connect to the remote node.
21:07:02 <fluffydonkey[m]> How can I get the error log from the wallet to figure out what's going on
21:08:35 <moneromooo> --log-level 2
21:08:48 <moneromooo> The log will be in the same directory as the binary.
21:08:50 <fluffydonkey[m]> I meant GUI wallet
21:08:57 <moneromooo> Ah. Dunno then.
21:09:48 <ndorf> are you sure you enabled the node to listen on external IPs? by default it's 127.0.0.1 only, and unrestricted
21:10:42 <fluffydonkey[m]> That might be what's going on
21:10:50 <ndorf> run the daemon with these flags: --rpc-restricted-bind-port=18089 --rpc-restricted-bind-ip=0.0.0.0
21:11:02 <ndorf> then change the wallet to connect to port 18089 instead of 18081. should work
21:11:22 <ndorf> that sets up restricted rpc, which means the clients can't do things like shut down the node, pop blocks, get certain information, etc
21:13:26 <fluffydonkey[m]> Success!
21:13:47 <fluffydonkey[m]> Why was changing the port necessary? It should have still worked with 18081 right?
21:13:49 <ndorf> awesome
21:13:51 <ndorf> no
21:14:05 <ndorf> 18081 is still bound to localhost-only for unrestricted RPC
21:14:31 <ndorf> i mean, you could expose the unrestricted RPC port too, but that can be somewhat dangerous
21:14:57 <fluffydonkey[m]> I understand now. Thank you
21:15:56 <ndorf> unrestricted rpc allows commands like `monerod exit`, you probably don't want untrusted clients doing that to your node.
21:16:31 <ndorf> that being said, if your whole network is trusted and secure, yeah you could just expose that.
21:16:49 <ndorf> this is the best setup 99% of the time though, IMHO.
21:18:33 <donkeydonkey[m]> to get it working on 18081 with restricted rpc couldnt you also set --rpc-bind-port=18081 --restricted-rpc
21:19:01 <ndorf> yes. but then you don't have unrestricted rpc even locally, which could prove very inconvenient if you run it in the background without the console
21:19:33 <donkeydonkey[m]> good one.
21:20:11 <al> [17:45:58 17.02.2021] <moneromooo> AFAIK these are IPv6. "Not really" is not a good description. Either they are IPv6 or not.
21:20:11 <al> ok, they really aren't IPv6
21:20:31 <al> it's an IPv4 in IPv6 compatible addressing, which can be used on AF_INET6 sockets
21:20:51 <al> hope that's a better descriptiong
21:22:44 <ndorf> donkeydonkey[m]: for a practical example, you wouldn't be able to change the bandwidth limits without restarting the daemon, with that setup
21:23:56 <donkeydonkey[m]> makes sence. i usually have my daemon running in the foreground so didnt think bout that.
21:26:57 <ndorf> gotcha, in that case it does make sense to just not have unrestricted rpc at all
21:48:26 <fibonacci> Good for you guys.. bout time
22:01:21 <DisBotXMR> <Izay21> Can someone help me setup a miner
22:01:52 <sethsimmons> <DisBotXMR "<Izay21> Can someone help me set"> Better question for #monero-pools, most likely.
22:15:11 <kjartan> Is there an explanation out there for the sawtooth-pattern that the volume on Monero is showing? Just curious...
22:15:23 <kjartan> https://i.ibb.co/pvPWx7W/image.png
22:16:13 <sech1> yes there is
22:16:40 <ndorf> that includes exchanges that straight up fake their volume.
22:17:25 <kjartan> But during the middle of December that didn't happen?
22:17:51 <ndorf> either that, or cmc wasn't including that exchange during that time
22:18:19 <ndorf> it's not really a realiable source for this kind of data. pick the exchange you think you can trust, and get it from them directly
22:18:27 <ndorf> exchange(s) i should say
22:20:57 <kjartan> I agree. Looks like the pattern started around 11th september last year with some huge spikes. Probably illuminati.
22:32:29 <DisBotXMR> <Cesium> is there any reason for me to not want to set up a node on a machine at home and forward a restricted port to the open internet so I can use the node on my laptop away from home?
22:34:48 <ndorf> Cesium: none, just make sure you open and forward the restricted RPC port, not the default unrestricted one
22:35:11 <ndorf> Cesium: if you don't want random strangers using your node you can set a user/pass on it, or require mining payment for RPC
22:35:46 <DisBotXMR> <Cesium> thank you
22:36:01 <ndorf> Cesium: alternatively you could use ssh tunneling and not forward any ports at all
22:36:08 <ndorf> well, aside from the ssh port, heh
22:37:11 <DisBotXMR> <Cesium> i already used ssh to do it but I just want to be even lazier
22:54:36 <rojiro[m]> is this the same channel as #monero on freenode?
22:54:41 <ndorf> yes
22:55:00 <ndorf> it's bridged. i'm connected to freenode
22:55:59 <rojiro[m]> what it's strange is that I am not seeing my chats from freenode. Perhpas it's knows since I have the same username in both places?
22:56:23 <ndorf> could be something like that. you're seeing my messages? i assure you i'm sending them to freenode :)
22:56:56 <rojiro[m]> yeah, i see your's. Must be some sort of filter for your own nick or something...
23:24:10 <Infinity8> This is freenode
23:25:14 <xfil> matrix users are the worst
23:25:19 <Infinity8> ban them all
23:35:02 <angrymonkeyboi[m> The 1980's called. They want their chat protocol back