00:02:33 <selsta> simplewallet depends on wallet2
00:02:46 <selsta> so you can't just take simplewallet out
00:08:18 <RustyIcicle> i notice others have used "libwalletqt" from the GUI wallet, but that obviously depends on Qt
00:09:42 <ga_1700[m]> not much of a cpp talent, but I'd like to help with testing if needed, I've the read 
00:09:43 <ga_1700[m]> https://github.com/monero-project/monero/blob/master/docs/CONTRIBUTING.md
00:09:43 <ga_1700[m]> is there anything on the "to do" list I could assist with ? 
00:10:46 <RustyIcicle> I can imagine that starting to reply to the enormous pile of open, unanswered issues would be greatly appreciated :)
00:21:55 <selsta> Rucknium[m]: you can use wallet_api
00:22:13 <selsta> src/wallet/api/ ...
00:22:34 <selsta> ga_1700[m]: in general open PRs always benefit from testing
00:22:55 <selsta> ga_1700[m]: https://github.com/monero-project/monero/pull/8046 for example should speedup tx generation, that is something you could test
00:23:32 <selsta> Rucknium[m]: sorry, didn't mean to ping you, the other person has left
00:27:41 <ga_1700[m]> <selsta> "ga_1700: in general open PRs..." <- I think I saw a "how to" about testing, looking for it now. 
00:29:42 <selsta> vtnerd: mooo addresses your comments, can you recheck? https://github.com/monero-project/monero/pull/7170
00:34:34 <ga_1700[m]> alright, each PR seems to have github actions running jobs and some tests, where does the human element for testing come in, or does it come into play at all ?
00:34:50 <ga_1700[m]> * actions running CI jobs and
00:35:03 <ga_1700[m]> s/alright, each PR seems to have github actions running jobs and some tests, where does the human element for testing come in, or does it come into play at all ?/alright, each PR seems to have github actions running CI jobs and some tests, where does the human element for testing come into the workflow, or does it come into play at all ?/
00:36:48 <selsta> it depends on the changes
00:38:50 <ga_1700[m]> It seems like labels are not being used much, so there wouldn't be much of a way for a nube to know which PR requires attended testing ?
00:40:23 <selsta> yes, labels would help
00:52:59 <ga_1700[m]> alright, seems like the build process is fairly straight forward and you have things documented, however without labels and/or internal knowledge of "which PR requires which action", not much can be done, I'm afraid (also, github actions take care of quite a bit, as it should). 
00:53:10 <ga_1700[m]> https://github.com/monero-project/monero#compiling-monero-from-source
00:54:16 <ga_1700[m]> * I'm afraid. (also,
00:56:38 <vtnerd> selsta: ok
03:52:15 <gingeropolous> mdb readers crashed my node
03:53:19 <selsta> is it the node that you use for xmrchain?
03:55:25 <gingeropolous> no, the one im running with p2pool daemon
03:55:40 <gingeropolous> and i already had the mdb_stat thing set to run every 3 mins in cron
03:56:33 <gingeropolous> weird
03:58:07 <gingeropolous> i got monerod spiking to 1600% cpu. ive never seen it use that many threds
03:58:41 <gingeropolous> maybe i just don't pay attention that often
03:59:02 <selsta> which node now? the same with the reader issue?
03:59:11 <gingeropolous> yeah
03:59:38 <gingeropolous> its running the modded daemon for p2pool. 
03:59:47 <selsta> 1600% cpu isn't normal
04:00:13 <selsta> doesn't p2pool use zmq and not the blockchain directly?
04:01:49 <gingeropolous> yeah. its settled down to the normal 130% zone
04:02:40 <gingeropolous> i was getting tons of these when it was blastin: 2021-11-15 04:00:37.215	[P2P1]	INFO	perf.ringct	src/common/perf_timer.cpp:156	PERF     4666          verRctCLSAGSimple
07:35:28 <spirobel[m]> https://github.com/monero-ecosystem/monero-javascript/blob/master/docs/developer_guide/creating_wallets.md can someone explain what the difference between monerojs.createWalletFull and monerojs.createWalletKeys is? what is a keys only wallet? How do I go about opening a wallet from a only a viewkey? is it related to "keys only wallet" or does it have nothing to do with it and i could use both functions?
07:36:02 <selsta> woodser[m]: ^
12:41:17 <woodser[m]> the keys-only wallet only does basic key management, like restoring from seed and getting keys and addresses, whereas the full wallet can connect to a node, scan for transactions, and maintain wallet state. you'd want to create a full wallet in order to scan a view-only wallet, like this from this example: https://github.com/monero-ecosystem/monero-javascript/blob/master/docs/developer_guide/view_only_offline.md
12:56:52 <spirobel[m]> <woodser[m]> "the keys-only wallet only does..." <- thanks a lot. I was going through the javascript files and saw that full implemented functionality on top of keys. But I wasnt really sure what the intended usecase for both of these respective APIs was. Thanks for clearing that up. Maybe I can make a short video on how to combine this with express.js and make something useful. 😀
12:57:56 <woodser[m]> sure. the motivation was to offer a smaller file for basic key management, 1.18 mbs vs 5.24 mbs for the full wallet
12:59:21 <spirobel[m]> woodser[m]: can you name a usecase where you would use keys over full? just so I would be able to mention something and explain the tradeoff.
13:01:40 <woodser[m]> like for a mnemonic generator, address validator, or deriving deposit addresses from a view-only wallet
13:05:49 <spirobel[m]> woodser[m]: just to be sure: I want to ask the end users for proofing their transactions and then verify these proofs in the express.js backend. I recon interacting with the wallet is thread safe, right? so I can startup the wallet together with the server in app.js and make it available as a global variable. And then access it from the requests. There wouldnt be any interference between the different requests, right? similar like
13:05:49 <spirobel[m]> sending multiple calls over RPC and waiting for their responses.
13:06:41 <woodser[m]> > I recon interacting with the wallet is thread safe, right?
13:06:41 <woodser[m]> yes, it should be
13:13:47 <spirobel[m]> > <@woodser:haveno.network> > I recon interacting with the wallet is thread safe, right?
13:13:47 <spirobel[m]> > 
13:13:47 <spirobel[m]> > yes, it should be
13:13:47 <spirobel[m]> amazing! thank you so much for your work! I cant wait to play around with this and work on a solution that doesnt require the separate deployment of a walletrpc 
13:14:45 <woodser[m]> great, hope you have success, please keep me posted :)
14:17:14 <jberman[m]> View tags PR :) https://github.com/monero-project/monero/pull/8061
14:21:03 <john_r366> view tags are super exciting - thanks jberman!
14:55:57 <Rucknium[m]> <john_r366> "view tags are super exciting..." <- Yes! But what's not super-exiting is that the IRC-->Matrix bridge is still sleepy.
14:56:40 <Rucknium[m]> exciting*
15:33:05 <rbrunner> While working on `wallet2.cpp`I stumbled over the following comment:
15:33:07 <rbrunner> https://github.com/monero-project/monero/blob/6d94953be259c6bf4a1407ec552a570a66b6179d/src/wallet/wallet2.cpp#L3032
15:33:25 <rbrunner> I guess the time of that "TODO" has come.
15:33:56 <rbrunner> But what makes me suspicious: That will bring the timeout until tx failure down from 500 seconds to 60 seconds. Is that right?
15:36:27 <rbrunner> git tells me that selsta wrote that about 1 year ago. Hmmm, maybe still not yet time then? What is the "v15" hardfork, again?
15:38:52 <selsta> see https://github.com/monero-project/monero/pull/7058
15:41:48 <selsta> 500 seconds was the current max timeout due to people running old code
15:43:02 <rbrunner> I see, thanks
15:43:03 <selsta> "That will bring the timeout until tx failure down from 500 seconds to 60 seconds. Is that right?" <-- correct, the extra seconds currently are due to a bug in https://github.com/monero-project/monero/pull/7021
15:43:18 <selsta> I don't remember where the second 120s come from but there was a reason for it
15:43:24 <selsta> should have documented it better :)
15:46:48 <rbrunner> Ah, now I understand. First somebody thought we could already now use the new lower value, and you found out, no, not yet, and made that PR.
18:16:32 <sgp_> I was taking a closer look at Monero's URI scheme differs from Bitcoin's BIP21, and there are some differences. Is there a good reason for this?
18:16:50 <sgp_> for example, Monero uses `tx_amount` whereas Bitcoin uses `amount`
18:17:29 <sgp_> looks like Monero uses `recipient_name` and Bitcoin uses `label`
18:17:51 <sgp_> Monero uses `tx_description` and Bitcoin uses `message`
18:18:30 <sgp_> Maybe not all these fields are completely 1:1
18:49:15 <sgp_> I opened 8063 and 8064 for various URI things
20:36:48 <hqm42> 2
21:38:45 <bevanoff[m]> Does anybody here know what the data member named rpc in the RPCTracker class from src/rpc/core_rpc_server.cpp is for?
21:42:33 <bevanoff[m]> Or how the paying_for parameter to rpc_access_pay works?
22:03:19 <vtnerd> the `rpc` member tracks the name of the function being tracked for performance
22:06:04 <bevanoff[m]> Thank you very much
22:11:20 <vtnerd> I think the `paying_for` parameter is just a used as a notice that shows in the log
22:11:37 <vtnerd> but I've not interacted with that particular feature of the daemon much