03:10:00 "jbermanis there anyone up to the..." <- I'm gonna take another pass through it in the next days and after I do that, offer the bounty on it to people who find issues with it/review it well 03:28:54 vtnerd: fwiw there actually is a fix nestled in there that prevents duplicate txs from getting added to the daemon's in-memory pool container. It's nestled in this PR because it seemed the most sensible way to fix it: https://github.com/monero-project/monero/pull/8076#discussion_r900408334 06:12:44 8619 seems awfully large. I'd have expected it to be a LOT smaller. I think the only thing the wallet cannot do without the spend key is calculate the key image, which must be left till later, no ? 06:13:58 (and the multisig code already has this deferring code, so you'd just need a function to go through transfer_details and calc) 06:14:27 Apologies if I'm missing a large problem here. 06:22:34 It seems much longer than it is because it also has the commits from scan_tx in its diff 06:29:05 Ah, I hadn't realized it was not all for this, thanks. 06:29:34 A quick page through wallet2 looks like it is quite plausible indeed. 06:34:39 The most notable implementation detail is that when it scans a received out in this mode, it will save all subsequent txs that include that output as a ring member 06:34:55 Then when loading the spend key, it re-processes all those txs too. This way it picks up 0 change spends even if they occur while scanning in this mode (without needing to query the daemon for spent key images) 06:40:07 When I first implemented it, I generated the key image for those outputs and surgically updated transfer_details. That was a lot of code 06:42:29 After the scan_tx fix, I decided to use a similar approach as from that PR: pop the transfers from when background sync started then re-call process_new_transaction with all txs picked up by the background scanner. It's way simpler this way/less code 15:44:13 Good afternoon guys, I'm currently looking at the unit tests for the Monero when I compile the wallet source code the tests appear within the release build of Monero but not the debug build of Monero? Is this supposed to happen? Thanks. 15:50:08 The tests are supposed to be built if you configure with BUILD_TESTS=ON. 15:50:28 They're probably enabled for debug, and not for release. 15:51:03 You said you compiled the wallet, I assume not the wallet only, but the whole tree ? 15:51:43 If you built just the wallet, then obviously that's why. The cmake output on configuration should tell you whether tests are enabled. 15:52:15 Look for "[bB]uilding tests 15:53:03 yo look guys i have setup my whole thing and i want to start mining i am not able to do that i have tried everything so please tell me something 15:54:12 answer please 15:56:50 Pro Fire Official: Go to #xmrmine:matrix.org 15:58:12 yes sir 15:58:45 no one is online bro no one 16:02:13 Lies 16:02:30 Im online and youre on matrix 16:03:05 yeah u didnt replied 16:03:05 i am saying the chat room is half dead 16:03:07 Meet you over there in 5 16:03:17 We were in a meeting 16:03:18 yes sir 16:03:58 i am new bro dont be so defensive 16:04:20 Pro Fire Official: this is -dev , stop 16:04:44 "You said you compiled the wallet..." <- Yes the whole tree. 16:06:27 "The tests are supposed to be..." <- Right okay thank you for the confirmation. :) 22:22:18 Hello together 22:23:35 i want to write a very simple blockchain explorer, but i m sure im doing something wrong..i got the blockchain of monero in raw format and read the blocks like this: https://pastebin.com/5m68y2hK could you tell me where is my mistake , please ? 22:24:08 i get abnormal values out 22:52:13 Pascal123: I don't know what you're trying t do, but this may be related: https://monero.stackexchange.com/questions/10919/understanding-the-structure-of-moneros-lmdb-and-how-explore-its-contents-using 22:52:33 > The C/C++ objects are written to the database. For this reason, even if you used a higher level language (e.g. Python or Javascript for example) LMDB wrapper, you are still going to need to convert that data to objects in your other language. For this reason, if you are going to directly query the database, you will almost certainly want to use C/C++, the native LMDB library and make use of the definitions in cryptonote_basic.h. 22:53:25 ok Thank you, i m just doing some educational works actually 22:53:35 i want to dive deeper 22:54:22 If you want to have a block explorer, ask for everything by RPC from monerod 22:54:36 It will give you JSON format 22:54:51 i want to read the blockchain from hard drive 22:55:06 reading the raw format 22:55:53 i implement the block structure, but if i read it i get abnormal results 22:56:14 If it's just experimental instead of practical, then start from that stackexchange question 22:56:40 hmm its more experimental 22:57:27 isnt it anywhere documented how to read blocks from raw file ? 22:57:39 Trying to read the raw data from the LMDB is going to be about ten times harder, or more, than just asking monerod to do the work for you. 22:58:09 is the raw file binary or it is LMDB Format? 22:58:44 I don't know since I did the easy thing: ask monerod 22:58:52 ok 22:59:37 could i request monero daemon without syncing whole node ? 23:00:49 If you didn't sync the node, how do you have .bitmonero/lmdb? 23:01:11 i did download the raw file from monero source 23:02:00 "i want to read the blockchain..." <- I have a rust lib for that: https://github.com/Boog900/monero-db-rs/tree/main 23:02:00 or there is a python lib however some types aren't supported: https://github.com/AnonimaUzanto/py-monerodb/tree/main 23:02:25 ok, thank you