13:33:05 <Guest9254> is this somehow based off of ethirium ?
13:34:38 <selsta> no, also please ask generic questions in #monero
13:35:49 <Guest9254> ok thanks
14:44:21 <woodser[m]> running the tests with `make debug-test` for #8518, I see test failures #6: check_missing_rpc_methods and #7: unit_tests
14:44:28 <woodser[m]> however, there is no debug/tests/check_missing_rpc_methods folder to run those tests specifically
14:44:35 <woodser[m]> and for some reason running unit_tests with `ctest --output-on-failure` is hanging
14:44:41 <woodser[m]> how can I run the check_missing_rpc_methods test?
14:56:41 <moneromooo> Looks like: python tests/functional_tests/check_missing_rpc_methods .
14:56:54 <moneromooo> and build/wherever/tests/unit_tests/unit_tests
14:57:31 <moneromooo> You should see the output in LastTest.log as well.
14:58:32 <woodser[m]> ok, thanks
15:02:46 <woodser[m]> hm for some reason the tests/functional_tests/check_missing_rpc_methods folder wasn't generated
15:09:55 <moneromooo> Do you mean "the tests/functional_tests/check_missing_rpc_methods.py file does not exist" ?
15:10:14 <moneromooo> It's a python script. It's in git.
15:24:11 <woodser[m]> ah I see. thought it was in ./build
16:31:58 <WillMorrison[m]> is there a flag for monerod to change the size of the blockchain? For example, only keeping the last 500 mb of blockchain data.
16:34:05 <moneromooo> --prune-blockchain (only needed once, it'll stay pruned afterwards).
16:55:03 <WillMorrison[m]> <moneromooo> "--prune-blockchain (only..." <- That prunes it but there's a minimum size there. Can I not lower it? For what I'm working on my node doesn't require any transaction history.
17:00:46 <moneromooo> In theory you can but you'd lose the ability to be useful to other peers, so bad idea.
17:01:14 <moneromooo> And diminishing returns, you would not gain that much on tpo of what pruning gains.
17:02:15 <WillMorrison[m]> Alright, thank you
17:02:42 <hyc> you could certainly develop a "caching" node that only retains info for e.g. the last month's worth of blocks
17:03:05 <hyc> other nodes could still sync from it if they're within the window of time that it covers
17:03:18 <hyc> wallets couldn't really use it tho
17:04:18 <moneromooo> You'd get a seventh of what's currently gained. Which is what... 70 GB ? 
17:04:29 <moneromooo> An extra 14 GB maybe.
17:05:00 <moneromooo> In return for being a useless node,
17:05:30 <moneromooo> Or close to useless. Currently a week's worth if kept at the tip btw.
19:36:54 <w[m]> <moneromooo> "--prune-blockchain (only..." <- With a config file... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/270eead70456c76ebdefc0c52d63e4c607bc8bef)
19:36:59 <w[m]> * With a config file... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/643b6b86b38362a621cf3a76a5900fa6dac45420)
23:15:42 <Palladionhehim[m> Got a problem, my public node has restricted rpc access as it's a public node
23:16:16 <Palladionhehim[m> However, I need to be able to make rpc requests for things like node status and tx details for a chain explorer running on my node
23:16:40 <Palladionhehim[m> What's the safest way to allow these requests? Note: the node tunnels through tor
23:16:55 <Palladionhehim[m> * through tor and uses access it through tor rather than my public IP
23:17:12 <merope> restricted rpc on the exposed network interface/port, unrestricted rpc bound only to LAN/localhost
23:17:31 <merope> you can run both options at the same time
23:18:43 <merope> or if you're tunneling stuff via tor, you only tunnel the restricted port, and you ensure the unrestricted port is only accessible to you locally
23:18:51 <Palladionhehim[m> So bind to two ports, one private and one public and restrict the public?
23:19:03 <merope> yes
23:19:10 <Palladionhehim[m> Alright I didn't think of that haha
23:19:11 <Palladionhehim[m> Thx
23:19:43 <merope> https://monerodocs.org/interacting/monerod-reference/#node-rpc-api
23:20:21 <merope> you use `--rpc-restricted-bind-ip` and `--rpc-restricted-bind-port` for the restricted stuff that you expose via tor
23:20:46 <merope> and the "regular" (unrestricted) `--rpc-bind-ip` and `--rpc-bind-port` for your personal usage
23:21:39 <merope> (double-check this with others, but I'm 99% sure there are no hidden caveats)
23:23:51 <Palladionhehim[m> I will, either way worse case scenario I see someone is mining and shut it doen
23:23:58 <Palladionhehim[m> Or they do it for me XD
23:52:26 <bbqcore[m]> yo guys some shitheads were smack talking XMR and mentioned the "Knacc attack" that supposedly affects CN coins
23:52:57 <bbqcore[m]> legit concern?
23:54:46 <merope> 1) old news
23:54:47 <merope> 2) better suited for #monero:monero.social