Hi everyone, I've just started my daemon and wallet-rpc on a debian machine on my home network, and I'm trying now to user nodejs to ask some informations about my wallet, but the response keep returning socket hang up, anyone can point my mistake?

Post the JSON you send in #monero.

I'm using monero-javascript, not sure how to get the JSON

kick update, I just fire the curl targeting wallet rpc from my application machine and from inside the server

both came with diferent results, I'm thinking that this issue is related to the port 38083 on the server side

Hi, I've encountered an issue with Monero GUI Wallet after a power failure where the wallet appears to have re-initialised. I've reported it as an isssue on GitHub, could someone look into Bug #7079 - monero-project/monero #7079

There are multiple psychological hooks to keep Monero community members in place. Here is one:

Notice that Scientologists don't stand on street corners saying "Would you like to talk about our Lord and Saviour, Xenu?"

Put yourself instead in the shoes of someone who spent $10,000 and 2-3 years of their life on their courses

And you get a bunch of bad sci-fi - you have two choices:

- either swallow a very bitter pill that you wasted a pile of money and a portion of your life

- or swallow the sci-fi, and from that point on, you will swallow _anything_ they tell you.

In the cult trade that's called "insider doctrine".

Would you like to talk about our Lord and Saviour of NASA, Howard Chu?

hi hi

If anyone is able to assist with my issue of Monero GUI Wallet having re-initialised after a power failure. I've move the bug to monero-gui - monero-project/monero-gui #3256

El-Aurian: Let's continue in #monero

dERUYNE ok

Anyone has an opinion on monero-project/monero #7072 (process N peers rather than drop) ?

It depends. Do any legit nodes break this limit?

Not that I know of.

If all v0.17 nodes don't send that many peers, then it's safe to enforce the limit

older versions don't matter obviously

If you launch a node with 256 out_peers and have 256 peers in your list, will it send all of them?

It's probably safer to just ignore excess peers

I think this is based on a misunderstanding. You don't send your current connection list.

But no.

ah, so what is sent there?

A random selection of your white list.

then it's safe to enforce the limit

FWIW, if we don't drop, it does not incentivize assholes to stop spamming. 140 kB handshake messages from the current asshole.

Also keepalives.

they'll just continue spamming with the maximum allowed number of peers, right?

For the record, my opinion is to drop such connections

Presumably. 15 kB messages, much better,

Hmm. I got an idea. Make it easy to plug to fail2ban.

very good idea actually

every time a connection is dropped (for whatever reason) it should be visible in the log with unique error message

at some log level

My fail2ban can't wait, hehe

on the other hand, this creates an easy way to block tor exit nodes, again...

people really need to use .onion nodes anyway

not clearnet nodes through tor

Lyza how do you use .onion nodes?

there's an option in the GUI to enable a SOCKS proxy

then you can just put onion nodes in the node field

is there a guide? I've never used SOCKS

Let me look. The dummy easy method would be to just download and run the tor browser then hit the tick box in the GUI, since the tor browser also starts a SOCKS proxy

this is more of a #monero convo though I think

There will be PoW on connect at some point.

IMO if the current protocol can be exploited by custom clients we should change it.

+1 selsta

(which will prevent mass banning of exit nodes, or at least make it costly)

adding a P2P_MAX_PEERS_IN_HANDSHAKE would make sense

and drop every connection that has > MAX

I'll do that.

Also, repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/192 - back to working more on monero after months mostly doing other stuff

nice

is the idea for PoW on connect to do some actual RandomX hashes for the receiving node a la RPC pay? or are you thinking like a separate system

Randomx is too heavy to verify sadly.

It will likely be Equix, or if not, keccak.

hmm, so something with asics for it?

that seem son the surface problematic

Equix does not have ASICs and if so it can be tuned.

Tor is looking into the same algorithm

oh okay I guess I thought that was a reference to equihash

It is not used for PoW so there is no incentive to ASIC it

gotcha. keccak is though right?

Most likely. It was designed to be silicon friendly.

It also very fast in software.

Guess blake2 would be faster even. Also ASICs probably.

Lyza: github.com/tevador/equix

ty for the link

.merge+ 7070 7071 7072 7073

Added

sech1: 7081

nice

#7082 only 2 more years? should have gone till 2023 exitscam

I've done two years every time before IIRC. It's arbitrary really.

Reason is, I've found a key from like 2000 or so someone's used, to which I no longer have the secret key :)

So I don't really want those keys to be kept alive forever.

I kinda figured it was arbitrary yeah. and 2023 just to align with the exttscam meme

It has an actual date, does it...

I don't know of an actual date, just "2023" according to fluffy

7054 is the only PR left that needs an approval before we can tag

7054 windows CI failed, is that just windows being windows?

the release branch does not have updated CI

7055 (master equivalent) passed

moneromooo in 7054, why do you call evict_host_from_white_peerlist() in the very end? it's inside "if(by_addr_it_wt == m_peers_white.get<by_addr>().end())" so the peer shouldn't be in the list already

To evict all the ones with different ports.

ah, and possibly IPV4 embedded in IPv6?

Yes.

7054 looks good at the first glance, I'll take a deeper look tomorrow

if it's not approved by then

max peers in handshake ban? xmrchain node is set to bajillions of peers

out_peers?

or what?

out-peers=1024

yea this is unrelated

word

Hi there. I want to get some info about the pow currently used in monero. Whats actually used? I've seen references to cryptonight / cryptonightr / randomx. Is this expected to switch soon?

I'm planning on implementing a miner for a new platform, and want to make sure I dont waste too much effort

mostly PoC / for fun

randomx, and we don't expect to switch soon.

this is the current PoW: github.com/tevador/RandomX

cool, many thanks