what the best way for a non dev IT person to contribute? basically just run a full node?

if i wanted to pursue a dev skill path, where should I start if all I know is server hardware, windows and linux?

#monero-community-dev:monero.social

This channel is for core development

Hacking, c++ etc

#monero-dev:monero.social is for core dev, hacking etc.

#monero-community-dev:monero.social is for lower level stuff

ok sorry

> <@jeffro256:monero.social> > Another question, with ristretto points. Why are prime order groups harder to implement algorithms for?

>

> They both have different challenges. When the number of possible elliptic curve points is not prime (e.g. Curve25519), you have to constantly worry about sanitizing curve points that are not in the correct subgroup, hence the existence of Ristretto. When you do not use prime subgroups (e.g. secp256k1 in BTC) you have to worry more about Pohlig–Hellman algorithm attacks

But why order h*l instead of l/q attractive?

* But why is order h*l

Well the order of the subgroup we use is actually l, not h*l. h*l is the total number of points on E(Fq). Also, we cannot use q as the order since q is the size of the underlying integer field.

AKA the base generator for curve25519 resides in a subgroup with prime order l

jeffro256[m]: Ive read some time ago that ristretto expands the subgroup to use h*l

but I don't know the correctness of that

I don't think so... If anything, some libraries even use scalars mod l instead of X, Y over mod q

They don't allow users to convert direct from an X value to a point (besides the base point), they have to use scalarmult against G

I would ask dangerousfreedom... They know better

> They don't allow users to convert direct from an X value to a point

That doesn't apply when using DH in X25519

<jeffro256[m]> "I don't think so... If anything,..." <- yea. I think sodium does

(they have wrote the zig implementation of ed25519 in its standard library, which I explored some time ago)

Hello. I have got a question about Monero Daemon RPC.... (full message at <libera.ems.host/_matrix/media/v3/do…cd924940f3003714cac3fc8c324ef0e28f8>)

yes, next_seed_hash is just for reference

.merges

if someone runs a stagenet or testnet node please update to release-v0.18, would be great if we had some testers before we put out the release

(or also mainnet)

the dandelion++ code had changes, there's now a ringct cache and the monero side randomx code had a rewrite, so testing mining and sending transactions would be great

all of the recent testnet spam during p2pool testing was broadcast from 2 nodes / wallet-rpc running release (both mainnet nodes currently have ~2MB/s traffic also and stable). The more testers the better!

my nodes have also been running release-v0.18 and so far everything good

<ghostway[m]> "but I don't know the correctness..." <- It is not expanding to use h*l points. It is remapping to l to avoid the overhead of multiplying by the cofactor, cleaning the scalar or other things.

selsta: someone on Reddit has a problem with this monero-project/monero #7708

monerobull[m]: they have to add disable_noise

`--proxy tor,127.0.0.1:9050,disable_noise`

I'll tell them

What's the cause here (for dummies)?

And how does that flag fix it

Ah i see

White-noise feature

the daemon constantly sends noise and in-between the noise it would send the transaction, in this case the transaction is simply to large and the node would switch to a different node before it's fully transmitted

yep

too*

selsta: Woah, something about monero i didn't know

Thanks!

.merge+ 8739

Added