04:33:13 <rotten> Revuo Issue 87 - https://revuo-monero.com/issue-87.html
04:35:12 <tobtoht> fluffypony: mymonero.com SSL cert expired
06:03:39 <fluffypony> tobtoht: tks we're fixing
12:07:24 <marcimbimbo> https://twitter.com/hyc_symas/status/1203709575226183683
12:07:27 <marcimbimbo> Last time I got an award like that was in a primary school football team. It had three stars too and said that I'm special :')
12:07:30 <marcimbimbo> I just binned it though instead of showing it off to naive groupies.
12:10:37 <mechanic41turk[m> <marcimbimbo "I just binned it though instead "> ok, you are just so cool to value such a certificate.
12:25:38 <ErCiccione[m]> mechanic41turk: please ignore the spammers
12:26:01 <mechanic41turk[m> ErCiccione: sure.
13:59:27 <raivavae> hello
13:59:53 <raivavae> some strange output when monerod start
13:59:55 <raivavae> http://paste.debian.net/1176983/
14:01:11 <moneromooo> This is from the logs, right ? You don't get that displayed ?
14:01:25 <raivavae> yes
14:01:31 <raivavae> from monerod logs
14:01:39 <moneromooo> Is anything not working ?
14:02:01 <raivavae> monerod works but this is very strange
14:02:19 <moneromooo> Are you a programmer ?
14:02:51 <raivavae> no but i give a try
14:03:45 <moneromooo> Then this is a stack trace, it shows the state of the call stack at a given point in the execution, here in this example when it tried to allocate some memory.
14:03:47 <raivavae> do i need to update anything for this logs to dissappear
14:04:24 <moneromooo> You can run with --log 0,*stack*:FATAL if you dont' want them.
14:04:57 <moneromooo> If it's because it\'s just spammy, there's a recent PR to just log it once.
14:05:33 <moneromooo> This particular one means (IIRC) that you don't have enough memory to start a miner. I could be wrong there.
14:05:45 <raivavae> so is smth that dont need to be fixed
14:06:12 <moneromooo> Well, you can try to free more memory. Or just ignore.
14:06:38 <raivavae> ok not smth serius
14:06:44 <raivavae> thnx a lot!
15:22:47 <doctorx> Hello. I have a question regarding RAM usage of "monerod.exe". I'm running a full node, public, on Windows, with 12 GB of physical RAM. When I launch "monerod.exe", the RAM starts slowly climbing up. I don't see that RAM pinned to a specific service or application in Task Manager so, I'm guessing this is monerod.exe buffering it's database in memory, using all of the available RAM?
15:25:05 <moneromooo> Yes.
15:28:13 <sech1> moneromooo there's also 7098 where I fixed one memory leak
15:30:49 <moneromooo> Indeed :)
15:38:31 <doctorx> moneromooo: Thank you for responding so fast. Is it possible to limit that or is it just by design?
15:38:57 <ksk> doctorx: It is most likely windows keeping in "cache" every bit monerod touched, so to say, since you have "free ram"
15:38:58 <Quotes> fuck windows, use linux!
15:39:24 <ksk> doctorx: as long as you dont run into problems running other applications there is no problem with the observed behaviour.
15:40:10 <doctorx> Well, I have, and I have not. For instance, if I wanna launch another app that requires a big chunk of RAM, it gives me errors.
15:40:35 <doctorx> As long as I don't open any other app that requires a high amount of RAM, it seems to run nicely.
15:41:05 <ksk> doctorx: also see: Windows ressource monitor or what its called, and its memory tab. Is this memory green (== not usable for anything else), or rather blue (thus cache, which can be reclaimed)
15:42:23 <doctorx> monerod.exe working set 8.6 GB
15:45:47 <moneromooo> By design. Though your OS might have knobs for this.
15:46:59 <moneromooo> In theory, the OS should be able to discard the cache but in practice when the pressure is fast and high, it might not work.
15:50:00 <ksk> Mhm yea, 3.5G of ram might just not be enough nowadays to "surf the web" :X
15:57:55 <Jaska_> lynx?
16:12:09 <doctorx> Thanks for the help. I appreciate it.
17:39:28 <donkeydonkey[m]> hi y'all. im looking for docs on best practices for running a public node. i found the page for running a node on monero.how which has a section about public nodes. is there any other good articles or such on running a public node?  thanks
17:40:39 <moneromooo> moneroworld.com is more likely than not to have something.
17:41:04 <moneromooo> Otherwise... use --restricted-rpc at least
17:41:22 <moneromooo> Maybe set up the pay-for-rpc system
17:41:44 <donkeydonkey[m]> word. i would like to do that
18:46:53 <sethsimmons> I've opened two PRs to add the ban-list to BTCPayServer if anyone who uses it (or has Docker experience) wants to test:
18:46:53 <sethsimmons> https://github.com/btcpayserver/dockerfile-deps/pull/18
18:46:53 <sethsimmons> https://github.com/btcpayserver/btcpayserver-docker/pull/413
18:53:10 <tobtoht> sethsimmons: can't test right now, but looks good
18:53:48 <sethsimmons> Sweet, please comment on those if/when you are able to test.
18:53:48 <sethsimmons> It's such a simple change I'm not sure how it could break, but don't want to break Monero further for BPS users :P
19:40:12 <donkeydonkey[m]> <moneromooo "Maybe set up the pay-for-rpc sys"> ok this pay-for-rpc is pretty cool! deff gonna have to make me a dashboard. the credits are a super cool idea! good work!
19:46:13 <donkeydonkey[m]> so on the public node does the monero daemon have to be background mining to use the hashes that are submitted to it? or does it somehow use those hashes that the clients submitted to it automatically?
19:48:51 <moneromooo> It does not. It uses them somehow.
19:50:05 <donkeydonkey[m]> rad
19:53:48 <donkeydonkey[m]> on the wallet-cli i set the credits-target option and it works great. though i noticed that the wallet-cli will stop doing this auto mining if i stop using the cli... tben when i enter another command on the cli it starts doing its credit-target mining.. is there a way to keep the cli going even if i stop entering new commands in the cli? thanks
19:57:42 <moneromooo> Had it reached its target (rpc_mining_info) ?
20:01:28 <donkeydonkey[m]> no
20:01:56 <donkeydonkey[m]> rpc_payment_info
20:07:47 <donkeydonkey[m]> its working now. i had 2 wallets connected to the node. i restarted everything and not its keeping going. its only stopping when it should at the credits-target. so no issue.
20:22:04 <donkeydonkey[m]> * now its keeping going"
21:38:57 <Beags[m]> after restoring from nmemonic seed, I currently have an empty Monerujo wallet and I'm not sure why. i changed the restore height to months before my first monero just to be safe
21:39:56 <Beags[m]> reason i restored is becsuse when trying to access the original wallet, it says 'node connection failed. check username/password'
21:40:23 <Beags[m]> is it possible to have xmr stolen by a public node? ive only ever used the defaults
21:40:55 <sethsimmons> No, they can't steal your XMR.
21:41:28 <sethsimmons> Try a different node like from here: https://community.xmr.to/nodes.html
21:41:40 <sethsimmons> Or run your own and be sure the restore height is properly set.
21:41:56 <sethsimmons> Or try restoring the wallet from see in the GUI/CLI wallets
21:42:35 <Beags[m]> as in full node wallet on pc?
21:42:45 <Beags[m]> thats worth a try, thanks
21:42:55 <sethsimmons> Yes, or use CLI/GUI with a remote node as well if needed.
21:43:02 <sethsimmons> But running your own node is always recommended.
21:44:43 <Inge-> Beags[m]: you only need to worry about stolen coins when you have synced the wallet so you see your old transactions AND a new unknown transaction emptying your wallet.... If you see no transaction history, you just aren't synched yet
21:47:07 <Beags[m]> thats a good point. theres no transaction history listed
21:47:45 <Beags[m]> * thats a good point. theres no transaction history listed, although its showing synced
22:06:34 <fehho[m]1> <Beags[m] "thats a good point. theres no tr"> Check that the sync is to the correct block according to a second source like https://localmonero.co/blocks and that the restore height is set to a block before any monero was sent to the wallet. I can't see what you said previously, only that it seems you have a wallet which should have monero in it without any monero in it.
22:11:30 <Beags[m]> monerujo is acting strangely, so im trying with cake wallet
22:17:38 <Beags[m]> okay that worked. cake wallet shows the xmr
22:18:44 <Inge-> I'd guess there was an issue with the node monerujo was connecting to