01:09:23 yanmaani, ok, so basically you would just have to run a bittorent node so you can populate the dht with your information that contains the monero p2p info 01:10:11 gingeropolous: Yes, but those are very easy to implement and there's libraries for them 01:10:30 It's about on the same level of complexity as a HTTP client 01:11:05 and theoretically, as soon as you are operating a bittorent node with monero p2p information, the entire bittorent network now has that monero p2p info 01:11:12 because of the dht magic 01:11:24 ? 01:14:53 yanmaani, is that how it works? 01:21:19 gingeropolous: don't really understand 01:21:31 if you have a connection to 1 node in the DHT network, it means you can find any other node in there 01:21:49 for a given key, this maps to a specific cluster of nodes, basically 01:23:55 gingeropolous: https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf 01:24:50 gingeropolous: when's the last time you seen fluffypony? 01:25:04 I swear it's easier to get an audience with the Queen 01:27:02 as for the details on how bittorent DHT works, check out https://www.bittorrent.org/beps/bep_0005.html (spec) and https://github.com/jech/dht (an implementation, ~3kloc) 02:33:13 thanks yanmaani . im always at a suboptimal level of understanding some things 02:34:38 Wolf0, a while if i reckon 04:04:41 gingeropolous: I'm looking for him 04:04:42 Hi all :-) 04:04:52 hey 06:28:52 <***> Buffer Playback... 06:28:52 [04:15:21] yes 06:28:52 [04:53:22] lza_menace: Sorry, got held up. When I churn, I always send my XMR to new wallets, but does churning work when you send the XMR back to the same wallet? 06:28:52 [04:53:43] yes 06:28:52 [04:55:27] how many churns per real transaction, should I make? 06:28:52 [04:58:20] idk, up to you. i don't churn at all 06:28:52 [04:58:58] i'll occassionally consolidate and move funds to new wallets so i don't maintain ancient wallets with old restore blocks 06:28:52 [05:12:08] lza_menace: okay, thanks for the info! :-) 06:28:52 <***> Playback Complete. 19:39:58 <***> Buffer Playback... 19:39:58 [11:47:33] and we all know the power of defaults! 19:39:58 [11:47:50] seems excessive. if DHT works why do we need DNS? 19:39:58 [11:48:23] or do you expect that some networks will be filtered/blocked so only DNS can be relied on? 19:39:58 [11:52:36] fwiw I like the idea of DHT and getting rid of libunbound from our build 19:39:58 [11:52:49] it has caused more than its fair share of bugs 19:39:58 [11:53:38] but there are trust questions to resolve. we use DNS to announce software updates now 19:39:58 [11:54:06] seems like we still need some centralized trust to handle these things 19:39:58 [12:01:34] i was just suggesting that option to not radically change what has worked 19:39:58 [12:01:46] phase-in, as it were. but sure. 19:39:58 [12:02:15] or perhaps its the first in line, and dns moves to #2 with hardcoded at #3 19:39:58 [12:04:42] re: dns as update announcements, that seems to be a different problem / mechanism 19:39:58 [12:09:38] hyc: You can use DHT with signed keys 19:39:58 [12:09:43] I don't know how well-supported it is 19:39:58 [12:09:46] But why not flood? 19:39:58 [12:10:07] Have a protocol message new_version, sign that with some key, gossip it over the network 19:39:58 [12:10:13] (like bitcoin's alert key) 19:39:58 [15:56:26] luigi1111: do you have permission to add ops over any #monero- channel? I'm trying to set up #monero-space which isn't registered and has no ops as far as I can tlel 19:39:58 [16:11:11] I think fluffy is the only one atm 19:39:58 [16:25:00] okay ty 19:39:58 [16:25:50] So centralized... 19:39:58 [16:25:52] ;) 19:39:58 [16:26:59] If anyone isn't busy I still would like an invite for the #Monero Matrix room if possible 19:39:58 <***> Playback Complete.