07:57:36 <selsta> moneromooo: there is still a second commit in 6574 which looks unintended
10:43:57 <philogy> where can I find the spec to how Monero transactions or blocks are encoded?
10:49:41 <asymptotically> https://cryptonote.org/standards/ - out of date but still worth reading
10:49:49 <asymptotically> i think you need to read the source to get up to date
10:50:28 <philogy> I'm not too familiar with the code base, in what directory/files can I find where the serialization is done?
10:53:35 <asymptotically> in some of the files (like https://github.com/monero-project/monero/blob/master/src/cryptonote_basic/cryptonote_basic.h ) you can see the fields in different structs, and there's a library in there somewhere called serialization that actually turns it into bytes
10:54:19 <asymptotically> i wrote a java library for parsing them, it might be slightly easier to read but not the best reference since it's missing some things (ringct stuff i think) https://github.com/00-matt/monerocore/tree/master/src/main/java/uk/offtopica/monerocore/codec
12:08:56 <moneromooo> selsta: looks ok to me, refresh ?
12:09:36 <moneromooo> There is one which fixes a scale, if you mean that one. Guess it can go in its own PR if you prefer.
12:10:02 <selsta> you PRed it separately already
12:10:41 <selsta> 6611
12:11:27 <selsta> or maybe it is slightly differenr
12:11:33 <selsta> and it looked only similar lol
12:13:39 <selsta> no seems to be the same
12:13:54 <moneromooo> Oh nice. I'll remove the second commit then.
12:37:34 <philogy> what are the ~800bytes for in between the bulletproof and mlsag signature?
12:37:52 <philogy> asymptotically: btw thanks, your code helped me figure out the varint encoding
12:48:31 <philogy> nvm ik what the 800bytes are for
13:23:02 <binaryFate> If anyone is using xmr.to API or is maintaining a wrapper: the current version has been bumped to version 3. (Version 2 still supported for now). Follow this guide to migrate, should be easy: https://xmrto-api.readthedocs.io/en/latest/api_v3_migration.html