.merges

Maybe, if it's already nearly time for 0.16.0.3, #6614 can be added for merging, otherwise we will fall back from "help" command to "help_advanced" in CLI wallet and daemon as far as I can see.

(I was very late to correct a conflict there, sorry about that.)

rbrunner: we don’t branch from master

Ah, alright, wasn't aware. So branching from master will happen for the CLSAG release?

yes

Ok, thanks. So we have a lot of merging ahead of us if we try to make the "beta date" of August 17 :)

.merges

Hi. Is there any news regarding #5172?

I know nothing about CORS. vtnerd would be the one with the best opinions I think.

Apparently monerod needs to return "Access-Control-Allow-Origin: *" as header. (developer.mozilla.org/en-US/docs/We…Headers/Access-Control-Allow-Origin)

better idea: nginx + reverse proxy to monero RPC, and in nginx you can add/remove headers as you please

yeah that would be my recommendation too

and avoid exposing monerod?

it doesn't need to return the wildcard all ("*") afaik

you can specify the specific domains with --rpc-access-control-origin

the wildcard all comes with security implications, but is likely easier when debugging and setting up the RPC

although, woodser asked for it, so there is the case with "open" RPC servers and some kind of HTML wallet

the wildcard would allow web wallets to select their daemon. otherwise the domain must host the daemon or nginx + reverse proxy is necessary

woodser: We're looking specifically at mobile clients (using your monero-javascript/WASM). We do have a specific domain, but there seems to be some issue connecting due to that missing header.

Maybe the issue is somewhere else - Should RPC work via webview even without that header altogether?

luigi1111w: you can tag v0.16.0.3 whenever you have time, thanks