00:14:59 br-m: Okay, good to know. I'm wondering if a feature could be added to create like a new torrent each month that is created from a checkpoint in the blockchain file? That way a new node just downloads the torrent plus the changes over the last month. 02:14:23 Ryushin: That….isn’t the worst idea 02:14:23 To make sure that the torrent is a correct history though, the hash of it would need to be carried and transmitted by the nodes that are already synced up 02:55:58 br-m: That is what I was thinking. It would be like an official torrent that only the pre-existing complete nodes would have. It would save a lot of wear and tear on storage devices. 06:42:42 Anyone knows what he is mentioning about Monero? https://xcancel.com/zachxbt/status/1980612190609576229?s=46 06:52:13 Ryushin: usually syncing from scratch nowadays is faster than importing a blockchain dump 06:52:21 they use different processes afaik 07:05:29 <321bob321> @hbs:matrix.org: UI/UX complaints apparently 07:09:41 @321bob321: Yes but in what context or tool? Doesn't seem clear. 07:10:46 <321bob321> Wallet ? 07:54:51 Zashi is a mobile wallet, so I assume ZachXBT is referring to UX issues with a mobile Monero wallet. 11:39:02 privacy as a service 12:34:21 DataHoarder: The actualy process of syncing is very IO intensive with an incredible amount of write amplification. The blockchain is currently 276GB. But in the process of syncing it will write several terabytes. I originally put the blockchain on a ZFS dataset on 30 drive HDD pool, then to a 6 drive SSD pool, and once I realized I was dealing with a huge mount of write amplification due to 15 minutes snapshots growing at an astounding rate, 12:34:21 I stuck it on a RAM drive and let it finish. After it was done I moved it back to the 30 drive HDD pool. 12:38:36 My main idea was creating monthly checkpoints of the block chain that acts as a bootstrap for new nodes, every from the beginning of the blockchain to the checkpoint is transferred like a bittorrent, then once the torrent piece is transferred, it does a catch up sync for up to a month of data. The only heavy IO is done just for that last catch up. 12:42:18 You mean db dumps and not raw exports 12:42:29 Raw esports get checked db dumps not really 12:43:30 So you switch verifying blocks with trusting torrent maker, unless the structure of it can be deterministic ally made, then at least just need to trust the people who made these dumps and verified the result 12:43:38 Raw exports* 12:52:44 Well the nodes also act as a torrent. Sharing the beginning of the block chain to the monthly checkpoint, then that giant chunk is bootstrapped as a torrent, then a final sync once it completes downloading. 13:03:23 Yay! I mined my first XMR this morning. 13:16:19 Ryushin: and how do people know if this data is legit? 13:16:29 The nodes could be colluding to tell you it's legit 13:19:39 Perhaps the official Monero site can have a SHA2 for the checkpoint, if it matches then it can continue. The official torrent bootstrap ile can come from the Monero site as well that the official wallet client uses. 13:23:32 I'm just trying to think of a way to bootstrap the file while having a distributed transfer. 13:29:20 so then you are indeed trusting the downloads are legit 13:30:19 Ryushin: having a boostrap'd file that gets imported more or less works, though a light version would be to verify the block headers, then assume txs are legit, which is the expensive part, then check this vs network 13:30:24 but the clients could end up isolated on their own little island 13:30:57 however, that's sort of the embedded checkpoints for releases