02:11:46 Noice 03:46:23 nioc right there with ya buddy 03:54:15 If anyone is interested in taking over either Bitejo Marketplace, Kuno Fundraisers or Vendo Digital Downloads, here is a Matrix room: #bitejo-dev:halogen.city 06:01:25 Gross 08:34:06 "Want the alpha build? I can send..." <- Thank you, I will wait till it's is live. Quite busy these days. 09:26:58 When does the restriction of bloat_extra version released to stable? 10:44:33 Hello, Is this the new/old room? 10:44:37 this is the currently active room 14:32:40 Sync on a USB spinner w. 1G net: Synced 111 blocks in 5.6 minutes (0.328 blocks per second) 🤢 14:34:32 TrasherDK[m]: is this the same node where you had corruption issues? 14:35:34 No, I rsync'ed from that one, to a probable replacement server. 14:36:10 The old server did: Synced 92 blocks in 1.2 minutes (1.277 blocks per second) 14:38:29 the numbers can be deceiving, some blocks are empty , some are full 14:39:39 if i was you i would let it run for about 1 year then see how its going 14:40:58 Well, it's the same lmdb files, syncing the same blocks. Old server has 200GB SSD vs 1TB external spinner, on the new. 14:41:13 whats teh tldr on mordinals and their effect on monero 14:42:21 tldr: undesireable bloat for the blockchain size 14:42:22 i know next release should limit them in some way 14:42:35 k4r4b3y[m]: yeah but how does it affect transactional provacy 14:42:39 s/provacy/privacy/ 14:43:41 r4v3r23: I will probably do a write-up next week on the empirical privacy effects of Mordinals 14:44:18 As in, how do Mordinals affect effective ring size. 14:44:57 Rucknium appreciate it 14:45:49 Rucknium[m]: looking forward to it 14:45:51 I will combine it with the P2Pool coinbase output analysis. P2Pool payouts got more efficient just before Mordinals started appearing. That's a fortunate coinicidence. 14:49:26 Here is data on the share of outputs generated by Mordinals and coinbase transactions: https://gist.github.com/Rucknium/67cc9efdf7e43a40c52417611b322d43 14:50:46 It's not simple to translate these numbers into effective ring size since decoys are sampled from long time intervals. 14:50:53 But the writeup will have the "translation" 14:54:53 Thanks! 14:55:23 Also nice to see that the morbinal update to pumpup the fees did neutralize a big part of the problem 17:09:44 jeffro256: so in the -cli for key images, im doing "incoming_transfers available verbose" then i see the key images at the end which i can "freeze" (it appears as [locked] then it you repeat the same command) 17:10:33 [frozen] rather 17:15:17 jeffro256: freezing to make sure i use a coinbase output. in this tx i did just that with your pull request, and i see "only coinbase being used" https://stagenet.xmrchain.net/tx/e075bf7e3ec463e05a9852cc5f7e6ac9e1b3298965533c04747a557b17abec57/1 17:16:00 a non-coinbase output transaction using no coinbase decoys also https://stagenet.xmrchain.net/tx/8f2f23db442e93e866adac7788645bb330e56a439ee10f5ec048c38d3222a00c/1 18:58:05 "r4v3r23: I will probably do a..." <- Appreciate that homie 19:34:20 "jeffro256: freezing to make sure..." <- Yay! Could you find any issues with it ? 19:47:52 only used it a few times, e.g. the sweep_all went well https://stagenet.xmrchain.net/tx/851ef2ad3a13c0c125779cf107dc38155f56978f62b3ffa81b78230d1a69dbe9/1 19:48:52 Rucknium: wants 100,000 tx's on mainnet not broadcast for analysis 🙈 19:57:31 Interesting my node was on 18.1.2. 19:58:05 Bad node operator :/ 21:50:19 looking to run monerod exclusively over tor. If I set p2p-bind-port=18083 which the hidden service runs on, it fails to initialize the p2p server. what am I missing here?