06:48:52 .merges 06:48:52 -xmr-pr- 7910 7977 08:01:05 release-v0.17 branch needs a fix https://github.com/monero-project/monero/issues/8092 08:02:24 cmake is such a PITA but at least this puzzle was documented 13:46:12 Hello everyone, i know you are all successful coders and that you live your best life being cypherpunks, can someone take the time and explain to me IRL slowly how to start the the daemon and the monero-wallet-rpc, I am really inexperienced with the command line but my drive is very strong and i am about to waste 1 month to understand what someone can explain to me in 1 hour. Please reach out to me. 13:46:20 I'm on windows 13:49:05 It's better to ask general questions in #monero, this is dev channel. Check out https://monerodocs.org/interacting/monerod-reference/ for how to run monerod 13:49:35 Yes I have gone throw that like 10 times 14:13:06 .merge+ 8094 14:13:06 Added 14:15:10 I did not see anything in #monero. Ask there and I will help. 14:16:54 matrix still isn't bridged in #monero almost 1 year later 14:17:43 Oh I see. 14:19:00 The Matrix #monero:monero.social and IRC #monero are separate rooms at this point. 14:19:39 Well... "monerod" alone will work. Add --testnet if you want testnet instead. --data-dir to put your chain not in $HOME. --log-level [123] to control amount of logs. 14:21:08 monero-wallet-rpc takes --testnet if monerod has it, --rpc-bind-port (your choice, you'll send JSON/RPC to that port), --disable-rpc-login for testing (or you need to login when you're ready for production), --wallet-file to select a wallet. 14:22:33 And if you want your daemons to be accessible from other machines, --rpc-bind-ip LOCALLANIP (or 0.0.0.0). 14:23:20 If monerod RPC is accessible from the public internet, you'll want --restricted-rpc. If monero-wallet-rpc is accessible from the public internet, you'll want --rpc-ssl enabled and login. 14:50:36 "I did not see anything in #..." <- Ok I will 18:41:05 .merges 18:41:05 -xmr-pr- 8094 20:36:40 moneromooo: https://github.com/monero-project/monero/issues/8062 20:36:47 does it make sense to change the log level of this message? 20:37:23 Sure. 20:37:25 seems like someone running intentionally broken nodes for a while now 20:37:40 It doesn't hurt anything AFAIK. 20:37:58 I'm not sure which one of the fields will be used, but it's innocuous. 20:38:58 yes, it's just log spam 20:39:11 not sure if it's possible to change the log level of "CHECK_AND_ASSERT_THROW_MES" 20:39:24 There's a L1 IIRC.