-
algo_max[m]
? i think the data dir is fine.. it's synching and saving blocks right now
-
dsc_
if the data dir is working then you are running under root
-
dsc_
which is not fine
-
dsc_
^_^
-
algo_max[m]
i'm running this inside a docker container
-
dsc_
ah okay. Fair enough.
-
algo_max[m]
not root.. i created /monero-data and chowned it :)
-
algo_max[m]
so that should be fine
-
dsc_
so 18080 is indeed for p2p traffic, it allows you to distribute the blockchain to other peers
-
dsc_
18081 is the RPC port which allows wallets, such as the CLI, GUI, Cake, Monerujo and possibly other programs to connect to it
-
dsc_
which one is more important for the network depends on who you ask :P
-
dsc_
If you ask me I'd say 18081
-
dsc_
because it allows users that are too lazy to run their own node to use Monero
-
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?
-
manifest
yes, dynamic dns is an option though
-
dsc_
Wallets will be able to find you regardless if you publish the IP somewhere or not
-
algo_max[m]
fine then i'll keep 18081 open too
-
dsc_
great! thanks for supporting the network :)
-
algo_max[m]
any idea how to get rid of the error "monerod status" is giving me?
-
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
-
dsc_
how are you accessing monerod if its running with docker as a service?
-
dsc_
or is monerod the entrypoint of the dockerfile?
-
algo_max[m]
i made it the entry point
-
algo_max[m]
and i open a second shell with docker exec -it bash
-
dsc_
type `status` in the terminal thats running monerod
-
dsc_
well
-
dsc_
does `print_cn` work there?
-
algo_max[m]
oh nice i didn't know you could type there :) this works, thanks
-
dsc_
cool
-
algo_max[m]
print_cn works too. both show some incoming connections already so this seems to be working.
-
dsc_
theres also print_pl
-
dsc_
(peerlist)
-
algo_max[m]
print_pl shows my ip address already, but listed as gray (offline?)
-
gingeropolous
hrm, i wonder how p2p rpc service advertising works with dynamic IP
-
gingeropolous
well prolly the same as p2p service
-
gingeropolous
though it'd be hard to maintain an "account" if your using RPC-pay
-
rot
-
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..
-
algo_max[m]
white e78520536f7c3deb 116.203.182.15:18080 18089 - 0 d0.h9.m34.s55
-
algo_max[m]
white 9b93cb498a7656b8 23.19.58.16:18080 - - 0 d0.h1.m49.s10
-
algo_max[m]
I can make sense of the first columns, but not of the last 3 columns
-
Mochi101
algo_max[m], last column is a date... last seen or last connected probably
-
Mochi101
d = days, h = hours, m = minutes...
-
Mochi101
I think the 0 is the RPC Credits
-
Mochi101
ah no... the third from the right column is RPC credits per hash
-
TheCharlatan
-
TheCharlatan
it's disappointing though that none of the tables in the daemon output have labels on their columns.
-
pantanero
hi all, how i can verify in monero-wallet-cli the current value of a variable? not willing to set it up.
-
pantanero
[wallet xxx]: set subaddress-lookahead
-
pantanero
doesn't work
-
moneromooo
set
-
pantanero
moneromoo: thx
-
pantanero
one little comment: isn't the "set helper explanation reversed"?
-
pantanero
subaddress-lookahead <major>:<minor>
-
pantanero
Set the lookahead sizes for the subaddress hash table.
-
pantanero
CLI output default from set command
-
pantanero
subaddress-lookahead = 50:200
-
pantanero
maybe the legend should be: subaddres-lookahead <minor>:<major>?
-
moneromooo
Looks OK to me. Can you be more precise about where you think the mixup is ?
-
dEBRUYNE
pantanero: major is accounts, minor is subaddresses for each account
-
dEBRUYNE
So the hierarchy is correct
-
algo_max[m]
TheCharlatan, Mochi101 thanks.. rpc_credits_per_hash % pruning_seed % elapsed 👍️
-
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.
-
pantanero
thnx one time more
-
endor00[m]
So by reducing the lookahead to, say, half the accounts, I can effectively reduce the scan time in half?
-
endor00[m]
Because 50:200 seems like a veeery generous number for my usage
-
selsta
endor00[m]: no
-
selsta
only difference is that it is faster to initially create the wallet when using a smaller lookahead
-
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?
-
selsta
subaddresses use a lookup table so half subaddresses does not mean half scan time
-
selsta
basically there should be next to no difference in scan time
-
selsta
but creating the initial lookup table is slower
-
endor00[m]
what about half accounts?
-
endor00[m]
same difference?
-
selsta
should also be no scan difference
-
MalMen
anyone know the link for that layer paper for "privacy" coins ?
-
ndorf
-
MalMen
exactly
-
MalMen
thank you
-
ndorf
np