00:11:20 it doesn't exist physically but somehow is property. makes sense that it's a law. 00:11:21 property can't be traded for goods and services? IOW, bartering is illegal in russia? 00:19:05 no idea. it's frowned on even in the US, because uncle sam wants to tax all transactions 03:48:01 "Putin has now signed a law saying that crypto is property, not money, and can't be used to pay for goods and services" this is so comical 05:34:44 https://www.crowdfundinsider.com/2020/07/164542-monero-xmr-zcash-zec-stellar-xlm-to-be-delisted-by-liquid-exchange-so-it-can-prepare-to-acquire-payment-services-license-in-singapore/ 13:05:25 <[discord] Yonatan#6948>: Question 13:05:33 <[discord] Yonatan#6948>: Does my node run when my laptop is sleeping? 13:08:36 if the node is on your laptop, then no 13:08:40 Or your laptop is lying about sleeping 13:21:15 <[discord] Yonatan#6948>: Oh ok 13:22:15 <[discord] Yonatan#6948>: Another question 13:22:23 <[discord] Yonatan#6948>: Can I monitor incoming traffic to my node? 13:22:34 <[discord] Yonatan#6948>: Because it’s exposed to the public internet 13:35:08 You’d have to setup some type of proxy, like a reverse proxy using NGINX to monitor/filter/rate limit 13:35:20 Obviously you get some logging in the daemon 13:35:30 But for more advanced logs you’ll need some sort of proxy. 13:44:33 How long has xmr.to made provisions for btc lightning payments? 13:49:24 I think the announcement was a few days ago 13:52:42 <[discord] Yonatan#6948>: Yep 13:52:53 <[discord] Yonatan#6948>: They don’t support a lot of channels 13:52:56 an 13:53:36 <[discord] Yonatan#6948>: Half of the lightning channels I have open don’t work with xmr.to 13:53:54 <[discord] Yonatan#6948>: I would love to see a lightning network for XMR in the future 13:58:34 Ok. The few that I would use often seem to work. 14:01:48 derpy_bridge_: definitely get in touch with them, together you can probably solve the reachability problems 14:02:29 i have a small service that accepts lightning payments and it's really useful when people contact me about things like that, usually it's easily solved and makes things better for everyone 14:02:53 oops, tagged the bridge. I meant Yonatan 14:05:16 <[discord] Yonatan#6948>: Already did 14:05:29 <[discord] Yonatan#6948>: They said they were planning on opening more channels soon 14:05:47 <[discord] Yonatan#6948>: Supporting* 14:07:57 What kind of services do you provide? 16:42:32 <[discord] Yonatan#6948>: I fucked up my key management for my encrypted partition 16:42:34 <[discord] Yonatan#6948>: How fucked am I 16:44:05 @yonatan : very 16:59:40 <[discord] Yonatan#6948>: Ahhhh 16:59:48 <[discord] Yonatan#6948>: Guess I’ll need to reinstall 16:59:53 <[discord] Yonatan#6948>: Fuck my life honestly 17:00:04 <[discord] Yonatan#6948>: That’s why you don’t don’t mess with your keys while you’re tired 17:31:23 @yonatan.... and then...you backup, and backup the backup 23:40:59 Hello all; I am looking for some tech support. Upon submitting a transaction from a watch-only wallet, if I enter get_tx_key [transaction] it displays a transaction key that is blatantly wrong (all 0 except for one). I saved the transaction key from the wallet that signed the transaction which certainly looks random, however upon attempting to type 23:41:00 it in for set_tx_key it states that it doesn't match the pubkey of the transaction; anyone have any ideas? 23:46:31 Did you do this in the hot wallet ? 23:47:05 No, in the watch-only wallet. It should also be able to save transaction keys, no? 23:47:41 What distinction are you making here ? 23:48:59 Upon signing the transaction in the wallet that had both private spend and viewkey, it generated a transaction hash which is the same as the transaction that was submitted to the network. Entering "get_tx_key" [txid] generates a hex string 23:49:56 The tx key is the *secret* tx key, so the hot wallet does not have it. I'll assume you meant hot wallet. 23:50:04 then, in the wallet that has only the private viewkey, I enter "set_tx_key [txid] [tx_key]" 23:50:54 I forgot you could do this. 23:51:21 So you take the secret key from the cold wallet, and set it manually in the hot wallet. And this errors out. Correct ? 23:52:22 Yes, it generated an error for me. This gets you the transaction key "r" which is just a randomly generated value of no connection to the private spendkey correct (based on cryptonote white paper)? 23:52:41 It was my understanding that I should have been able to do this? 23:53:02 It is random, yes. 23:53:47 The wallet that broadcast it claims it has a value that is blatantly not random, and distinct from what the wallet that signed it says