Am I missing something or does Monero not set its own RandomX configuration? Notably considering the RANDOMX_ARGON_SALT which is intended to be domain separated

Hello.

I needed some help with the monero testnet.

And please refer me to some code or docs which outline the steps to serialize and sign a transaction.

Thank you!

I have 2 XMR i got from the faucect;  I just need a public url where I can post my transaction

usamat-at-opolo xmrchain.net/rawtx

sech1 thanks. This will help me with the final step of submitting my tx.

any javascript sdk that can help me with serializing the tx as well?

sech1 please help me with this as well :)

how can i find utxo of an address uisng xmrchain.net

Why are you here? For the tech? Then you should be off at Zcash instead of trying to con newbies into a coin that doesn't work. For the money? If you put your money in BTC or ETH you would have been better off. For the magical crypto friends? Monero leadership laughs from loosers like that. Find yourself more healthy realationships that don't laugh at you when they steal your money.

selsta what was the command/log setting to see detailed sync stats like time taken etc?

I’ll write it down this time I promise 😅

set_log +sync-info:INFO should do it I think

To whoever's running a public RPC node in order to remove the incentive for people to stay safe: monero-project/monero #7324

So it'd be nice if you'd add tor and/or i2p so your node is still seen by default.

Since we can't really remove this since even though it's probably a cesspit of spies, some people really need it :/

Once we have enough tor/i2p public rpc nodes, I might just remove the include-unsafe altogether.

<moneromooo "set_log +sync-info:INFO should d"> Thanks, that did it!

<moneromooo "To whoever's running a public RP"> Can you expand on what this does? I run public RPC nodes and want to better understand the coming changes.

The patch ? It does not show public RPC nodes that aren't tor or i2p by default.

There's no tor/i2p public RPC node atm, so public_nodes returns empty.

And I don't really want to contribute to the public node use train,

Basically it means your node should be accessible via foofoofoo.onion:port rather than a.b.c.d:port.

Or i2p equivalent.

If that's the desired route we ne3d to make absolutely sure that the way users can implement Tor/i2p RPC is seamless and simple.

And what are the effects of this on Simple Mode in the GUI?

Probably slower and more likely to break since fewer nodes.

It's not daemon side though, so it'll only happen if the GUI does the same.

The other issue is that most users needing a public node are not going to be familiar with how to use anonymity networks and we don't bundle Tor.

I don't really care. Maybe the GUI can stay like this then and get spied on. As long as the CLI doesn't.

Ah this only affects wallet-cli

Nevermind then, that's probably a good fit!

Misunderstood

With the patch, yes. I'd expect other wallets to do the same though, unless they like being spied on.

im kinda confused. can the wallet connect to the daemon via tor/i2p? Or does the wallet still connect to the daemon via clearnet, and then the daemon pushes the tx over tor/i2p, and the assumption is that someone running a tor/i2p node isn't spying?

It can via tor. Never tried i2p, but I see no reason why it would not be the same.

but i assume this requires the user to be running tor/i2p alongside the monero GUI or CLI

Yes.

poor noobs

gah. how does bisq bake in tor and bitcoin so seamlessly...