<h​bs:matrix.org> Retroactive funding proposals should have a more detailed breakdown of time spent on various tasks rather than a simple amount, otherwise we risk having endless discussions as happened over reimbursements for MK

hbs: you should post that on the gitlab issue

<h​bs:matrix.org> done

<k​ayabanerve:matrix.org> hbs: Responded my hourly estimate, given a lack of an exact log, and uncertainty on if you want it per task (which would require post-building a log from commits and itself take several hours).

kayabanerve: the question i did have was whether $100 an hour was the going rate for a SotA ZK research post within industry. My calculations are that equates to $192k a year.

I am no expert in the ZK labour market though, to be honest.

<k​ayabanerve:matrix.org> Oh. No.

<k​ayabanerve:matrix.org> 350-600k would be

<k​ayabanerve:matrix.org> I've been invited to interview, saying they'd love to have me, at a 500k position specifically.

<k​ayabanerve:matrix.org> So I can confirm this would not be the going rate. Please let me know if you believe it proper to update to the going rate ;)

<k​ayabanerve:matrix.org> Off hand, I also believe Cypher Stack's going rate is decently higher as well, though I'd have to check their exact quotes given in CCSs prior and current

<k​ayabanerve:matrix.org> plowsof: Did you get an hour count by CS for their BP++ review?

<k​ayabanerve:matrix.org> I don't want to hassle them for an hour count, I couldn't care for the things, yet it would be a comparison point here if we have them.

<j​effro256:monero.social> @hbs I don't mind setting the precedent for retroactive funding for groundbreaking research. In fact, if this incentives more solo research to build things which were not before known possible, I'd be positively thrilled

<j​effro256:monero.social> Sender-privacy cannot theoretically get better than FCMPs. The fact that Luke synthesized research from numerous sources proving that we can move to trustless FCMPs using already established crypto (BPs) is an immense feat

<j​effro256:monero.social> @hbs I completely understand your hesitations, but this event should be an exception if ever there was an exception

<d​olores.sabaneta:matrix.org> Hello, I found the courage to start trying to understand the monero source. I'm using the header files and the static libraries provided after building the monero source to do my own little programs and learn, but I would definitely appreciate some help. So as I understand wallet/wallet2.h and crypto/crypto.h is where the magic happens.(I am really not understanding any of the cry<clipped message>

<d​olores.sabaneta:matrix.org> ptography yet) As I understand a tx has a tx_id which is a hash of the entire thing, it has 16 inputs that are represented by a 256 bit public key, a key image that is created from the 16 inputs and it also has at least 2 outputs. I have a mnemonic seed, and I used the bytes_to_words() from mnemonic/electrum-words.h to convert it into a secret_key. Now this is where I would need s<clipped message>

<d​olores.sabaneta:matrix.org> ome help, what function from what file do I need to use to check if a certain tx was created by my secret_key ? I imagine that I need to "scan" the inputs present in the transaction to see if one was spendable using my secret_key, but I can't seem to find the function. Am i using the term "secret_key" correctly ? because each output also has a key pair derived from the "master key<clipped message>

<d​olores.sabaneta:matrix.org> " ?

You cannot, as such, check whether a tx was created with a given secret key. If you mean checking whether a tx was created to a given public key, start with process_new_transaction in wallet2.cpp.

<j​effro256:monero.social> Couldn't you theoretically ask "did I spend this tx" by looking each input ring, then looking up the tx where each ring member was created, try incoming balance recovery to applicable tx outputs, calculating key images, then checking whether the key images in the original tx match?

<j​effro256:monero.social> AFAIK there's not a function specifically to do this

<d​olores.sabaneta:matrix.org> This is very overwealming. How does my cake wallet know what transactions belong to me ? I only give cake a seed and it gives me an history of what transactions I did.

<j​effro256:monero.social> Maybe in `wallet2::scan_tx`, actually there's some logic that does this

<j​effro256:monero.social> It knows it if was sent to you by scanning every single output on-chain, doing Diffie-Helman with the transaction public key, and recomputing the transaction output public key

<j​effro256:monero.social> The wallet knows that you sent a transaction if it sees your key images in an input ring on-chain

<j​effro256:monero.social> But to know the key images, you have to scan the transaction outputs before that transaction

<d​olores.sabaneta:matrix.org> This is very helpful thank you, it is also a lot to take in.

<j​effro256:monero.social> Have you read "Zero to Monero"?

<d​olores.sabaneta:matrix.org> Yes of course

<d​olores.sabaneta:matrix.org> Can't say I fully understand it though

<j​effro256:monero.social> Yeah it's a lot to take it at first, and the terminology is pretty confusing at times

<j​effro256:monero.social> The way `wallet2` normally knows that you spent a transaction is matching the key images in on-chain tx inputs against a stored list of key images for the outputs it has earlier received

<j​effro256:monero.social> It's always great when more people decide to look at the source code though, so don't be discouraged

<d​olores.sabaneta:matrix.org> I don't have the blockchain on my machine and would've liked if there was a function that directly took in a key image. I think my best chance is to download the blockchain and learn how to use the wallet2 class.

<j​effro256:monero.social> The key image doesn't prove to yourself that you sent the transaction, though. It just proves that a unique signer has signer this particular ring signature. It's only because the list of key images that `wallet2` stores was previously verified to have belong to owned transaction outputs that you can use this trick

<d​olores.sabaneta:matrix.org> To create a wallet using the seed I imagine I first need need to use the words_to_byte() function to get the secret_key and then use the wallet2 function called generate to restore a wallet using this secret_key ?

<j​effro256:monero.social> Yes

<d​olores.sabaneta:matrix.org> Thank you very much !

<j​effro256:monero.social> Ofc

<w​oodser:monero.social> > <s​elsta> testing of release-v0.18 would be appreciated since we will tag a new release soon

<w​oodser:monero.social> the release-v0.18 branch is passing my tests, except the fixes needed from: monero-project/monero #8938 (was hoping that was going to make it in)

woodser. it misses an approval but will try to get it in