> <@rucknium:monero.social> will.yijinin: We were just talking about these issues in #monero-research-lab:matrix.org . You should let us know if any of these address schemes could make your life easier as a merchant/user:

> monero-project/research-lab #92

> gist.github.com/tevador/50160d160d24cfc6c52ae02eb3d17024

Thank you. The exchange I work for plans to list Monero soon so I don't think the new address form matches the schedule.

Monero Devs - is the team interested in a code signing certificate for the Windows EXEs? If so, I'm happy to get you hooked up with one at cost. My company has a partnership with Sectigo and thus can get them cheap.

Advantages - verifies EXEs are authentic, bypass SmartScreen

Sectigo is aka Comodo

Can get DigiCert too but they're a lot more expensive

also gets rid of the "unknown publisher"

s/Advantages - verifies EXEs are authentic, bypass SmartScreen/Advantages - verifies EXEs are authentic, shows Monero as the publisher, gets rid of unknown publisher, and instant reputation with SmartScreen if you get an EV certificate./

willyijinin[m]: seraphis is still a long way away, 1yr+ I’d guess

Hello, where in the Monero repo can I find information about encoding and decoding the unsignedTxHex as in... (full message at libera.ems.host/_matrix/media/r0/do…cfe8ea8ae03160420cd076b65caedf88770)

src/wallet/wallet2.cpp, the structures are in src/wallet/wallet2.h, it uses serialization in... somewhere... I think I changed it to use src/serialization like a year ago but I'm not positive.

`t_serializable_object_to_blob` this? c++ is a bit confusing for me because you can implement the method everywhere. moneromooo

git grep t_serializable_object_to_blob

this one is likely in cryptonote_format_utils

how do I find the exact logic for `::serialization::serialize` which I suppose is the encoding of the transaction object into unsignedTxhash?

moneromooo: BTW does the repo have a method to unserialize the unsignedTxHex?

The opposite of t_serializable_object_to_blob. See parse_and_validate_block for an example.

serialize is in src/serialization, it's a bit hard to follow (C++).

moneromooo: Sorry to bother you again. But mymonero is not open sourced. In `create_transactions_2` there is:... (full message at libera.ems.host/_matrix/media/r0/do…8df0924130e2664a0fb700a6cd4e591c477)

moneromooo: In other words, the offline wallet export this array to a view-only wallet.... (full message at libera.ems.host/_matrix/media/r0/do…db61d33bcca18eb600435a4d2403871d111)

s///, s/which does not has output hex in each array element. I understand the view-only wallet search the blockchain for existing keyImages. But after the search, the view-only wallet has an array of keyImages. How does it know which of the outputs hex are unspent?/which does not has output hex in each array element. I understand the view-only wallet checks if any of the above keyImages exists on the blockchain. After the check, the

view-only wallet has an array of keyImages left which I suppose represent the utxos. But how does the view-wallet connect the KeyImages with the utxos?/

<UkoeHB> "will.yijinin: seraphis is..." <- Implementation or on paper

The light wallet stuff in wallet2 is probably out of date and broken. It got added long ago and I don't think anyone maintained it as things changed.

What do you call "hex" ? I've been kinda assuming you mean "pubkey".

A wallet can determine whether a key image is spent in two ways:

- seeing it used in a ring in a block on the current main chain

(ie, while scanning new blocks)

- asking the daemon via the is_key_image_spent RPC.

The view wallet connects an output with a key image by exporting the output to the cold wallet, and importing the key image it sends back.

A full wallet can calculate it on the fly (see process_new_transaction in wallet2.cpp)