00:00:24 <algo_max[m]> ? i think the data dir is fine.. it's synching and saving blocks right now
00:00:34 <dsc_> if the data dir is working then you are running under root
00:00:40 <dsc_> which is not fine
00:00:43 <dsc_> ^_^
00:01:04 <algo_max[m]> i'm running this inside a docker container
00:01:10 <dsc_> ah okay. Fair enough.
00:01:24 <algo_max[m]> not root.. i created /monero-data and chowned it :)
00:01:33 <algo_max[m]> so that should be fine
00:02:17 <dsc_> so 18080 is indeed for p2p traffic, it allows you to distribute the blockchain to other peers
00:02:42 <dsc_> 18081 is the RPC port which allows wallets, such as the CLI, GUI, Cake, Monerujo and possibly other programs to connect to it
00:03:26 <dsc_> which one is more important for the network depends on who you ask :P
00:03:54 <dsc_> If you ask me I'd say 18081
00:04:15 <dsc_> because it allows users that are too lazy to run their own node to use Monero
00:05:26 <algo_max[m]> will users have to enter my ip / hostname in their wallet so they can use my RPC services? because i'm on a dynamic ip. does it still make sense for me to publish 18081?
00:05:57 <manifest> yes, dynamic dns is an option though
00:05:58 <dsc_> Wallets will be able to find you regardless if you publish the IP somewhere or not
00:06:22 <algo_max[m]> fine then i'll keep 18081 open too
00:06:35 <dsc_> great! thanks for supporting the network :)
00:07:34 <algo_max[m]> any idea how to get rid of the error "monerod status" is giving me?
00:08:07 <algo_max[m]> i used it to check the incoming and outgoing number of connections.. but since i added --restricted-rpc i get this error
00:08:42 <dsc_> how are you accessing monerod if its running with docker as a service?
00:08:53 <dsc_> or is monerod the entrypoint of the dockerfile?
00:09:02 <algo_max[m]> i made it the entry point
00:09:11 <algo_max[m]> and i open a second shell with docker exec -it bash
00:10:12 <dsc_> type `status` in the terminal thats running monerod
00:10:20 <dsc_> well
00:10:28 <dsc_> does `print_cn` work there?
00:10:47 <algo_max[m]> oh nice i didn't know you could type there :) this works, thanks
00:10:51 <dsc_> cool
00:11:26 <algo_max[m]> print_cn works too. both show some incoming connections already so this seems to be working.
00:11:43 <dsc_> theres also print_pl
00:11:56 <dsc_> (peerlist)
00:19:14 <algo_max[m]> print_pl shows my ip address already, but listed as gray (offline?)
00:50:34 <gingeropolous> hrm, i wonder how p2p rpc service advertising works with dynamic IP
00:50:48 <gingeropolous> well prolly the same as p2p service
00:51:07 <gingeropolous> though it'd be hard to maintain an "account" if your using RPC-pay
07:18:28 <rot> Revuo Issue 77 - https://revuo-monero.com/issue-77.html
10:08:38 <algo_max[m]> What are the columns that monderod print_pl outputs? It doesn't show a header so it's kinda hard to tell. Documentation also doesn't tell..
10:08:41 <algo_max[m]> white      e78520536f7c3deb          116.203.182.15:18080      18089 -     0    d0.h9.m34.s55
10:08:41 <algo_max[m]> white      9b93cb498a7656b8          23.19.58.16:18080         -     -     0    d0.h1.m49.s10
10:09:00 <algo_max[m]> I can make sense of the first columns, but not of the last 3 columns
10:50:39 <Mochi101> algo_max[m], last column is a date... last seen or last connected probably
10:51:06 <Mochi101> d = days, h = hours, m = minutes...
10:53:36 <Mochi101> I think the 0 is the RPC Credits
10:56:33 <Mochi101> ah no... the third from the right column is RPC credits per hash
11:56:43 <TheCharlatan> algo_max : https://github.com/monero-project/monero/blob/master/src/daemon/rpc_command_executor.cpp#L91 . Last column is last seen indeed.
11:59:28 <TheCharlatan> it's disappointing though that none of the tables in the daemon output have labels on their columns.
17:29:56 <pantanero> hi all, how i can verify in monero-wallet-cli the current value of a variable? not willing to set it up.
17:30:16 <pantanero> [wallet xxx]: set subaddress-lookahead
17:30:23 <pantanero> doesn't work
17:37:06 <moneromooo> set
17:57:47 <pantanero> moneromoo: thx
18:06:06 <pantanero> one little comment: isn't the "set helper explanation reversed"?
18:06:15 <pantanero> subaddress-lookahead <major>:<minor>
18:06:22 <pantanero> Set the lookahead sizes for the subaddress hash table.
18:06:37 <pantanero> CLI output default from set command
18:06:52 <pantanero> subaddress-lookahead = 50:200
18:07:43 <pantanero> maybe the legend should be: subaddres-lookahead <minor>:<major>?
18:12:48 <moneromooo> Looks OK to me. Can you be more precise about where you think the mixup is ?
18:19:17 <dEBRUYNE> pantanero: major is accounts, minor is subaddresses for each account
18:19:25 <dEBRUYNE> So the hierarchy is correct
18:28:40 <algo_max[m]> TheCharlatan, Mochi101 thanks.. rpc_credits_per_hash % pruning_seed % elapsed 👍️
18:31:37 <pantanero> now with explanation i understand major is for the account and minor for the subbaddress. I thought that it was an interval between 50 and 200.
18:34:02 <pantanero> thnx one time more
19:13:32 <endor00[m]> So by reducing the lookahead to, say, half the accounts, I can effectively reduce the scan time in half?
19:14:43 <endor00[m]> Because 50:200 seems like a veeery generous number for my usage
20:03:35 <selsta> endor00[m]: no
20:04:10 <selsta> only difference is that it is faster to initially create the wallet when using a smaller lookahead
20:05:54 <endor00[m]> is it because by the time I reduce it, it has already generated the keys associated to the accounts and subaddresses, so it will keep checking them anyway?
20:07:04 <selsta> subaddresses use a lookup table so half subaddresses does not mean half scan time
20:07:22 <selsta> basically there should be next to no difference in scan time
20:07:35 <selsta> but creating the initial lookup table is slower
20:07:39 <endor00[m]> what about half accounts?
20:08:40 <endor00[m]> same difference?
20:11:22 <selsta> should also be no scan difference
20:29:04 <MalMen> anyone know the link for that layer paper for "privacy" coins ?
20:30:44 <ndorf> MalMen: this? https://www.perkinscoie.com/en/news-insights/anti-money-laundering-regulation-of-privacy-enabling-cryptocurrencies.html
20:30:54 <MalMen> exactly
20:30:56 <MalMen> thank you
20:31:04 <ndorf> np