01:00:59 <apotheon> wow
01:01:05 <apotheon> already up to Mochi102 again
01:01:13 <apotheon> How soon does Mochi103 happen?
01:07:05 <alMalsamo> selsta: Can I configure pruned blockchain WHILE I am downloading like BTC supports or do I need to download the full blockchain to disk and THEN prune it?
01:10:24 <nioc> alMalsamo: set pruning while downloading the blockchain
01:10:37 <nioc> it's the only way to actually save the space
01:23:37 <Bill48105> right or you end up with it bigger than necessary if you turn on after unless you manually shrink it after
01:24:52 <nioc> if you prune afterwards it doesn't reduce the size but it does prevent it from growing
01:26:22 <nioc> until the pruned chain grows to the size of the regular chain that you started with
01:34:55 <alMalsamo> nioc: How do I configure this?
01:35:32 <alMalsamo> Also why wouldn't pruning after downloading the full blockchain reduce the size?
01:37:06 <nioc> I only use the CLI and know that there is a flag to use at initial startup but don't remember  
01:37:08 <nioc> it is persistent so you only need to use the flag the first time 
01:37:30 <nioc> as to why, I have no idea  :)
01:38:13 <nioc> for sure selsta will know
01:38:34 <nioc> know all the things  :D
01:39:10 <Bill48105> google works :) https://www.getmonero.org/resources/moneropedia/pruning.html
01:39:56 <selsta> alMalsamo: --prune-blockchain
01:40:06 <selsta> you only have to use the flag once
01:40:13 <selsta> then it will stay pruned
01:40:51 <selsta> ok nioc wrote that already :D
01:42:29 <Bill48105> well there's ./monero-blockchain-prune too which is what i was referring to earlier
01:42:40 <nioc> confirmation is good 
01:42:52 <Bill48105> but you need enough free space to copy the existing in place
01:43:56 <Bill48105> enabling pruning is is different than actually pruning it
01:44:52 <Bill48105> thus --prune-blockchain (enable pruning only needed once as it saves the setting) vs monero-blockchain-prune (prune/shrink it by doing copy)
01:45:04 <Bill48105> i'm no guru but that's my understanding of it
01:45:13 <Bill48105> souce: doing both myself
01:45:16 <Bill48105> source even
01:45:45 <Bill48105> issue with monero-blockchain-prune is if you seek pruning because you ran out of disk space already lol
01:47:10 <selsta> usually it's easier to delete the chain and resync from scratch with --prune-blockchain
01:47:27 <selsta> the separate blockchain prune tool takes ages
01:47:39 <Bill48105> that was me :D  and didn't have enough free space to prune/shrink it so i had to migrate wallet to another drive then prune
01:47:44 <Bill48105> and yes it took overnight
02:14:28 <Mochi102> use the pruning tool and it does reduce the size
02:15:02 <Mochi102> but yeah, it makes a copy, so you need a lot of space
02:15:30 <Mochi102> I pruned it locally on my windows machine and then uploaded it to my ubuntu server once pruned
02:15:47 <Mochi102> locally I run a full chain and on my server I run it pruned
02:22:31 <Mochi102> apotheon, Mochi103 might be here soon.
02:26:17 <apotheon> Mochi102: good to know; thanks for the warning
03:15:13 <Bill48105> warning whoop whoop lol
03:23:56 <narf> nipples
03:24:14 <narf> whoops wrong chan
03:24:16 <narf> lol
03:34:41 <Bill48105> sure.. wrong channel.. yeah.. uhuh.. lll
04:05:18 <pmp> Hello there. Does anyone know where I could get help with setting up a node on Gentoo? I am not sure if this is the right channel.
07:00:04 <Steven_M> one of my tx's failed to send and the wallet didn't say why?
07:01:43 <Steven_M> s/one of my tx's failed to send and the wallet didn't say why?/one of my tx's failed to send and the wallet didn't say why.
07:04:01 <Bill48105> how do you know i failed if it didn't tell you? did you check the logs
07:04:39 <Bill48105> how was it you sent (using what)
07:06:19 <badjabber> Steven_M if your local daemon failed to broadcast the tx (it never appeared on xmrchain.net mempool for example) you might be able to force it to broadcast the tx with relay_tx
07:06:27 <badjabber> https://monero.stackexchange.com/questions/6649/transaction-stuck-as-pending-in-the-gui
07:07:11 <badjabber> ^that might help for getting there from the gui.  If you are using cli for daemon then relay_tx <txid> should force it to broadcast hopefully
07:37:15 <Steven_M> badjabber: okay, thank you. :)
11:27:24 <alMalsamo> 2022-02-12 11:24:05.363 I Synced 77728/2557806 (3%, 2480078 left, 0% of total synced, estimated 8.8 days left)                                                                
11:27:45 <alMalsamo> Is this really gunna take 8.8 days, how much can I trust this output from monerod?
11:36:13 <merope> alMalsamo: might even take you longer... hope you're not using an hdd to sync, they are extremely slow at random reads (which sync uses very heavily)
11:36:33 <merope> Use an ssd for the initial sync if you can, it speeds things up massively
11:37:23 <merope> And then move the chain back to the hdd once you're done syncing and just need to keep up
11:38:11 <merope> Maybe consider enabling pruning, which reduces the stored blockchain size to almost 1/3 (50GB instead of 120GB)
11:46:29 <alMalsamo> merope: Yeah HDD unfortunately, I have a new 2TB 2.5" SSD and 1TB mSATA SSD right next to me on the desk but I haven't installed them yet
11:46:47 <alMalsamo> Also I did enable pruning with CLI switch I don't have enough space to store the full chain
16:06:45 <alMalsamo> 2022-02-12 16:04:52.668 I Synced 419680/2557947 (16%, 2138267 left, 14% of total synced, estimated 10.6 days left)                                                            
16:07:17 <alMalsamo> I went from 3% to 14% in ~5 hours, how could it be that the rest will take a full 10+ days?
16:12:16 <moneromooo> The start of the chain is light. Few txes.
16:12:39 <moneromooo> The percentage is based off height.
16:48:16 <selsta> the estimated time remaining is quite inaccurate
16:49:02 <selsta> for full chain sync at least, when only syncing a couple thousand blocks it is accurate
16:56:44 <alMalsamo> selsta: Well I have to do a full chain sync to initialize my node right, even though I enabled pruning (because it still has to download the full cahin even when pruned)?
16:57:19 <selsta> basically yes, I just meant that the estimated time remaining will be a bit inaccurate
17:00:33 <moneromooo> You can use --synced-pruned-blocks, it'll save bandwidth, but probably not time.
23:39:46 <alMalsamo> moneromooo: Hmm well I already started this process with just monerod --data-dir /mnt/monero --prune-blockchain so it is probably too late to add --synced-pruned-blocks, right?