02:37:08 https://www.themoneromoon.com/p/the-monero-moon-issue-65 04:57:06 Hello, I required some help 04:57:22 I want to export my pruned monero db to my server, but you cant use blockchain=prune 04:57:50 i sent the .mdb file, and i presume its configured for my computer and not the server, so it cant be imported 04:58:58 ``` 04:58:59 2024-05-01 04:54:55.862 I Loading blockchain from folder /home/retkid/.bitmonero/lmdb ... 04:58:59 2024-05-01 04:54:55.862 D option: fast 04:59:00 2024-05-01 04:54:55.862 D option: async 04:59:00 2024-05-01 04:54:55.862 D option: 250000000bytes 04:59:01 2024-05-01 04:54:55.862 T BlockchainLMDB::open 04:59:01 2024-05-01 04:54:55.863 T BlockchainLMDB::need_resize 04:59:02 2024-05-01 04:54:55.863 D DB map size: 87732275200 04:59:02 2024-05-01 04:54:55.863 D Space used: 76084457472 04:59:03 2024-05-01 04:54:55.863 D Space remaining: 11647817728 04:59:03 2024-05-01 04:54:55.863 D Size threshold: 0 04:59:04 2024-05-01 04:54:55.863 D Percent used: 86.7235 Percent threshold: 90.0000 04:59:04 2024-05-01 04:54:55.863 D Setting m_height to: 3137649 04:59:05 2024-05-01 04:54:55.864 T mdb_txn_safe: destructor 04:59:05 2024-05-01 04:54:55.864 T Blockchain::init 04:59:06 2024-05-01 04:54:55.864 T BlockchainLMDB::height 04:59:06 2024-05-01 04:54:55.864 T BlockchainLMDB::block_rtxn_start 04:59:07 2024-05-01 04:54:55.864 T mdb_txn_safe: destructor 05:45:01 albassort: Normally the data.mdb file is compatible across different operating systems 05:58:06 dEBRUYNE i assume rsync is corrupting across the 70 gb. I am now syncing it with syncthing 05:58:45 Did you leave the Monero software running? That may have caused a corruption 06:05:02 No, I don't think so. 06:05:14 I tried 2 separate times with full transfers 06:05:25 syncthing was probably the right tool for it, anyway 06:19:30 <321bob321:monero.social> is the db getting witten too? 07:15:21 .xmr 07:15:22 norman: You must have bot account & be logged in 07:17:39 whats up? 07:30:30 https://www.justice.gov/opa/pr/early-bitcoin-investor-charged-tax-fraud 07:59:55 #shum 09:58:27 Hi there, can you PM me how to start using it ? 12:22:05 <5m5z3q888q5prxkg:chat.lightnovel-dungeon.de> good, well deserved for using BTC 12:22:16 * m-relay <5m5z3q888q5prxkg:chat.lightnovel-dungeon.de> grins 16:53:17 A little tip for all Linux users who mine Monero on their work PC and don't want to be disturbed by the mining process. Use »nice -n 19 ./xmrig«. This sets xmrig to the lowest priority in the process scheduler. The higher the number, the nicer the process: -20 = not nice to 19 very nice. See also »man nice«. 16:55:03 Can also use less nice but tell xmrig to not use all cores 16:57:15 ^⁻ This could also be useful to prevent the CPU from overheating. 16:58:11 You don't necessarily have the best coolers on a normal PC. 17:01:58 xmrig --cpu-priority=N does not work als good. I wonder why? 17:06:34 I often switched off xmrig because it just got on my nerves when I wanted to do something on the PC. Compiling something etc. That is now history. 17:08:08 It now behaves like a submissive slave in the background. 19:04:11 This is the real way. 19:04:42 I find it more responsive that way, when you use the computer in the same time 19:13:26 Why not both at the same time? Fewer cores and a high nice value? 19:24:09 kayabanerve: I just listened to your Twitter Space! Great Insides! 19:24:11 I got a very happy takeaway. Am I right with this? 19:24:13 The 10 block lock time wouldn't be an issue anymore, because a wallet can easily create pocket change, so you can make multiple spends without waiting time! 19:24:15 And the locktime isn't an issue for merchants who are willing to take the risk of unconfirmed transactions, which means Monero can offer an instant transaction user experience just like Bitcoin Cash. 19:59:39 Is there a rule that decoy inputs are never selected if they spawn from the same transaction? 20:09:31 erembax: No, there is no rule like that. I assume you cannot see this message soon since you are on the matrix.org home server. 20:12:52 rucknium: Speaking of not seeing messages, I have given up on element. FYI if you are including node count in any of your work I would not rely on the number shown at monero.fail/map 20:14:57 Do you think it is too high? I do, too. But if we include it in the cost effectiveness measure, then we are just overestimating the node storage costs. My analysis so far already says that increasing the ring size (which increases storage costs) is more cost effective than increasing the fee/byte. 20:15:00 Many of the shown nodes are 'last seen 8 months ago.' I believe their records are not correct, or not updating. 20:15:21 The other tool I am aware of that shows this is tools.rino.io/network/ 20:15:36 which shows something like 1.5-2k nodes. 20:17:32 My memory is a little fuzzy, but IIRC that map does not actively crawl the network. 20:18:16 I could try to run https://github.com/endorxmr/monero-node-p2p-scanner to get a firsthand count. AFAIK that code <--- is similar to what monero.fail uses. 20:20:41 I am not sure if rino is correct, but the numbers do change on a daily basis. I think monero.fail has been stuck at 22537 for quite some time. 20:21:40 Rino's is probably just a list of known peers from...that command that gets the list of peers 20:24:36 <321bob321:monero.social> This is why there needs a health check endpoint -.- 21:16:48 Pocket change isn't a complete non-issue (output quantity technically still is a fingerprint) yet it wouldn't be the issue it is today. The question is no longer about fingerprints within a graph subset yet rather the entire chain, and you can't trace intermediary TXs (between pocket changes). 21:17:37 I would not say that makes the 10-block lock a non-issue nor claim Monero instant nor claim BCH instant Tigerix: 23:10:10 hello so, I did a manual transfer in parts and the checksum is identical to the version that works on my pc 23:10:22 context: im trying to send the .mdb from my pc to my server for a node 23:10:27 i cant export it due to it being pruned 23:10:45 with this error: 23:10:46 2024-05-01 23:08:49.283 E Failed to parse block from blob