07:23:46 <xmrmatterbridge> <rbrunner7> Is that awful fake Android MyMonero app visible for you as well, again, for the sixth time already now? https://play.google.com/store/apps/details?id=com.mymonero.wallet
07:25:40 <xmrmatterbridge> <rbrunner7> (Google recognizes me as being in Switzerland; maybe it's not visible everywhere, that's why I ask.)
09:30:24 <endor00[m]> Can't someone just create a stub MyMonero app and publish it, so that the name cannot be taken anymore by the scammers?
09:30:58 <endor00[m]> Or maybe just a basic app that shows the official website through a webview or something
09:50:44 <fluffypony> endor00[m]: yeah we're working on that
09:52:29 <endor00[m]> Cool!
10:16:59 <xmrmatterbridge> <rbrunner7> Note that unfortunately it seems apps can have the exact same title string, which is most visible; only the package name which is much less visible must be unique. Worst case a stub MyMonero app will push the scammers down to 50% or so, but not eliminate them ...
12:55:35 <Zaraki>  I am using MyMonero wallet. Do I need to specify a "payment ID" if I want to send xmr to my account on binance ?
12:55:47 <dEBRUYNE> No
12:55:50 <Zaraki> I read somewhere that a payment ID needs to be specified if I want to send to Binance. But I couldn't find this payment ID anywhere on Binance
12:55:52 <dEBRUYNE> Just use the address provided by Binance
12:56:06 <Zaraki> What about this? https://www.reddit.com/r/Monero/comments/7n83qt/binance_x_no_payment_id_xmr_lost_forever_no_heres/
12:56:52 <dEBRUYNE> Payment IDs (the ones Binance used) were phased out a year ago or so
12:57:34 <Zaraki> Alright, thanks, I will use the just the address provided by Binance
12:58:00 <dEBRUYNE> Should work
12:58:01 <dEBRUYNE> np
12:59:12 <Zaraki> oops it seems that I have an old version of MyMonero wallet. I will update it first
17:19:21 <jonathancross> <xmrmatterbridge "<rbrunner7> Is that awful fake A"> I reported it.
17:56:19 <mawk> why is blockchain syncing slower the closer it gets to 100%?
17:56:26 <mawk> it's at 95% for hours
17:57:52 <selsta> daemon includes checkpoints, so up to the latest checkpoint it syncs faster
17:58:43 <mawk> ah I see
17:58:52 <mawk> I should've used a ssd maybe
17:59:00 <selsta> yes that makes a large difference
17:59:11 <selsta> download v0.17.1.3 which should be out today / tomorrow and it will sync faster again up until ~99%, as it includes new checkpoints
17:59:24 <mawk> ah lol, I should've waited I guess
17:59:55 <mawk> but it's a remote server, ssd is expensive on that kind of stuff
18:09:46 <mawk> I guess I can interrupt syncinc then try again
18:09:50 <mawk> I won't lose my progress
18:09:54 <mawk> with the new version
18:10:39 <moneromooo> If it's monerod, you can stop at any time and restart.
18:17:32 <mawk> is it helpful to open a restricted rpc node? or just having a node run with the p2p protocol stuff enabled is good enough
18:23:02 <moneromooo> incoming and outgoing p2p is typically what you want.
18:23:28 <moneromooo> RPC, if you want to access your node from the outside. SSL and whitelisted key is best then.
18:23:46 <moneromooo> Public if you want, but it just gives others more incentive to not run their node, which is counterproductive.
18:27:35 <mawk> so I just have to open the right ports and that's all, no need to sign up to a register
18:27:52 <moneromooo> Correct.
18:28:12 <mawk> perfect
18:39:54 <mawk> I know it isn't technical talk, but are you afraid of XMR delisting from exchanges?
18:40:00 <mawk> like it just happened with that one I forgot the name
19:13:28 <jason_> the only path toward actually decoupling is off of the exchanges. i would def be afraid,  but only because it's such a lightly charted area .. a major cryptocurrency that can't tank in the same fashion as the others for lack of it being offered to suck up the daily market poundings .. of course the opposite could be true too .. where it also can't run up w/ the others .. still .. nice to have less 'paper monero' about :)
19:23:37 <mawk> 85733 blocks left to sync
19:23:49 <mawk> it's not just checkpoint, it's really slower the closer it is to 100%
19:23:58 <mawk> maybe it's because of the db that gets huge and the fact it's not ssd
19:24:04 <mawk> like it has to seek or something?
19:45:45 <selsta> mawk: yes it is verifying all blocks during sync
19:45:55 <selsta> which requires a lot of seeking
19:47:05 <selsta> mawk: the last checkpoint in v0.17.1.1 is on height 2210500
19:49:22 <sech1> no new checkpoints for 0.17.1.3?
20:13:13 <mawk> probably I should've enabled pruning from the start to gain time, but would that have precluded me from being a regular p2p node?
20:16:53 <sethsimmons> No, you can still be a helpful peer to the network as a pruned node, pruning in Monero was intentionally designed for that.
20:19:05 <mawk> ah nice
20:19:16 <mawk> well now it's too late I guess, I'll prune when I run out of space
20:24:17 <selsta> sech1: no, it will have new checkpoints
21:07:03 <mawk> 2020-11-08 21:04:11.385 I [8.8.8.8:8888 INC] Sync data returned a new top block candidate: 2162445 -> 2226334 [Your node is 63889 blocks (2.9 months) behind]
21:07:08 <mawk> that means my P2P node is working?
21:07:16 <mawk> if it's "INC" it means someone successfuly contacted me
21:07:55 <mawk> but none on IPv6 for now, I should see what's up
21:08:49 <selsta> mawk: type "status"
21:08:57 <selsta> 12(out)+0(in) connections
21:09:03 <selsta> means I have 12 out and 0 incoming connections
21:09:20 <mawk> 0 0
21:09:22 <mawk> but I'm still syncing
21:09:48 <selsta> both zero?
21:10:00 <selsta> what does sync_info show ?
21:10:30 <mawk> 17 peers, 1 spans
21:10:33 <mawk> but none ipv6
21:11:18 <mawk> maybe a silly question but the p2p protocol is TCP right?
21:11:39 <mawk> I saw some talk about SYN in a protocol description pdf
21:12:05 <mawk> then I suppose it's punching NAT and I have to have public ip
21:12:15 <mawk> or at least a permanent mapping between the node and my public IP
21:13:03 <selsta> ipv6 is disabled by default
21:13:20 <mawk> well I set bind address to ::
21:13:23 <mawk> when starting monerod
21:19:13 <mawk> I guess it needs to be synced first anyway
21:19:53 <selsta> can you post the full command you used to start monerod?
21:21:32 <mawk> ah yes nevermind it's not p2p which I started on ipv6, it's rpc; so I have to restart it with ipv6 p2p enable now
21:21:46 <mawk> for reference the command was: ./monerod --rpc-bind-ip 0.0.0.0 --rpc-bind-ipv6-address :: --rpc-login foo:bar --bootstrap-daemon-address auto --confirm-external-bind
21:22:02 <mawk> (the rpc port is firewalled, and open only for my lan which I access through vpn)
21:22:31 <selsta> ok that explains why it said 0/0 when doing status
21:23:32 <mawk> it's not explained by the fact it's syncing?
21:40:12 <binaryFate> New version v0.17.1.3: CLI and GUI binaries are now available at getmonero.org
21:42:14 <mawk> ah cool
21:43:24 <binaryFate> See blog posts for more details https://www.getmonero.org/blog
21:57:07 <mawk> I am infinitely disappointed, this checkpoint business didn't make it faster
22:02:00 <selsta> mawk: then it is because your hard disk
22:02:09 <selsta> there definitely are new checkpoints up until 3 days ago
22:02:43 <mawk> hmm yes must be that then
22:02:47 <selsta> mawk: is this a VPS?
22:02:58 <mawk> it's a regular server, not a vps
22:03:04 <selsta> ok
22:03:07 <mawk> but running inside a container I made myself yes, so I guess actually you could say it's a vps
22:03:13 <mawk> but I haven't put any I/O quota stuff
22:03:36 <mawk> it's running under lvm, that's all
22:05:10 <selsta> With SSD it is possible to sync up in a couple hours
22:10:28 <Franck[m]> <gingeropolous "Franck, bitinfocharts has those "> thanks!
22:34:47 <mawk> I start monerod like this: ./monerod --rpc-bind-ip 0.0.0.0 --rpc-use-ipv6 --rpc-bind-ipv6-address :: --rpc-login nicolas:koraxkorax --bootstrap-daemon-address auto --confirm-external-bind --db-sync-mode fastest --p2p-use-ipv6
22:34:51 <mawk> and I still have no connection on ipv6
22:39:37 <selsta> mawk: does print_pl print any ipv6 addresses?
22:42:36 <mawk> only ipv4 and ipv6-mapped ipv4 addresses
22:42:47 <mawk> I'll try again when it finished syncing, it's maybe due to that
22:47:30 <selsta> we don’t have ipv6 seed nodes, you might have to add ipv6 peers manually, or find peers that have ipv6 peers in their peer list
22:47:55 <selsta> as far as I understand it, but I did not use ipv6 with monero much
22:49:17 <mawk> ah I see, that's maybe why then