08:23:08 <makkiato> Hello. Is the site https://sideshift.ai/ considered trustworthy by the community? Unfortunately it does not load with the TOR browser (gives a JS React error) Are you aware of other (good) alternatives?
08:27:35 <moneromooo> I hear "Sideshift" is legit, though no idea of that domain is the correct one.
08:31:00 <makkiato> I found out about it/them in the homepage of Monerujo, so I guess it's legit. But I just contacted them and they say they do not support TOR.
08:31:56 <moneromooo> That sounds like a lie. You don't need to do anything to support tor. You have to do extra work to prevent tor from working though.
08:32:14 <moneromooo> Unless they mean a hidden service.
08:32:39 <makkiato> In this case, it is a JS error, so I guess it's possible (at least in principle) that their code breaks with the TOR JS limitations.
08:32:40 <moneromooo> Evil assholes like cloudflare make it easy to block tor though.
08:32:48 <makkiato> it's not a IP ban.
08:33:04 <makkiato> but I am disappointed by the way the answered: "we do not suppor TOR." lol
08:33:11 <moneromooo> Well, possibly they load JS or other from other sites which block tor themselves.
08:34:14 <makkiato> right. In any case I am looking for the most privacy-preserving way of converting some (small amount of) eth to xmr. If you have any suggestions, please share
08:34:34 <selsta> makkiato: as far as I know, they delisted monero ages ago
08:34:57 <selsta> maybe I'm mixing them up with a different website
08:35:08 <moneromooo> shapeshift ?
08:35:12 <selsta> oh right
08:35:18 <selsta> that was shapeshift
10:48:54 <ErCiccione> In case people missed it. Haveno's CCS to fund the user interface: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/295
10:49:03 <ErCiccione> on reddit: https://old.reddit.com/r/Monero/comments/tg6y5i/ccs_proposal_haveno_ui_funding/
14:59:47 <JoBbZ_> Hm, so the Monero GUI app is unfortunately not usable on my windows system.  It gets to about 70% of the block chain sync'd and then corrupts, twice now
15:29:54 <hyc> is it actually corrupting, or just running out of disk space
16:07:28 <JoBbZ_> hyc: It has approximately 6.8 TB of free space, it's not running out
16:17:27 <selsta> JoBbZ_: what happens exactly at 70%?
16:17:47 <selsta> daemon crash?
16:27:01 <JoBbZ> That's an excellent question.  It causes my system to reboot
16:53:55 <coxring> https://revuo-xmr.com/issue-112.html
17:18:49 <selsta> JoBbZ: could be broken computer hardware?
17:19:15 <selsta> monero has no code that causes your computer to restart, that shouldn't happen
17:28:42 <cornfeedhobo> could it be memory pressure?
17:34:08 <JoBbZ> shouldn't be, only using 30% of my 32GB of RAM.  Both times I've let it sync, it has ended up rebooting at approximately 70%.
17:34:20 <JoBbZ> unless monero eats up the other 70% of RAM while running
17:34:41 <JoBbZ> I still wouldn't expect it to cause the system to reboot uncleanly
17:35:14 <JoBbZ> I don't have this issue with MyMonero, either
17:56:53 <bertvvvs> Event Viewer shows nothing?
18:00:40 <JoBbZ> not for what I originally filtered on, but I see one from bugcheck, putting the dmp file into windbg now
18:03:11 <JoBbZ> double fault abort
18:04:31 <JoBbZ> I wonder if it made my CPU overheat :P
18:05:40 <selsta> JoBbZ: mymonero doesn't do any syncing / scanning
18:05:47 <selsta> so it's not CPU intensive
18:06:21 <selsta> there are stress tests you can run to check your hardware health
18:08:12 <selsta> some can correct me if I'm wrong but rebooting means either a bug in windows or some hardware issue, a bug in an application shouldn't completely shut down the whole OS
18:09:20 <bertvvvs> JoBbZ: bitlocker enabled?
18:10:39 <JoBbZ> bertvvvs: no, I have bitlocker turned off
18:11:25 <JoBbZ> selsta: yeah, the article I'm reading indicates potentially a damaged CPU or not a current microcode version.  I'll have to see if this happens w/o monero running.
18:14:23 <bertvvvs> try downloading the raw blockchain: https://www.monero.how/tutorial-how-to-speed-up-initial-blockchain-sync
18:14:55 <JoBbZ> thanks!
18:21:57 <selsta> that will still require verification, which is CPU intensive
18:30:05 <JoBbZ> yeah, I'm going to run the intel cpu diagnostic tool see if it finds anything
18:44:46 <gingeropolous> selsta, yeah the IPs that were showing up on those logs look... familiar
18:45:26 <selsta> gingeropolous: as far as I know the first person tried with ban list and it didn't help
18:45:32 <gingeropolous> hrm
18:45:32 <selsta> but maybe it's other IPs
18:45:38 <selsta> so still worth a try
18:45:51 <gingeropolous> but isn't it odd that it would sync up to a certain height?
18:46:00 <gingeropolous> well, i guess an attacker would want it to look normal for a bit
18:47:46 <selsta> I tried syncing up with a fresh VPS and no ban list and didn't have any issues
18:48:49 <JoBbZ> no issues found by the diagnostic tool
18:51:11 <gingeropolous> i wonder if seed nodes are borkt
18:51:38 <gingeropolous> well, that wouldn't explain y u can syn with no issue. did u try syncing with a new ..... yeah fresh VPS. hrm
18:52:12 <gingeropolous> my one seed node is blowing these everywhere: 2022-03-17 18:51:54.225	[P2P0]	ERROR	net	contrib/epee/include/net/abstract_tcp_server2.inl:777	Setting timer on a shut down object
18:53:02 <gingeropolous> eh ill just run master
19:11:29 <selsta> gingeropolous: seed nodes are unrelated
19:11:52 <selsta> they are able to sync to a specific height, at this point seed nodes aren't used anymore
19:12:03 <selsta> also the message you posted is harmless IIRC