04:33:51 my 04:36:43 bah. my thoughts started to drift towards PoW and blockchain for this as well. Like, if your metapeer node somehow runs minimal versions of participating nodes, the subnetwork nodes could publish hashes of peerlists in their blocks, so the metapeer could use the same nakamoto consensus approach 04:37:31 you'd really just need minimal code to check PoW and header consensus i think 04:37:45 none of all the transactional stuff 04:39:22 of course, this ... shifts... the centralization to the block producers, but thats de-facto acceptable. or de-.... something 04:45:27 of course, nefarious block producers could publish bogus peer lists, but these lists would then be countered by the next block, which presumably is by a different block producer 04:46:37 and if the metapeer's peer list uses the same sort of peer list functions as existing peer lists (moving from white to grey to eviction etc), then a metapeers old peers wouldn't get kicked off its list by just nefarious block 04:48:20 though this doesn't solve the issue for a non-blockchain based network - i.e., how could we rope in bittorent network or tor or i2p etc 04:53:46 though members of a blockchain network that also run non-blockchain network nodes could advertise all of their services available 16:12:57 hello everyone 16:13:08 When I do a sweep_single transaction, the incoming tx when refreshing shows "NOTE: this transaction uses an encrypted payment ID: consider using subaddresses instead". I thought payment ids were completly dropped. Should I be worried? 16:13:36 No, it seems to trigger for change with the default placeholder. It's fine. 16:14:18 awesome, got really worried that it would make my tx different from others 16:14:23 thank you for the quick reply 17:40:02 I’m getting a compile error in my application, “no type named ‘chacha_key’ in namespace ‘crypto’“, even though it includes wallet2.h which has #include “crypto/chacha.h”. Adding to CMakeLists include_directories(“src/crypto”) and #include “chacha.h” in my application source resolves the error. The error appeared without any code changes so it could be related to my environment. Any 17:40:02 idea what could cause it?