"dixie__flatline" (matrix.to/#/@dixie__flatline:halogen.city) we all had to start somewhere

quit

I have a node which can't receive incoming connections due to having an external IP that differs from the IP it makes outgoing connections on. I'm working on a patch for issue 5979 which will resolve this, but is there any workaround in the meantime for maintaining sync?

for example, can i manually tell the daemon to make outgoing connections to certain peers, or manually publish its external IP somewhere for other peers to find?

i think there was something on github recently, about the latter (manually specify external IP)

yeah, issue 5979?

there's no way to do it at the moment but i'm working on a patch

just wondering if i can do something to stop my node from having no connections in the meantime

for some reason it doesn't make many outgoing connections, even though the limit is high

and since it has no inbound connections, it loses sync

that's interesting

have you given it enough time to find enough peers?

it's been up for 5 days or so

it occasionally gets one connection

for a while

it vaguely keeps up with the network, as in, at least once a day it is up-to-date

but there are long periods where it has 0 peers and falls behind

that seems strange, like maybe you have something else going on that's preventing you from making those connections

maybe. i mean, it's deployed in a production kubernetes cluster, no other services in the same cluster have any issues

i've shelled into the container and tested connectivity, i can connect out on tcp/18080 without any issues

is `--out-peers -1` appropriate for unlimited outbound peers or does it not work the same way as inbound peers?

maybe it's being interpreted as `1` somehow?

try something else, like 96

yeah will try

i just fired up a new daemon without an incoming port, and it found 8 peers and started syncing at 200Mbit+/sec in less than a minute

syncing worked perfectly initially, and was very fast, it's only since it caught up to the network the first time that i've had this issue

i changed the -1 to 96, will observe

if that fails maybe trying the default, 8, is worth it too

8 should generally be enough anyway, right?

probably. i always have incoming, so i don't know for sure

but if there is some weird bug related to that setting, it maybe could go undiscovered for a while, since most people probably don't change the default

yeah, makes sense

Suppose you have outputs in two different wallets and, for whatever reason (maybe they are almost dust) want to construct a transaction that uses outputs across the wallets. Is there any way to import the output private key (i.e. x = Hs(aR) + b) and it's associated output into another wallet in order to do this?

jbg: try removing p2pstate.bin, you might have only attack peers in your list (which only tell you about peers in their list).

testerino

test

test failed

perfect :D

better test

betterer test

.xmr

can someone donate me crypto?

<rbrunner7> Lovejmwi1, I could send you testnet XMR if you want to try out wallets

is that not real crypto?

<rbrunner7> What is real, what is only fantasy? :) Anyway, testnet coins don't have any value

I have some stagenet XMR. They are double value of testnet XMR.

<rbrunner7> Psssst, TrasherDK, wanna try this scheme together with me: rbrunner7.github.io/consensus.html

rbrunner7 Yeah. I read that one a long time ago. Good one :)

<rbrunner7> Thanks!

Hi

is it bad form to expose "get_connections" JSON RPC calls to the public web?

Thats only available via an unrestriced RPC, correct?

yes

I mean I would say its bad form to expose any unrestricted RPC

Especially since it allows all kinds of things, including mining to someone else's addresses

Should only expose restricted RPC externally

using something like this in your command line: --public-node --rpc-bind-ip 0.0.0.0 --rpc-restricted-bind-port 18089 --confirm-external-bind

and then just port forward to the restricted port, not the unrestricted one

im guessing recreating something like this would be done within private networks and updating something that is external: monerohash.com/nodes-distribution.html

like they're just scraping an internal, unrestricted daemon and then storing results in a DB

Posted on reddit: monerooutreach.org/stories/monero-paper-wallet.html

Hi