00:06:40 selsta: I thought so, and I support that. How much are they going up by? 00:06:51 by 5x from what i remember 00:07:21 so around 0.5c to 2.5c 00:07:45 That's fair enough :) 00:08:16 Got to make mining worth while. 00:17:45 selsta: Forgot to say thanks for your help, sorry. 00:25:03 Is small scale XMR mining possible on a VPS, provided it had a dedicated CPU? 00:32:38 possible yes, but not recommended on a VPS 00:35:11 VPS providers also don't like you mining 00:35:33 it can be a reason to get banned 00:35:50 also it simply isn't worth it due to low hashrate in virtual machines 00:39:58 Mochi101: That's quite the time, almost enought to compile Firefox. 00:44:09 See ya 01:22:39 selsta: okay, thanks for explaining. :) 01:45:23 For the love of god why does monero have to have such an awful user experience??? 01:45:46 Updated to v18 of the gui and now it tries to resync the entire blockchain 01:45:57 This process takes days 01:46:35 Dammit bitcoin takes seconds to sync 01:47:29 This is eating 1MB/s of my internet all day long 01:47:52 Bitcoin takes several days to sync., Electrum takes a few seconds. :) 01:48:02 Yeah electrum is what i mean 01:48:08 Just like the gui in remote mode takes a few minutes. 01:48:19 No it doesnt, i am using remote node and it takes days 01:48:28 Crap remote node then. 01:48:32 It tries to download entire blockchain but it doesnt save it on my pc 01:48:38 That's not remote node then. 01:48:56 Remote node doesn't download anything other than your wallet data which is ~30-40mb for my wallet (Pool based) 01:50:04 Remote nodes download entire blockchain to check locally the rings in your wallet against it otherwise it would broadcast to some node you tx's, right? Everytime i have used remote node it downloads entire blockchain and immediately deletes it from my pc as its checking it 01:51:12 Not that I've ever seen before, but I always cli mine. Also, if you know when your wallet started, you should be able to provide an offet. 01:51:14 (offset. 01:51:42 The offset doesnt help it still takes days 01:51:55 You can syunc an entire monero node in < 24 hours. 01:51:59 What kind of disk are you on? 01:52:05 SSD 01:53:31 No idea then tbh. That's super slow no matter what, I literally dump the entire thing in < 24h on a modern PC, wallet syncs take, from 0 about an hour. 01:56:56 what is data.mdb in my monero folder and why is it 3gb? 01:59:12 That would be because you're still running a local node. 01:59:18 data.mdb is the monero database. 02:00:09 It looks like the update erased all my remote nodes and defaulted me to local 02:00:30 :) 02:00:33 Easy to fix., 02:00:37 this is what i mean, worst user experience ever 02:00:50 Tbh, most of us just use the CLI. 02:01:13 If I had to guess, we're probally saving your config in a folder somewhere, and it's versioned to your monerod because of stuff like ringct/etc. 02:01:30 But that's my. /guess/ I haven't looked at the GUI project in quite some time. 02:02:24 well i input my remote node and now its doing the extremely slow wallet block downloading process still 02:03:09 why cant we have real remote nodes like electrum has 02:03:13 instant sync 02:03:39 Feather wallet is similar to Electrum if you're looking for that. 02:03:51 no wonder everyone uses mixers and shit like tornado cash instead of this 02:04:02 Because electrcum gets to cheat, and knows exactly what txns are yours. :) 02:04:09 XMR has nothing like that because privacy. 02:04:09 tried feather wallet still doing this download gigabites of blockchain shit 02:04:26 Feather is remote node only. Doesn't download the blockchain. 02:04:40 There's tradeoffs for everything. If you want to enjoy privacy, you're gonna have to deal with some work. 02:04:51 oh my god can people stop spreading those bullshit lies, remote nodes on monero download gigabites of blockchain 02:04:56 ive had to deal with this for years 02:04:59 it does this every time 02:05:03 It doesn't, because I literally do it all the time. 02:05:03 :P 02:05:27 I do run my remote node on my network, and it's all nvme, but it's not yeeting the entire monero DB to you. 02:06:12 In any case, just upgrade to the CLI wallet, and keep it synced w/ the occassional save and your deltas will be so small you won't even notice. 02:06:42 i dont know what that means 02:07:36 Wellp, guess you're stuck with the slow GUI process then. Tbh, I think people are generally working on that (If memory serves right, this HF is supposed to help with it, from my understanding). 02:08:36 ... next fork in 0.7 days 02:09:09 Yeah, I don't have the screen up for when it is. I've been busy patching pools. :P 02:09:48 still waiting for minexmr to shut down 02:10:10 Technically, only 7 PM here on the west coast. 02:10:11 is it the 12th yet? 02:10:16 Yes. 02:11:10 so you are saying this downloading gb with a remote node is a problem with the gui version? 02:11:55 the GUI definitely doesn't download GBs, unless you sync multiple months of history 02:12:45 yeah it doesnt do it everytime, but if i have to reinstall everything it does, but is that gui specific or just how monero works? 02:13:08 Given that you said "When I reinstalled everything, ti disabled my remote node, and enabled my local one" 02:13:16 which OS are you using? 02:13:17 I would say "That's you don't know how to check your config" 02:13:49 Two different scenarions, recently i just updated the gui version, its moving along alot quicker now but still taking a little while. 02:14:23 > It looks like the update erased all my remote nodes and defaulted me to local 02:14:30 If it removed your remote nodes and put you to LOCAL 02:14:34 If i reinstall everything, that means all monero files are delete, i start over, i input my seed and wallet height, my remote node address, then it proceeds to take days eating bandwidth to sync again 02:14:34 It's going to download the entire chain. 02:14:48 Did you restart the gui after setting up remote? 02:14:57 IIRC, the node doesn't auto-shut-off when you put in a remote. 02:15:07 As the remote is, in theory, a temporary fix until your local node is synced. 02:15:11 Yeah the update fucked over my wallet settings, i corrected it now, it appears to be syncing faster as expected 02:15:39 which OS are you using? 02:15:48 Debian 02:16:33 we use https://doc.qt.io/qt-6/qml-qt-labs-settings-settings.html 02:16:49 if it gets wiped for no reason (assuming you didn't delete the settings) then it might be a bug in Qt 02:16:58 I didnt restart the gui, if i input remote node it shows up in a list in the wallet, then all i do is click on it and it connects to remote node, no need to restart 02:17:01 so far I did not read any other report about this 02:17:18 i didnt delete the settings, i just updated it and it wiped my settings 02:18:49 it's one of those next to impossible to debug issues 02:19:09 It seems to be a bug in Qt, so not even our code. There is no way to reproduce the issue, etc. 02:21:05 Then shouldnt first start of gui show at least a message warning that setting may have been deleted? Why are developers so adverse to warning users of bugs and flaws 02:22:13 Or a message next to remote node "monero remote nodes still require massive amounts of data to be downloaded, this may take many hours". Most users will think something is wrong when this happens. 02:22:14 It does show a "welcome to monero" screen on first start 02:24:02 The tech behind monero is so much more complex than the gui programming, if theres this many issues with something so basic it doesnt inspire confidence that the tech isnt full of problems too 02:24:04 The only time where you would wait a while and use a lot of data is when restoring a multiple year old wallet. 02:24:11 lol 02:25:00 or maybe the GUI has no contributors 02:25:10 Even the shittiest coin will always have a very clean working gui wallet. It took monero years to even put out a gui. 02:25:42 Yeah thats dumb though, monero devs have to be sitting on millions of dollars in coin, they could have a full team on that alone 02:25:57 there is literally no dev tax and no premine 02:26:04 monero devs have nothing 02:26:36 As if fluffypony wasnt mining the shit out of it since day 1 02:27:17 shittiest coins are all simple forks, obviously they don't code their own gui 02:27:20 at best they get a reskin 02:35:25 also you can use light wallets like mymonero.com if you care so much about every MB data 02:36:01 you would still have better privacy than in bitcoin 02:37:10 Lol the haters are so easy to spot in a project with no premine and no dev tax 02:37:41 who would have thought that researchers don't work on a gui 02:46:26 jeese... 02:47:05 researchers hate their users? cause cli is a big fuck you to 99% of users 02:47:10 SquirrelCity wants a 75% premine. 02:47:44 i linked a light wallet that is so easy to use that nothing can go wrong 02:48:02 SquirrelCity, you can't have your cake and eat it too. There are tradeoffs to having some privacy. 02:48:33 A little bit of sync time is part of it. 02:48:44 1 day of wallet sync is like 15MB 02:49:05 LIke i just synced this thing two days ago and now im sitting here for several hours watching it sync 02:49:19 You're doing something wrong. 02:49:21 then you did something else wrong 02:49:21 not from scratch, from where i last synced 02:49:30 User error... 100% 02:49:39 What system are you on? 02:49:44 i didnt do anything but update the gui software and now have to reset the remote node 02:49:46 2 days = 1400 blocks = 3 seconds with a remote node 02:49:48 thats literally all ive done 02:50:01 maybe 5 seconds 02:50:09 600000 blocks remaining 02:50:13 wtf 02:50:16 that's not 2 days 02:50:25 which remote node did you set? 02:50:30 SquirrelCity, are you on Windows or Linux? 02:50:33 its some onion node 02:50:37 im on debian 02:50:38 lol 02:50:41 running through tor 02:50:51 man 02:51:09 are you using tails? 02:51:12 i mean thats what youre supposed to do, running over clearnet breaks the anonymity 02:51:17 no 02:51:36 are you sure that you don't have issues with persistent storage? 02:51:46 Running over clearnet doesn't break the anonymity. 02:52:14 no my system is persistent, i have a 3gb piece of monero chain sitting on it for some reason from a previous session 02:52:29 if you synced 2 days ago and now have to sync 600k blocks it means that it did not save the wallet cache correctly 02:52:33 yeah it does break the anonymity, it creates a side channel attack 02:53:22 then the software is fucking up because i didnt do anything besides open it and close it after it had finished 02:53:32 could also be permission issues on your side 02:54:00 yeah maybe if this gui is trying to plant its file somewhere it shouldnt be 02:54:01 so your GUI settings are gone and your wallet cache didn't save correctly? two completely separate pieces of code failed here 02:54:16 sounds more like an issue on your system 02:54:29 its fucking debian like i didnt do anything special to it 02:54:47 such patience 02:55:10 what sort of OS do they even test this on, pop os? arch? 02:55:25 windows 95? 02:55:33 it's a bit funny that you complain about slow sync while using tor 02:55:49 You're the beta tester SquirrelCity. 02:55:52 yeah well tor is fast now, i get like 500KB/s on the remote node 02:57:46 ok on my home folder i got three folders for monero in it, .bitmonero which has a 3gb blockchain file, one called Monero which has a wallet file, and another one called monero-strage with a wallet folder, settings.ini, and monero-wallet-gui.log. 02:57:59 *monero-storage 02:59:09 you can delete ~/.bitmonero 02:59:16 and under .cache folder there is monero-project folder which has monero-core folder in it and qmlcache folder in that and then a bunch of random filenames in it 03:00:15 "one called Monero which has a wallet file" <-- it should have wallet and wallet.keys 03:00:24 ok before i do, .bitmonero has not only the blockchain file but bitmonero.oog, p2pstate.bin, p2pstate.bin.unportable, rpc_ssl.cert and rpc_ssl.key 03:00:41 Yeah that one has wallet and wallet.keys 03:00:57 *bitmonero.log 03:01:11 in `wallet` it should save the wallet cache, meaning the synced blocks. in `settings.ini` it saves the GUI settings. 03:01:20 they are all only relevant for running a node 03:01:40 since you don't run a node you can delete it 03:02:12 i dont see a wallet cache anywhere 03:02:30 the file namend wallet without extension is the wallet cache 03:02:50 i found in my home directory now a folder called .shared-ringdb that has the same blockchain files but they are only a few kb 03:03:33 How big should the wallet cache be? this one is 9MB 03:03:48 how old is your wallet? 03:03:53 and when was the wallet cache last saved? 03:03:54 years 03:04:04 like days ago 03:04:20 i think i made it in 2014 or somehin 03:05:01 does the wallet cache seem to save correctly? 03:05:10 it should update once every 10 minutes 03:05:35 it doenst give any errors, seems to work fine 03:05:43 it meant the last modified date 03:06:10 2021? wtf 03:06:34 yea like i said it seems like permission issues 03:06:48 can you go to Settings -> Interface, what does it say as autosave value? 03:06:58 ok the monero-storage folder with the wallet files in there (there are two folders with the same wallet for some reason) show it updated today 03:07:25 10 minutes 03:07:30 maybe you simply opened the wrong wallet file? 03:08:26 seems you enabled portable mode, which should save most of the data in monero-storage, including default wallet location 03:08:31 i just opened the gui as usual, i didnt select a wallet when i did 03:09:05 yeah i see under info it says remote node, portable 03:09:58 it should also say the wallet location on info 03:10:40 yes its under monero-storage, so the the regular monero folder is the extra one. 03:10:56 the regular monero folder seems to be from before you used portable mode 03:12:00 Cool well still at 600k blocks left and should be done next week at this rate 03:12:25 there comes a point where if i want privacy ill just pay in cash 03:12:41 it takes less than a week to mail it and i dont have to leave my computer on 03:12:49 try mhfsxznn5pi4xuxohj5k7unqp73sa6d44mbeewbpxnm25z3wzfogcfyd.onion:18081 03:13:44 Im averaging 400KB/s with nothing else running, tor doesnt really go much faster 03:13:56 compared to 10 years ago this is crazy fast 03:14:16 600k blocks is over two years of history, how often does one sync 2 years of blocks over tor? 03:14:37 hopefully never but apparently monero requires it at every update 03:14:43 it does not 03:14:53 yeah well it does for me and it has every single time 03:15:35 there have been so many times where i would have willingly used any other crypto just to have something that worked 03:16:04 no one forces you to use monero 03:16:05 ive lost opportunities because i fired up monero and it had to sync for 3 hours 03:16:22 well it seems like the only privacy solution at this point 03:16:28 its a shit situation 03:16:37 you don't have to sync over tor 03:16:38 Send me your seed and I'll tell you how fast I can sync it on my system. 03:16:50 halarious 03:17:08 yeah i do, side channel attacks are a thing 03:17:30 my internet connection isnt that much faster 03:17:37 if you use monero frequently you could run your own node and then sync a wallet from block height 0 in like 20 minutes 03:18:16 i dont have the space to run a full node or else i would have, yeah it would save alot of this headache 03:18:51 the monero bloat is massive and getting worse 03:19:10 but its the tech, no way around that 03:19:12 pruned is 50gb for 8 years of blockchain history 03:19:28 and there is no downside in pruned node, you still have full history 03:20:13 But i have to download the whole thing to prune it? 03:20:29 i may be able to fit 50gb 03:20:36 its gonna eat up all my space 03:21:12 i dont wnat to reinstall my entire system to get a new drive 03:21:38 just to fit a monero blockchain on it because it otherwise takes hours to send a tx 03:22:10 it really shouldn't take hours to send a transaction 03:22:22 you sync a wallet once and then you only have to sync it from the last state 03:22:27 582000 blocks left 03:22:57 you said you have two wallets in monero-storage 03:23:02 which size does the wallet cache have? 03:23:27 6.4mb 03:23:30 i only have one wallet 03:23:46 i have some files named wallet.old_cache that last modified in april 03:23:46 close this one and open the 9mb one 03:23:55 oh wait, that is also 2021 03:23:59 9mb from a year ago? 03:24:10 yeah no i dont want to start over again 03:25:16 closing and reopening gui, maybe it will update faster 03:26:01 sometimes if i connect to a new remote node it will star the sync way back over again, not years but like months 03:26:32 i think thats where i remember it taking 3 hours to sync, when the node i was using no longer connects because onion nodes break all the time 03:26:43 try the one i posted 03:26:50 i maintain it 03:27:15 im not on the same computer... no way to copy that over except by hand 03:27:39 if only tor didnt force stupidly long onion addresses on everyone for no reason 03:27:59 https://termbin.com/k24n 03:27:59 tradeoffs 03:28:51 easiest way to copy long urls 03:31:50 Can you all suggest another privacy coin? im so tired of this shit, i cant even catch a break on the bullruns witht his coin, crabbing constantly breaking pain in my ass 03:32:02 try zcash 03:32:07 missed so fucking hard in 2021 investing in this crap 03:32:10 i heard their wallet can't even set a custom blockchain location 03:32:35 zcash is a joke, trusted setup give ma fucking break 03:33:55 firo looks like the only thing else around 03:34:31 "if i connect to a new remote node it will star the sync way back over again" <-- the only way this can happen if you connect to a remote node that is still on and old chain or so, but even then the wallet has reorg limits 03:34:44 at least newer version have a reorg limit 03:34:59 i get my remote nodes from xmrguide.org 03:35:05 they say if it is synced 03:36:06 if you 1) connect to a good node and 2) have your wallet cache save correctly is should never jump back 03:36:47 hey its happens, maybe no one complains about it, maybe they do and the devs dont give a shit, its a common occurence in free software projects. Ive never said anything because i figure if they cared they would have fixed it after so many years, but it remains unfixed. 03:37:12 we would definitely get reports about this 03:38:01 monero is fragile, forcing users to rely on a single remote node, i should be able to connect to many nodes simultaenously like every other crypto project 03:38:26 so all the data is compared and verified 03:38:45 and then an attacker runs lots of nodes 03:38:50 every time maybe one node has a bit flipped somewhere and the gui freaks out and starts all over again 03:38:56 didn't electrum print fake update messages? lol 03:39:38 so what, thats the whole point of decentralizion, moneros solution is to centralize where you get your blocks from 03:39:54 that was some centralized backdoor shit too 03:39:59 no, monero's solution is run your own node which is significantly more decentralized 03:40:31 no one takes crypto seriously anymore because everything is some half ass attempt at decentralization, and is mostly centralized. 03:41:06 Ok but at 4x the bloat of other chains isnt practical. Not every has 200GB to throw at some crypto project. 03:41:33 it's 50GB, pruning is enabled by default in the GUI 03:41:42 and privacy has its price 03:41:46 can't have both 03:42:07 So if i select local node now, its only going to store 50gb? 03:42:27 not like 200GB and then eat processor pruning it to 50gb? 03:42:50 its going to download and store 50gb? 03:43:09 start monerod from command line with ./monerod --prune-blockchain --sync-pruned-blocks 03:43:32 yes it will only use 50gb and it will also sync pruned blocks which should result in less bandwidth 03:43:44 it verifies the data and prunes instantly 03:44:39 where is monerod 03:44:44 says no such file 03:44:49 next to monero-wallet-gui 03:45:07 how did you install monero-gui? 03:45:11 this is linux, they dont want users to find where software is located unlike windows that puts everything in program files 03:45:16 through command lin 03:45:22 wbich command? 03:45:32 sudo apt install monero or something i forget 03:46:05 which version did it install in Settings -> Info? 03:46:21 0.0.00.0.0.18 03:46:34 the most recent 03:46:35 wut 03:46:40 Lol 03:47:04 what does the package say for version number? 03:47:19 0.18.0.0 03:47:23 ook, is that enough zeros 03:47:44 they could just call it v18 like a normal project 03:47:54 but yeah thats the latest i think 03:48:44 where is software installed in debian 03:48:48 there are non major releases too lol 03:48:48 bin 03:48:50 boot 03:48:51 dev 03:48:53 etc 03:48:54 can't you just enter monerod 03:48:55 media 03:48:55 opt 03:48:56 proc 03:48:57 it should install it? 03:48:58 run 03:48:59 sbin 03:49:07 like wtf does any of that is supposed to mean 03:49:22 SquirrelCity: It's usually installed under the table. 03:49:52 no if i run ./monerod it gives an error no such file 03:49:58 not ./monerod 03:49:59 just monerod 03:50:17 with the two options from previously 03:51:34 ok that worked i guess 03:52:08 2.6m blocks left 03:52:18 where is this storing it? 03:52:58 ~/.bitmonero 03:53:09 and do i select local node in the gui and it will find it? 03:53:14 yes 03:53:32 or will it delete everything and try to restart like it does with remote nodes? 03:54:40 it should not, but it also should not with remote nodes 07:34:55 69K transactions yedterday. Noice. 07:54:30 nice 08:00:15 what os the fork blockheight? 08:00:19 is* 08:01:38 2688888 08:28:29 lucky 09:31:00 If I were to start mining and join a pool, what's the average monthly income I could expect? 09:33:28 Start monerod, start mining, wait a minute, running mining_status. You can expect about that much. 09:33:58 Maybe a smidgen more, as xmrig is a bit faster at mining. 09:34:44 Also, run mining_status several times, 5 minutes apart, since its report depends on the current block reward, and it varies based on fees. 09:35:39 Or you can expect about 0.3 monero times your hash rate times 86400 times 30.5 divided by 2.5e9 monero a month. 09:36:12 Wait, this is off by a factor of 60. 09:36:36 You'd get a sixtieth of that calc. 09:37:17 P2Pool best pool btw. 09:43:06 p2pool best pool 09:48:17 moneromooo: I haven't got mining hardware yet, so I can't run the command as you suggest. I'm wondering whether to rent one of these to mine with: https://my.vultr.com/deploy/?baremetal 09:55:14 rebting hw for mining monero is 99.999% likely to be a net loss 09:55:22 renting* 09:59:25 inge: oh, oh well. 10:05:16 moneromooo: inge: You see, I'm having to rent a server now to host a monero node, so I was hoping to mine on one to offset the cost. Never mind. 10:30:00 I've heard that R Pi's are bad for running nodes on, because their CPU's lack an instruction set that Monero needs. Is that true? 10:30:53 Yes. Also because their I/O is dire AIUI. 10:33:41 moneromooo: Is there another SBC suitable for the job? 10:39:54 I hear the rockpro64 is ok. 10:40:04 I think. You'll want to ask a better source. 10:44:01 moneromooo: okay then :-) 10:44:27 * Steven_M has to go now though. 10:45:08 Thanks all :) 12:45:54 I use Rock64Pro with 4GB ram it's great 12:46:02 Armbian Bullseye 12:46:33 The metal case on Pine64 is like $15 and it does a great job 12:49:32 yeah, same here 13:45:19 Just installed p2pool on it, works great (RAM is now maxed out tho), and will be pointing ryzen 3950x toward it 13:48:45 More info: https://github.com/monero-ecosystem/PiNode-XMR/issues/39#issuecomment-1014464851 13:56:30 That project really should be renamed ARMNode-XMR or MiniNode-XMR or something because the Raspberry Pi is barely sufficient as a node board. I suppose it is fine for submitting your own tx via remote node, but I assume a major network boom may cause Pi boards to fall behind or freeze 16:03:44 moneromooo: are we doing the "two forks in 2 days" to allow old tx to empty out of the mempool (or what the reason for it was) ? 16:05:15 I am not moneromooo, but happen to know: Yes 16:15:04 this is peculiar to Monero? I don't hear other chains do it. Also, this would make it difficult with prepared transactions submitted after such a fork I guess 16:49:55 Less than 3 hours until the first consensus upgrade in two years woooooo 16:53:26 imma gunna make a tx shortly after just so that I can experience more rings 17:03:09 Same. Just so I feel special 17:56:11 garth: any idea here? https://github.com/monero-project/monero/issues/8473 17:59:04 Hyc was right about the propensity for these problems via weak power supplies. The time this happened to me was a bad board component, probably memory. 17:59:20 Both of these suggestions have been mentioned alreadt 17:59:25 Already 18:02:47 25 blocks before the fork! :) 18:05:33 Less than one hour! 18:20:49 16blocks 18:35:10 9blocks 18:35:56 block by block updates? 18:36:40 barolo - 8 18:41:48 -3 18:45:41 2 18:46:19 -1 18:48:01 (next fork in 1.0 days) 18:48:15 Nice 18:48:18 .barolo 18:48:25 Happy fork all 18:48:26 .barolo 18:48:32 May the fork be with you 18:48:43 I didn't follow much, beside upgrading my node, do we have 2 forks in a row? 18:49:19 The second fork forbids the old transaction format 18:49:31 You have 24h for transition 18:49:36 oh i see, thanks! 18:50:10 Wonder if we’ll stall at 268890 for a bit due to losing miner 18:50:18 How do I rate-limit a node properly? 18:50:24 *2688890 18:50:39 the fork happened at 2688888/2688888 I believe 18:50:45 so 2 blocks have been mined after that 18:50:47 I used --rate-limit-up and --rate-limit-down but I still saw a 79Mbps spike when synchronizing the chain 18:51:11 This ran up an unexpected bill for bandwidth so I'm trying to avoid that in the future 18:51:54 2688891 just mined! all is good 18:51:58 Happy hard fork everybody 18:54:48 never mind, looks like I needed to change my expected units, Fluorine Fermi works now 18:55:18 happy hardfork! 19:07:11 Daemon keeps crashing on Windows... 19:07:45 setting log level to 4... see what happens 19:07:48 Try running it as admin? 19:07:57 log level 4 is super resource intensive 19:08:11 2 should be enough 19:08:48 np 4 me 19:08:56 Mochi101: which version are you using? 19:08:57 Happy Fork day 19:09:39 selsta, I just downloaded the new CLI point release from getmonero... I thought because I was using 0.18.0 it was crashing 19:09:50 but the point release is crashing too 19:10:04 so far we did not receive any crash reports about both versions 19:10:05 I am on 0.18.0 19:10:29 Mochi101: do you use zmq / p2pool mining? 19:10:40 Oh yeah, v15 is out. 19:10:44 no.. nothing selsta just a node... no pruning 19:10:46 Awesome 19:11:02 how quickly does it crash? 19:11:33 30-45 seconds in... fans run up hard (but this is normal) 19:11:48 nothing in the onscreen log 19:12:13 so does it not start correctly? 19:12:35 it does... then it starts going for blocks 19:12:39 then it crashes 19:13:18 sounds like corrupted blockchain 19:15:27 consecutive opens and I need to sync less blocks though 19:15:33 so it's adding blocks 19:17:54 increase log level? 19:17:54 Do you get a core file ? 19:18:24 downloading Windows dmp file reader 19:18:31 If not, can you run in gdb 19:18:44 gdb? 19:18:50 ie, gdb /path/to/monerod, then: run 19:19:01 gdb indeed. The GNU debugger. 19:28:32 FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_msvcrt.dll!strlen 19:28:47 I don't know how to make sense of this. 19:28:53 I would say some DB issue 19:29:47 (380.1314): Access violation - code c0000005 (first/second chance not available) 19:29:57 Or some memory corruption somewhere. 19:30:21 I'll point it to my pruned copy of the blockchain... 19:30:23 :D 19:30:28 let's see... 19:32:03 I haven't synced it in years though. 19:35:02 no nodes want to connect :( 19:35:09 will wait a bit 19:35:38 Who wants to connect an a years old crusty chain... 19:37:25 lol 19:37:52 it's updating 19:40:26 maybe it is a corrupt db 19:40:37 hopefully I can just pop some blocks to fix it 19:42:11 usually no 19:42:35 This has never happened to me before. 19:44:23 Now I get to complain about sync times... like that guy last night selsta 19:44:25 ;) 19:45:05 with SSD it isn't bad 19:46:10 i synced from scratch in 8h a couple days ago 19:47:10 I have more time than I have XMR. 19:47:25 So I'm not worried. 20:07:15 hehehe... popping blocks crashes the import tool selsta 20:07:26 goodbye lmdb 20:24:10 Mochi101: if it is corrupted then you can't pop blocks 20:26:15 selsta, yeah... syncing from scratch... already 25% 20:43:26 garth: https://github.com/monero-project/monero/issues/8473#issuecomment-1214219927 20:55:42 selsta, what hardware did you sync on? 20:56:22 M1 Mac Mini 20:56:59 wow... I never thought you'd be an Apple user. 20:58:50 no gentoo / arch lol 20:59:32 coreboot? 21:01:32 I use a MacBook at home, the Mac Mini is remote for devs to login 21:01:47 since most devs don't have a Mac 21:01:54 I see. 21:02:17 I'm usually on Win 8.1 21:02:19 :D 21:02:44 My other laptop is Win 10 21:04:24 how far did it sync 21:04:47 Currently 49% from scratch. 21:10:22 when making a tx after the fork I got this message in the daemon immediately after I pushed the key to send the tx 21:10:25 E Unable to send transaction(s) via Dandelion++ stem 21:11:13 tx showed up in the block explorer immediately 21:12:06 seems the selected dandelion stem become unavailable / disconnected 21:13:03 not sure if I have ever gotten this message b4 21:13:06 maybe :) 21:13:10 so it either choose a different one or it skipped dandelion completely 21:13:20 seemed to skip 21:13:28 it exists since v0.16 21:13:52 thx 22:02:47 54% selsta. So slow... Maybe I should go sync Ethereum :D 22:06:47 maybe it syncs the pre bulletproof transactions currently 22:07:22 1466000 22:07:31 they're pre bulletproof 22:08:19 between 1400000 and 1685555 are the slowest 22:08:57 wonder if monero would be still a thing if bulletproofs weren't discovered 22:09:08 syncing would take ages and the chain would be massive 22:11:18 Hard to say... Ethereum is massive and people still use it. 22:11:43 I think I synced gETH for a week and gave up on it 22:18:58 selsta When were Bulletproofs discovered? 22:22:55 garth: https://www.getmonero.org/2017/12/07/Monero-Compatible-Bulletproofs.html 22:22:56 2017 22:24:27 Wow 22:24:33 Sort of saved our butts 22:24:56 I remember pre-bulletproof txs. Awful massive things 23:51:31 garth, yeah... 50 cents per tx 23:52:00 hmm I remember $2 tx 23:52:10 wow 23:52:27 65% here now 23:53:13 1685555 mined already? 23:53:37 1779000 23:56:47 4 hours in 23:56:54 almost