03:34:01 selsta: hey are you in the monero dev team by any chance? 03:52:13 Yes 03:53:07 Selsta is team capn. 03:53:07 im the waterboy, can i help? 03:53:30 seems they already left 04:04:46 Hello, is there anything that I can contribute with Java? 04:19:52 it's not directly for monero-project, but there's an open issue in haveno to fix a scrollbar for 0.25 XMR: https://github.com/haveno-dex/haveno/issues/677. that project's built on monero-java in case there's anything else you see 04:23:08 I see, will definitely check it out. Thanks 04:31:39 if anyone can help, this would be really helpful to verify a peer's unsigned tx fee without creating a new tx unnecessarily: https://github.com/monero-project/monero/issues/8710 15:02:28 Hi. 15:02:28 Is it possible to get transaction fee rate via wallet/node rpc? 15:04:19 https://www.getmonero.org/resources/developer-guides/daemon-rpc.html#get_fee_estimate 15:04:41 you can also create a transaction with do not rely set and get the exact fee 15:04:45 relay 15:05:30 omg,  so blind)) thank you)) 15:06:27 I want to find a way to get fee before transaction processing. 15:06:27 So using get_fee_estimate I will get only fee per byte. 15:06:28 But how to get size of common transaction? 15:07:18 Just look at a block explorer 15:08:56 Depends on what you are doing. Can your system work with `monero-wallet-rpc`? https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#estimate_tx_size_and_weight 15:09:15 yes 15:09:42 Then use that ^ RPC call. 15:09:51 Thank you so much! 15:10:49 What is ring_size is preferred? 15:11:24 "Unless dealing with pre rct outputs, this field is ignored on mainnet" 15:11:57 Ring size is set by consensus rules. You have no choice. Now it is 16. 19:34:32 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/xjmNEVELJbRkobIHRyqKyvBM 19:34:33 Hi, guys im encountering some issue with the node. It was working for a while, and i was making rpc requests to monero-wallet-rpc server, and everything was fine. But suddenly, all the requests started to fail with timeout. I went to see some logs of the monerod service and there was an error 19:35:04 Now i cant even stop the process :D 19:35:25 I'm running on testnet, so, I wonder is it common problem? 19:35:50 I'm running on testnet, so, I wonder is this problem could persist on mainnet though? 19:37:18 only `kill` shuted it down :D 19:39:20 Looks like you set your rpc port to restricted 19:39:52 Or double binded the p2p port and rpc port.. something like that. 19:39:52 config issue 19:47:02 hmm, need to double check, thx 19:47:21 but, now i restarted it and it works 19:48:05 if it would be a config issue, it would throw an error immidiately, isnt it? 19:53:53 It might be related to Tor configuration, I'm like double listening my p2p server on 28080 and 18083(for tor connections) ports 19:53:53 It might be related to Tor configuration, I'm like double listening my p2p server on 28080 and 18083(for tor connections) ports? 19:57:45 Hm.. is it 28082 zmq conflict with rpc 28082? 19:57:45 without knowing your configs / flags, thats my guess 19:58:34 Ah, yeah I had some zmq options set, let me a sec 19:58:43 (are you able to start the wallet after the node? Or are they conflicting with one another) 19:59:38 I do, they aren't conflicting 20:01:04 just now, when i restarted the node, the wallet rpc stopped on its own behavior, i restrted the wallet rpc as well. Everything works now 20:01:29 If it happens again --log-level 1 20:02:34 And ❤️ a paste website. I dont know if its element or my eyes, but i can barely read the screenshot 20:05:14 ok, sure. By the way the no-zmq=true is set 20:06:27 yeah.. its not zmq. Errors say p2p, so something with 18080. 20:06:27 maybe just a hiccup lol. We'll see if it happens again 20:13:13 Yeah, from my perspective it happens after continious of sending requests to wallet rpc, such as get accounts, transafers and adding lesteners. 20:21:28 Andrey: Is wallet-rpc and monerod on the same machine? 21:35:37 yes