<r4v3r23[m]1> "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

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: monero-project/monero #8076#discussion_r900408334

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 ?

(and the multisig code already has this deferring code, so you'd just need a function to go through transfer_details and calc)

Apologies if I'm missing a large problem here.

It seems much longer than it is because it also has the commits from scan_tx in its diff

Ah, I hadn't realized it was not all for this, thanks.

A quick page through wallet2 looks like it is quite plausible indeed.

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

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)

When I first implemented it, I generated the key image for those outputs and surgically updated transfer_details. That was a lot of code

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

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.

The tests are supposed to be built if you configure with BUILD_TESTS=ON.

They're probably enabled for debug, and not for release.

You said you compiled the wallet, I assume not the wallet only, but the whole tree ?

If you built just the wallet, then obviously that's why. The cmake output on configuration should tell you whether tests are enabled.

Look for "[bB]uilding tests

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

answer please

Pro Fire Official: Go to #xmrmine:matrix.org

yes sir

no one is online bro no one

Lies

Im online and youre on matrix

yeah u didnt replied

i am saying the chat room is half dead

Meet you over there in 5

We were in a meeting

yes sir

i am new bro dont be so defensive

Pro Fire Official: this is -dev , stop

<moneromooo> "You said you compiled the wallet..." <- Yes the whole tree.

<moneromooo> "The tests are supposed to be..." <- Right okay thank you for the confirmation. :)

Hello together

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: pastebin.com/5m68y2hK could you tell me where is my mistake , please ?

i get abnormal values out

Pascal123: I don't know what you're trying t do, but this may be related: monero.stackexchange.com/questions/…-and-how-explore-its-contents-using

> 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.

ok Thank you, i m just doing some educational works actually

i want to dive deeper

If you want to have a block explorer, ask for everything by RPC from monerod

It will give you JSON format

i want to read the blockchain from hard drive

reading the raw format

i implement the block structure, but if i read it i get abnormal results

If it's just experimental instead of practical, then start from that stackexchange question

hmm its more experimental

isnt it anywhere documented how to read blocks from raw file ?

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.

is the raw file binary or it is LMDB Format?

I don't know since I did the easy thing: ask monerod

ok

could i request monero daemon without syncing whole node ?

If you didn't sync the node, how do you have .bitmonero/lmdb?

i did download the raw file from monero source

<Pascal123> "i want to read the blockchain..." <- I have a rust lib for that: github.com/Boog900/monero-db-rs/tree/main

or there is a python lib however some types aren't supported: github.com/AnonimaUzanto/py-monerodb/tree/main

ok, thank you