16:33:42 <jeffro256[m]> .merges
16:33:42 -xmr-pr- 8572 8575 8602 8603 8604 8610 8611 8615 8616 8618 8627 8628 8635 8636 8642
21:42:52 <MajesticBank> not sure is it good channel, did monero had like whole codebase audit recently?
21:43:16 <MajesticBank> I imagine a lot of parties would be interested to donate to this cause
21:43:30 <MajesticBank> myself included
21:45:52 <jeffro256[m]> AFAIK, Monero has never done a whole codebase audit because that would be nearly impossible IMO
21:46:58 <jeffro256[m]> There's ~319,000 lines of code in both the contrib/ and src/ directories
21:47:49 <jeffro256[m]> Usually audits happen on specific, very critical portions of the code so that the audit is manageable and the most resources go towards making sure the core is correct 
21:50:03 <nikg83[m]> <MajesticBank> "myself included" <- You can start with hackathons and submit findings to devs 
21:58:20 <NorrinRadd> There should be some bounties for refactoring / organization 
22:04:40 <mrnaif> Hi! How to parse payment id out of tx extra data?
22:04:40 <mrnaif> I am using the code from this python lib: https://github.com/monero-ecosystem/monero-python/blob/master/monero/transaction/extra.py
22:04:40 <mrnaif> Is it pubkeys or maybe nonce by any chance, or should I write custom parsing code?
22:06:31 <selsta> https://monero.stackexchange.com/questions/1381/how-are-the-various-tx-extra-types-formats-used
22:06:34 <selsta> does this help?
22:08:59 <hyc> I thought payment ids are extinct
22:12:01 <selsta> encrypted ones are still alive
22:15:22 <mrnaif> Ah, so nonce is encrypted payment id most likely. And how to decrypt it?
22:26:28 <selsta> I assume payment-id support is built in to the library
22:28:04 <selsta> https://github.com/monero-ecosystem/monero-python/blob/master/tests/test_wallet.py
22:28:19 <selsta> line 156 for example
22:30:02 <selsta> or maybe I don't fully understand what you are trying to do