02:05:26 <chiselfuse> what are ~/.bitmonero/rpc_ssl.{crt,key} for?
02:06:49 <br-m> <gan:skhron.org> there's an argument to be had that the naming is self-explaining to be honest
02:09:22 <chiselfuse> gan: yea but the cert is expired and yet my gui connects to the node and doesn't complain. are they not in use by default?
02:10:14 <chiselfuse> even if they lack chain of trust, i'd expect at least the ssl library in the gui to refuse using the connection
02:15:06 <br-m> <gan:skhron.org> to be fair, not totally sure if they are as per https://docs.getmonero.org/interacting/monero-wallet-rpc-reference, the params are supposedly autodetect - whatever that means
02:20:03 <chiselfuse> i checked wireshark and they communicating with tls. i can't tell if it's the expired ones in that directory. my guess is that autodetect has monerod detect if the wallet sent a tls hello or started talking in protocol raw
03:24:45 <chiselfuse> gan: btw i tested it and found that monerod serves this cert, not sure about monero-wallet-rpc-reference
03:25:05 <chiselfuse> monero-wallet-rpc*
03:25:44 <br-m> <gan:skhron.org> ohhh, okay then
03:25:45 <br-m> <gan:skhron.org> I've looked at the wrong thing for whatever reason
03:26:49 <chiselfuse> i find it weird how ~/.bitmonero/ is used almost entirely by monerod except for the monero-wallet-gui.log file
06:17:49 <br-m> <ofrnxmr:xmr.mx> As you said, monerod
06:18:19 <br-m> <ofrnxmr:xmr.mx> Wallet-rpc and wallet-cli use the working directory
06:19:02 <br-m> <ofrnxmr:xmr.mx> Monerod also uses ~/.shared-ringdb
07:32:02 <br-m> <ofrnxmr:xmr.mx> Gui uses ~/Monero
07:32:02 <br-m> <ofrnxmr:xmr.mx> why would wallets use a hidden data dir?
07:33:15 <br-m> <ofrnxmr:xmr.mx> Gui also uses (iirc) ~/.config/monero-project or monero-core
07:40:56 <plowsof> related issue for the gui here https://github.com/monero-project/monero-gui/issues/2291
07:51:31 <vthor_> aphoenix:matrix.org: Glad to send you the first with XmrSigner (with OTS lib) signed transaction  https://xmrchain.net/tx/c67a676df6d741b70f209466bd1787e774fd0bf0826f4b53cc1bd6674af9a647 Have a lot of success.
08:32:12 <br-m> <rottenwheel:unredacted.org> 👀
08:32:29 <br-m> <rottenwheel:unredacted.org> vthor_ what'd you just say? 🤔
08:32:53 <br-m> <rottenwheel:unredacted.org> is that OS in alpha, beta, public yet? 👀
08:36:51 <DataHoarder> vthor: you fell for the beg spam >.<
08:42:38 <plowsof> nooooooo
08:43:47 <dukenukem> oh, well.
08:43:49 <dukenukem> tru dat.
08:44:00 <dukenukem> 👀
08:48:55 <plowsof> gitlab is offline sadly, vthors recent update shared progress / completion of it. would be great for people to try it, instructions for those with the physical device or those like myself who would require the emulator working with seedsigner compiled would be ideal 
08:54:22 <vthor> DataHoarder: don't think it was spam, I myself needed to beg a friend fro some xmr dust o test the xmrsigner, it's not that he was "begging" for a fortune
08:54:45 <DataHoarder> they posted all across random channels, dev, etc. on different nicks
08:55:30 <DataHoarder> can that however make an OutProof or SpendProof? :D
08:55:53 <DataHoarder> then it's up to par to my libraries which spent something from the zero-key wallet the other day
08:55:59 <vthor> rottenwheel: I made the first transaction with the "new" XmrSigner(-os (dev build)), when I stop writing I will build a dev and non dev build for pi0 and put it in release.
08:56:35 <DataHoarder> monero.social having issues >.<
08:56:54 <br-m> <rottenwheel:unredacted.org> 👍️
08:57:00 <vthor> DataHoarder: "can that however make an OutProof or SpendProof?" nope
08:57:07 <DataHoarder> https://irc.gammaspectra.live/c808efe602cd3840/image.png 
08:57:33 <br-m> <rottenwheel:unredacted.org> oh lordy, great.
08:57:54 <br-m> <rottenwheel:unredacted.org> another day in mononoland.
08:58:01 * br-m <rottenwheel:unredacted.org> sips
08:58:16 <dukenukem> The bridge bridges the /me pretty well.
08:58:19 <dukenukem> =]
08:58:37 <DataHoarder> it was temporary
08:58:47 <DataHoarder> but yeah, dropped some of the messages due to timeouts
08:58:52 <dukenukem> context deadline exceeded?
08:58:59 <dukenukem> what timeouts?
08:59:12 <DataHoarder> vthor: https://blocks.p2pool.observer/tx/8367d8b97545a884881817b74b3105a60f152b139a3dc0cea6d4a6e9a95a9d60?address=8AHBTeYxHJgB3K1Gi7WLNyLa4TE9YJSr9WNtz1RSnjW3K2Dqe2cXy8UUcTBj9WtDkjQrDW6LV8dCtYNpUDuAwRRw5vrowfN&txkey=4bfe58107010cd3210c7f44c9cd68c9a242fdc314bc3af6e8f8ac5761406f80e the tx made using my  BP+ proof code and CLSAG proof code
08:59:23 <DataHoarder> and ofc, SpendProof https://mrelay.p2pool.observer/e/xoO1tZQLWEpsQzho
08:59:47 <DataHoarder> funny cause monero wallet by default cannot spend from this wallet (zero-scalar key)
09:00:07 <DataHoarder> dukenukem: HTTP timeouts, server timeouts, doesn't matter, "matrix server" timeouts so messages cannot be sent
09:00:49 <br-m> <ct:xmr.mx> @rottenwheel:unredacted.org why did you have plowsof create your twitter account in the first place? I mean it should be pretty simple with single use phone numbers to create am account, no?
09:00:50 <DataHoarder> context deadline exceeded means in standard ways that the deadline set to the operation failed (timeout)
09:08:13 <br-m> <ct:xmr.mx> Read your github reply rotten. Your initial post read like you asked plowsof to create an account for you, not that he front-ran you. That's an important difference
09:13:09 <plowsof> me front-running would be a lie. i was also asked to create the or a reddit account but felt he could at least do something himself (after he asked me to create the irc account, and the twitter federated account which uses a paid relay from pluja  (was it 0.01 xmr from my own wallet?).  all of which i returned the details for promptly
10:02:31 <br-m> <321bob321> Plowsof was haveno frontend?
10:29:25 <plowsof> s/was/wen 😔
10:49:21 <vthor> dukenukem:  rottenwheel: https://github.com/XmrSigner/xmrsigner/releases/tag/v0.11.0
10:51:53 <vthor> the first signing XmrSigner images for pi0, feather 2.8.1 crashes on importing key images, tested successfully with 2.6.8 and 2.7.0, I guess it has to do with changes in wallet2, but can not say it confidently without to adapt ots to the current master.
10:53:59 <br-m> <plowsof:matrix.org> can the release artifacts be used in the emulator vthor?
10:57:32 <vthor> No, but I will thinker now if I can get the libmonero-ots.so in a appimage of the emulator, if I succeed (I hope and I'm releatively confident) I will add it to the release for siduction and ubuntu 24.04 lts
11:02:19 <vthor> in reality the emulator is the python XmrSigner code + installed OTS library. I have a script that makes an executable, but the libmonero-ots.so is not yet included, so it will for sure fail on a machine where libmonero-ots.so is not installed.
14:42:05 <br-m> <pw:xmr.mx> plowsof: what does he do?
16:02:13 <muffinmeow> hello people, do any of you have any recommendations on how to perform the first sync of a monero node? i have tried running `monerod` normally, without pruning as i heard pruning might be more likely to get corrupted (please correct me if i am wrong), and it got corrupted at 99% and gave a BUS error. I have also tried downloading the blockchain from a remote source (from getmonero.org), but the `blockchain.raw` file was only 80GB, and I don't know i
16:02:15 <muffinmeow> f it is up-to-date.
16:04:19 <muffinmeow> it took a pretty long time to do all this... but unfortunately it didn't work
16:10:05 <sech1> Just running monerod is the way. Block chain download is outdated
16:10:49 <sech1> BUS error shouldn't normally happen
16:10:49 <muffinmeow> sech1: thank you! i guess i will try again...
16:11:07 <muffinmeow> it happened when it was at 99%, i really don't want it to happen again
16:11:11 <sech1> Is it a raspberry pi or something?
16:11:24 <muffinmeow> no, its a consumer device
16:11:53 <sech1> It's better to sync on your desktop and then just copy data.mdb
16:11:58 <muffinmeow> there was no sudden shutdown or anything, there were no disconnections whatsoever
16:12:10 <muffinmeow> sech1: well i was trying to sync on my desktop
16:13:28 <br-m> <jeffro256> Mac ARM chip?
16:13:40 <br-m> <ofrnxmr> > <muffinmeow> hello people, do any of you have any recommendations on how to perform the first sync of a monero node? i have tried running `monerod` normally, without pruning as i heard pruning might be more likely to get corrupted (please correct me if i am wrong), and it got corrupted at 99% and gave a BUS error. I have als [... too long, see https://mrelay.p2pool.observer/e/zJOC_JcLb1J1TFRi ]
16:13:40 <br-m> <ofrnxmr> You are corrected. Pruning isnt more likely to be corrupted
16:13:48 <sech1> BUS error sounds like ARM
16:14:11 <muffinmeow> not ARM
16:14:16 <muffinmeow> x86_64
16:14:28 <muffinmeow> its a regular computer if that makes sense
16:14:55 <sech1> Never seen it on x86. Maybe your computer is unstable. Run some stability tests first
16:15:05 <br-m> <ofrnxmr> (TECHNICALLY since it does more operations, it would be more likely to be doing something during an unclean shutdown that could cause corruption, but its not a differencethat is lose sleep about)
16:15:45 <muffinmeow> stability tests? i don't really have any other option anyway
16:16:00 <muffinmeow> this is my personal computer
16:16:50 <muffinmeow> also, sorry for going off-topic a little, but what is the matrix room ID for the bridged room?
16:18:57 <br-m> <jeffro256> Like memtest 
16:21:52 <muffinmeow> i guess i will try to prune it next time, since not pruning already failed once
16:30:14 <br-m> <ky:tilde.horse> hi im pwny
16:30:26 <br-m> <ky:tilde.horse> last time i spoke here, a mysterious stalker tried to scare me with my ENS metadata
16:30:31 <br-m> <ky:tilde.horse> i'd like to inform you that i got my tax returns
16:30:43 <br-m> <ky:tilde.horse> most of it was taxable income i made from being employed
16:31:02 <br-m> <ky:tilde.horse> i recommend the same if that actor is still here lol
16:36:00 <moneromooo> SIGBUS can be had on x86_64 for very invalid memory accesses. 
16:36:37 <moneromooo> I've seen that with lmdb before. Can't recall the details of "very" though.
16:37:26 <moneromooo> I *think* it was accesses via mmap beyond the huge mmapped area...
16:38:13 <moneromooo> might hav been triggered by bad data from the db tree structure itself. Memory's hazy.
16:38:27 <moneromooo> But corrupt db for sure.
16:40:07 <muffinmeow> moneromooo: so do i just try again?
16:40:52 <muffinmeow> i don't think i have any different options other than trying again but with pruning this tine
16:40:56 <muffinmeow> *time
16:47:27 <moneromooo> Yes. If you want to guard against this happening again, and you have space, you can exit monerod from time to time and copy the db so you have less to redo. 
16:49:19 <muffinmeow> moneromooo: yes that is definitely something i shoudl've done last time...
16:49:28 <muffinmeow> thank you!! and thank you to everyone else who answered
16:49:53 <moneromooo> Well, it's not supposed to happen in the first place :/
16:50:36 <muffinmeow> yeah... it was really annoying when i waited for that long and i got hit with a SIGBUS error at 99%
16:51:36 <muffinmeow> oh also, what is the current size of the blockchain? i have like 200GB or free space, but i also have external storage options if that's necesarry
16:54:15 <moneromooo> A bit more than 200 GB IIRC :) External is more prone to corruption though - easier to break connection.
16:54:45 <moneromooo> pruned is less though, like a third or so
16:55:24 <moneromooo> If you sync pruned, i suggest adding --sync-pruned-blocks, saves on dl size with close to no security impact.
16:55:53 <moneromooo> And yes, "close to no security impact" does sound dodgy :D
16:57:00 <muffinmeow> eh no, it seems safe enough
16:57:06 <muffinmeow> thanks again
16:57:57 <muffinmeow> im guessing pruning would also reduce the time it takes?
16:59:41 <stmuthur> hey guys. what steps are necessary to backup and restore the blockchain?
17:08:56 <br-m> <ct:xmr.mx> stmuthur: copy the .bitmonero folder to a different location for backup, copy it back to the original location to restore
17:09:28 <moneromooo> and make sure bitmonerod is not running while you do that.
17:09:55 <moneromooo> Syncing pruned blocks should be a bit faster, but it really depends on your bottleneck.
17:10:42 <muffinmeow> moneromooo: i believe the bottleneck would be internet speed
17:10:45 <moneromooo> Pruning without --synced-pruned-blocks actually is slower, since it syncs fully then prunes data older than ~5k blocks.
17:11:00 <muffinmeow> i will make sure to add that flag
17:14:03 <stmuthur> thanks guys
17:17:22 <br-m> <pw:xmr.mx> monerod will continue to sync from it'd last point, no? > <moneromooo> Yes. If you want to guard against this happening again, and you have space, you can exit monerod from time to time and copy the db so you have less to redo. 
17:19:56 <br-m> <pw:xmr.mx> add --prune-blockchain on first run.
17:20:14 <br-m> <pw:xmr.mx> muffinmeow: add
17:20:14 <br-m> <pw:xmr.mx> --prune-blockchain on first run.
17:21:13 <muffinmeow> okay, should i *not* add it when i stop to make a backup and then continue again?
17:23:30 <br-m> <pw:xmr.mx> why would you stop and make a backup?
17:23:30 <br-m> <pw:xmr.mx> `/monerod --pruned block chain
17:23:30 <br-m> <pw:xmr.mx> if it errors or stalls at any point shut down terminal and run it again and it will continue from just before it's stall point
17:24:23 <br-m> <pw:xmr.mx> sorry for the edits @ IRC people 
17:25:41 <br-m> <pw:xmr.mx> if it faults, just run /monerod and it will continue from where it left off.
17:25:41 <br-m> <pw:xmr.mx> 👍
17:29:26 <br-m> <pw:xmr.mx> just noticed when I edit it takes out - else where. ffs auto correct
17:29:26 <br-m> <pw:xmr.mx> /Monero --pruned block-chain
17:29:26 <br-m> <pw:xmr.mx> only needed on the first run.
17:31:04 <br-m> <pw:xmr.mx> I give up. touch some gass. auto correct is pwning me
17:31:16 <br-m> <pw:xmr.mx> this > <@pw:xmr.mx> add
17:53:44 <stmuthur> lol
18:09:49 <br-m> <infiniteinfinity:matrix.org> I’m literally only $2.67 short to place an order. I know this is a long shot, but can anyone lend me just three dollars? I’ll repay you $10 next week. 🙏🥺 84PVFkghz6CLb9Uf6tCQg45DhimMPs1qaSK2atAQHJjoaWGxabBKiroZqPBd7Y6CnB389fgd85nL1UwtYKmKzgWc8FQ7362
18:11:14 <DataHoarder> plowsof ^ the beg worked and they are in for more
18:11:59 <DataHoarder> see vthor different nick, different ask, different reason, beg spam/scam :)
18:12:04 <DataHoarder> cause it worked they are in for more
18:59:48 <nioc> I have nothing to give now so just pay me $7.33 next week
19:02:33 <muffinmeow> hehe
22:01:14 <br-m> <kiersten5821:matrix.org> > <muffinmeow> hello people, do any of you have any recommendations on how to perform the first sync of a monero node? i have tried running `monerod` normally, without pruning as i heard pruning might be more likely to get corrupted (please correct me if i am wrong), and it got corrupted at 99% and gave a BUS error. I have als [... too long, see https://mrelay.p2pool.observer/e/5-T6hZgLQnAxQ0pX ]
22:01:14 <br-m> <kiersten5821:matrix.org> it means some part of your hardware is bad, if you cant diagnose whats wrong with your current hardware like memtest, you will have to buy new hwrdware
23:05:55 <vthor> DataHoarder: wow, you can't see the difference?
23:06:59 <DataHoarder> difference?
23:07:14 <DataHoarder> it's in ref to: > 10:54:22 <vthor> DataHoarder: don't think it was spam, I myself needed to beg a friend fro some xmr dust o test the xmrsigner, it's not that he was "begging" for a fortune
23:07:53 <vthor> yes, and you don't see the difference between this one and the other one?
23:08:09 <DataHoarder> it's the same address, spammed across multiple unrelated channels :)
23:08:59 <vthor> heck, you are right.
23:09:24 <vthor> my bad. This world is more then screwed
23:09:30 <DataHoarder> because they got some dust now they know they will get some so they will probably ask every few days (that's how the previous ones behaved)
23:10:08 <vthor> and then even so cheeky to use the same address.
23:10:33 <DataHoarder> just ask them for a main address next time :)
23:10:46 <DataHoarder> so they can mine, and won't work for exchange addresses
23:15:20 <vthor> well, in this case I felt because I myself wanted to implement for Monero-gui the necessary area labels for the screen reader, but my live goes pretty sideways to not say south, so I was not able to fullfill what I wanted to do (still plan it later in a slower pace if not yet done), and I needed two weeks ago also only some dust to verify myself the XmrSigner transaction. So now officially I felt for an elderly scam :D (and I was laughing before always about 
23:15:22 <vthor> all the scams...)
23:26:49 <muffinmeow> <kiersten:matrix.org>: well it works fine on a daily basis, and it managed to get to 99%
23:27:24 <muffinmeow> this wouldn't happen if i stopped the process from time to time to back the database up and keep going
23:28:05 <muffinmeow> i could've continued from one of the backups in case of a corruption without starting all over again, simply "getting new hardware" isn't really an option
23:33:05 <muffinmeow> also sorry if that wasn't a proper reply or mention, i don't know how to reply to matrix users through this bridge
23:35:19 <br-m> <gan:skhron.org> their problem in all fairness, they should setup proper pushrules if that's a concern 🧌