Does anyone know what the stagenet network byte is for XMR addresses?

I know that the network byte "identifies the network and address type; 18 - main chain; 53 - test chain

", but what is stagenet's?

Adreik: 24. but these are for primary addresses only. integrated and subaddresses have different prefixes.

Is that 24 as a decimal integer, or 0x24?

Adreik, github.com/monero-project/monero/bl…2/src/cryptonote_config.h#L251-L253

Thanks

:)

was literally just about to paste the same thing, lol

those are non-hex values btw

we are looking for somebody knowledgable with monero javascript (wasm wallet) in combination with react, if you are happy to help join us right now under meet.jit.si/MoneroStammtisch

strangest thing just happened: i just executed this command ```./monero-wallet-rpc --daemon-address localhost:38081 --daemon-login superuser:abctesting123 --stagenet --rpc-bind-port 38083 --rpc-login rpc_user:abc123 --rpc-access-control-origins localhost:9100 --wallet-dir ./```

and got a FLOOD of transactions. i m talking THOUSANDS, recieved and sent. this is super weird to me since i was not the one that made them, i can see amount, tx id. most tx are from this year, but well before i made the stagenet wallet... wtf?

I can confirm, this is super strange. None of those transactions are related to alexanarcho We should not be able to see this data!

and then there are these

we figured it out, i started the wallet of woodster github.com/woodser/monerowebwallet.com/blob/master/src/index.js :D

Hi is there anybody from monero-javascript I can reach out to? I have some questions regarding the WASM implementation

wasm sounds like woodser

yes axactly

* yes exactly, is he active on matrix?

Hello everyone

I have a technical question in regards of dandelion++. Is this the right place to ask about this topic?

or #monero-dev

here's prob better

Okay, thanks. Are, epochs, periods of time?

My question comes from this article: monerooutreach.org/stories/dandelion.html

This specific paragraph: Dandelion++, like Dandelion, has a stem and fluff phase. In the new stem phase, to implement dynamic connectivity, it proceeds in discreet intervals, called epochs.

Yes.

Thank you moneromooo

this episode is MCF:fluffypony got a haircut!

:-P

he's looking fairly sexy today

Well, more sexy than usual.

;)

ah, haircuts. man that brings me back

Mochi103: is it the glasses?

because they're fake, non-corrective lenses :-P

:D

fluffypony: u hipster

fluffypony are you real?

well I don't have a beard

so there's that

evolbit: I like to think so

fluffypony: that's okay, you can still qualify as a hipster, just learn nodejs and mongodb

funny pony i see

ndorf: lol

fluffypony I have the beard but no knowledge about nodejs / mongodb

no mongoDB.

just no.

hyc doesn't have a beard, but he does have a fiddle

oh, right now I have a beard.

haven't shaved in weeks

let them use it (mongodb), It's funny to find some on the internet :p

lol

you realize you're talking to a community that prizes privacy, right?

does the fiddle have a beard

Reminds of Airplane. Or Airplane 2 ? The Iran air plane...

hmm, don't remember airplane 2

hey, mongodb is great at something....it's definitely the best database out there if you want to be horribly insecure as a default!

i heard it was also good if you wanted to have unpredictably inconsistent data

built in chaos engineering - next level stuff

hyc: ofc I know, I was just joking. Jokes apart, Developers and Sysadmins should be aware of mongodb, it's really easy to mess up with the configs

haha, yup

not sure i agree that devs and admins need to be aware of it.

just malware scanner tools should be sufficient.

it's too late when the problem is detected by a malware scanner, unless you're saying that they should flag mongodb :p

flag it? they should automatically remove it

no human intervention necessary :P

^^ lol

lol

mongodb is web scale

i assumed it was a jab at the hipster terms like "Web scale"

"You turn it on and it scales right up"

i'm not sure what "web scale" means but the first thing it conjures is something that takes a minute of CPU time and 3GB of RAM to display a half KB of text and a small image

(image not guaranteed)

clickhouse.tech this one works better when you have several TBs of data

rickrolld

Hello everyone. Me again asking about RPC requests. I'm using a RPC payment node and I would like to know, what is the mining private key, from address, that I need to use to make requests? And in the request, where should the key be added? I know what is the private key, I know how to get it from the CLI, is that the key I need?

I'm getting the message: "Client signature does not verify for get_info"

It's a normal Schnorr signature. The RPC is signed. The secret key is in the rpc_mining_status (or similar name) command output.

I can't recall exactly what is signed in the RPC data, lemme check now...

Ah, the timestamp. Guess there should be a salt.

See src/rpc/rpc_payment_signature.cpp

Thanks moneromooo, going right now to check it out. I'm looking a command similar to rpc_mining_status right?

Yes.

Okay, moneromooo I've got, RPC client ID, and RPC client secret key

Which one should I use to make the request, the ID or secret key?

And two more questions, when making the request, should the wallet be running? Where should the signature go when making the request ("params")?

Depends what you mean by "use".

To sign, a secret key. To tell what account to use, the public key.

To make a call. Let me show you what I'm using to make the call.

In a "client" field.

"should the wallet be running?" is confusing.

Since it's sending a request, it presumably is running. So I'm guessing you assume different things.

Should the wallet be open, mining? The wallet has credits. If not I could close and just send the rpc request.

curl 127.0.0.1:18081/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'

This is the command I'm currently using.

This is what I get

Whatever is using the RPC has to be running. If it is not the wallet, then the wallet does not have to be running. If it is the wallet, it does.

The RPC node is running. When I make requests from the terminal that's the message I get back. I do have a RPC wallet too, that has been mining for credits. But when I send requests to the blockchain it says: Client signature does not verify for get_info

The requests are sent trough a terminal

I was told it's because I'm not signing the request. So, my question is, how should I send the request using the secret key from the wallet(rpc id or secret key) to the rpc deamon?

**daemon

You sign the timestamp with the secret key matching the public key, put it in the client field. See the file I linked earlier.

If you're getting errors, bump log level in the daemon, it might tell you what is wrong.

The signature contains more that jsut the Schnorr signature btw. See that file, first function, second to last line.

It's a small file.

Oh, okay okay I think I understand. I'll have to put the signature in the file. The file has two functions, make and verify. I believe is in the verify function.

Yes it's a small file. The bool functions receive arguments (const, crypto: :, uint64_t), what I'm not sure is how to add the keys to the file and not mess everything up. I thought I could send the keys through terminal arguments.

I'll stop for today. Don't want to blow up. Thank you moneromooo :)

See you tomorrow

You don't add keys to a file. You sign the timestamp with the secret key. Add timestamp and pubkey like in that code. Put that (as hexadecimal) in the client field.

Well, timestamp, technically increasing nonce, but timestamp is a useful instance of this.

Oh...o_o, okay, I'll give it a try. By the way I was able to make calls using Python :), it took me almost 3 hours to figure it out :P

There is python code htat sends those client signatures in tests/functinal_tests.

Nice