> <@onionltd:matrix.org> I didn't mean to generate the documentation automatically as in take variable names and stuff them inside a table after a function name. No. In fact I think the current documentation is good. What I'm challenging is the way this documentation is being maintained because the current way requires... (full message at libera.ems.host/_matrix/media/r0/do…8ccaa07f9025b78d667056a1baf9a633b9d)

I've set up my wallet and the request below returns me correct result... (full message at libera.ems.host/_matrix/media/r0/do…c28058e3543400c9ae7b4cf58a355d704df)

* the request in the terminal below returns, * code below in the node.js env, it

willyijinin[m]: openwallet RPC is not valid if wallet-rpc wasn't started with --wallet-dir option

wallet-rpc runs in two separate modes: you tell it a specific wallet-file on cmdline, and it only operates on that wallet file

or you tell it a wallet-dir where many wallet files can reside. then you can use openwallet to open a specific wallet file in that dir.

but if you start it with wallet-file specified, then that single wallet is opened and thus the openwallet rpc is meaningless. it's already open.

hyc: got it thank you

hyc: I also figured this out by trial and error. Maybe it would be good if it was added to the docs in this clear cut way. Would save newcomers time <3

In other chains that employs the ed25519 curve, the private key is a 128-character string while the public key is the second half/64-character of the private key. For Monero which half is the private spend key which half is the private view key?

s/employs/employ/

spend is first, view is second.