01:57:09 > <@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: 01:57:09 > https://github.com/monero-project/research-lab/issues/92 01:57:09 > https://gist.github.com/tevador/50160d160d24cfc6c52ae02eb3d17024 01:57:09 Thank you. The exchange I work for plans to list Monero soon so I don't think the new address form matches the schedule. 03:54:29 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. 03:55:07 Advantages - verifies EXEs are authentic, bypass SmartScreen 03:58:28 Sectigo is aka Comodo 03:58:50 Can get DigiCert too but they're a lot more expensive 04:00:30 * asheroto[m] uploaded an image: (52KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/FdBVfdWBKMgbjWwkjBMCpmeg/image.png > 04:01:25 also gets rid of the "unknown publisher" 04:01:54 * asheroto[m] uploaded an image: (98KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/FyQUwDeoPOcGUZBherVIliLK/image.png > 04:06:26 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./ 04:12:42 willyijinin[m]: seraphis is still a long way away, 1yr+ I’d guess 07:47:17 Hello, where in the Monero repo can I find information about encoding and decoding the unsignedTxHex as in... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8a129cfe8ea8ae03160420cd076b65caedf88770) 08:23:13 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. 08:49:38 `t_serializable_object_to_blob` this? c++ is a bit confusing for me because you can implement the method everywhere. moneromooo 08:50:22 git grep t_serializable_object_to_blob 08:50:34 this one is likely in cryptonote_format_utils 08:53:23 * willyijinin[m] sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/e39178a86c36da43261f81bc58f2508ec684c716 08:55:55 how do I find the exact logic for `::serialization::serialize` which I suppose is the encoding of the transaction object into unsignedTxhash? 08:59:57 moneromooo: BTW does the repo have a method to unserialize the unsignedTxHex? 09:02:57 The opposite of t_serializable_object_to_blob. See parse_and_validate_block for an example. 09:03:26 serialize is in src/serialization, it's a bit hard to follow (C++). 09:13:40 moneromooo: Sorry to bother you again. But mymonero is not open sourced. In `create_transactions_2` there is:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/217ab8df0924130e2664a0fb700a6cd4e591c477) 09:26:45 moneromooo: In other words, the offline wallet export this array to a view-only wallet.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/0f26cdb61d33bcca18eb600435a4d2403871d111) 09:29:50 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 09:29:50 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?/ 09:35:01 "will.yijinin: seraphis is..." <- Implementation or on paper 10:04:58 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. 10:06:11 What do you call "hex" ? I've been kinda assuming you mean "pubkey". 10:06:42 A wallet can determine whether a key image is spent in two ways: 10:07:02 - seeing it used in a ring in a block on the current main chain 10:07:10 (ie, while scanning new blocks) 10:07:22 - asking the daemon via the is_key_image_spent RPC. 10:08:44 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. 10:09:10 A full wallet can calculate it on the fly (see process_new_transaction in wallet2.cpp)