09:45:12 Guys how do I check if my monero node is discoverable? I set it up as a .onion because my isp doesn't allow for port forwarding. 09:45:32 I'm using monero gui btw 10:02:51 I think you can access your .onion node through browser and there will be some info about the node in json format, so you can verify it’s accessible 10:03:13 Sounds like “I use arch btw” xD 10:03:24 I tried connecting through localhost and it didn't work. the port 18089 is closed 10:04:46 is it possible to enable the port through the daemon startup flags? 10:06:35 It should be enabled, but if you want it to be discoverable by others I think you have to configure port forwarding or maybe get public static ip, idk 10:06:57 Are you able to sync your wallet using your node? 10:07:11 it's still syncing 10:08:53 but my point is that even if I could port forward the daemon doesn't have the port open 11:35:35 ok i figured it out I needed to add some daemon startup flags to turn on the restricted rpc mode and make it a public node and it works now 11:35:48 pxwm46culmrb2sxtbmwkhsczbj3veqeuaex2a5772uszyg2oujxiawad.onion 13:04:03 Verifying the first eight and last eight together should be pretty secure then. 13:06:23 Do you have any resources to back this up? 13:11:35 When I wanted to be sure, I check the first 4 or 5, then check the first 4 or 5 of sha256sum of the address plus a couple random chars appended. 13:13:06 While using a dedicated signing device like a Ledger? 13:14:53 It's interesting that I can't find a strong standard answer. In Bitcoin, we verify the first and last 6 characters. 13:54:23 No, normal software. 13:54:55 If you're comparing with Bitcoin, then you need to know that monero addresses are the concatenation (kinda) of two keys. 13:55:32 So if you're going to compare 1 and 6 for a monero address, it's kinda like comparing 6 at most, not 7. 13:56:21 Probably not quite right since the base58 encoding might avalanche from the start to the end, but nowhere like a cipher. 13:56:32 So if you want to do that, compare 1 and 7. 13:57:06 Best would be comparing 1 and 6 from the first key though. 13:58:02 Though to get the exact same security, you might have to turn the 6 into 5 or 7, depending on the "compression" each of the schemes achieve. I've no idea what Bitcoin uses to encode their addresses. 13:59:02 Also, the first char is not the first textually, since that's the netowrk byte, so will always be 4 for standard addresses, etc. You'd want the second (I think that's where the spend pubkey starts). 13:59:19 * moneromooo ambles away again 15:45:49 I did some more research and the first 16 seems to be the best if you aren't going to fully verify each character. 15:45:57 The likely reason for this is because limiting the number of characters that you read at a standards level will effectively reduce the number of unique addresses, as well as create a target for attackers to exploit 15:47:25 While it isn’t likely that any one address would have both the first 6 and last 6 matched, someone could run a program to generate and save a bunch of addresses into a database to use against people that are unlucky enough to have those matches. 15:49:23 Another smart idea could be to hash your address and check those numbers in addition to the other numbers 15:50:47 An actually funny idea I just had: you could also make an algorithm that would generate a unique “chain” of hashing algorithms and you could check that instead 15:50:48 That way an attacker can’t also select for matches of a well known hash algorithm 15:51:12 Probably overkill, but it should work 16:00:18 I'm looking for a ux friendly but secure way for your casual monero user that's spending from a hot wallet. 18:47:48 Hey guys, trying to set up a monero-cli wallet on a VPS, and the syncing is incredibly slow. It's a 16gb ram, 6vcpu, SSD vps and it's currently at 96% 18:47:55 But it's been syncing for over 12 hours 18:48:37 It syncs like 40 blocks per minute at the current rate 18:50:08 What did stand out to me though, is that when I launched monerod I got the message `The blockchain is on a rotating drive: this will be very slow, use an SSD if possible`. I assume it's because of virtualization that it can't properly detect the drive as an SSD 19:25:53 I love the name 19:26:24 also, it's normal to see a warning of rotating drive on VPS. That's because their hypervisor (likely QEMU) is passing a virtual drive 19:26:36 so on paper it looks like an HDD but it's actually SSD speed 19:27:39 However 40 blocks per minute is slow so I suppose it's actually SSD, but instead of files they are using something like LVM thinpool, which is slow at allocating new storage for your VPS 19:28:26 Anyway, if you want to check disk speed use Yet-Another-Bench-Script on github 19:28:32 this will give you the disk/network speed 19:29:02 However 40 blocks per minute is slow so I suppose it's actually SSD, but instead of files they are using something like LVM thinpool, which is slow at allocating new blocks of storage for your VPS to use 19:29:26 Ah I understand, I'm currently testing out another datacenter that provides an NVMe ssd instead, and it's already at 42%. Not really quantitative since the blocks get fatter the further you go but it does seem _better_ 19:29:29 May I also ask what OS you are running ? 19:29:36 I'll give that a try thank you 19:29:46 Ubuntu 22 21:16:23 some days irc is so dead 21:24:17 matrix-mossad too 21:24:34 at least this channel 21:46:05 We relaunched. monero.win 22:56:52 This site and idea looks awesome 23:13:07 monero.win was up for sale on reddit 2 years ago, which "we" have relaunched it 🤷 23:15:16 https://www.reddit.com/r/Monero/comments/yjdfd4/monerowin_is_closed/ ~ https://web.archive.org/web/20221101164419/https://www.reddit.com/r/Monero/comments/yjdfd4/monerowin_is_closed/ 23:16:11 mochi101 23:21:33 https://www.reddit.com/r/Monero/comments/14wgt2w/new_monero_blockchain_betting_game/ 23:21:52 so the original "we" of monero dot win are @ playmonero.com 23:25:37 (imagine selling your auto garage company and then opening a competitor next door to the new owners 😆)