moneromooo: there is still a second commit in 6574 which looks unintended

where can I find the spec to how Monero transactions or blocks are encoded?

cryptonote.org/standards - out of date but still worth reading

i think you need to read the source to get up to date

I'm not too familiar with the code base, in what directory/files can I find where the serialization is done?

in some of the files (like github.com/monero-project/monero/bl…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

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) github.com/00-matt/monerocore/tree/…/java/uk/offtopica/monerocore/codec

selsta: looks ok to me, refresh ?

There is one which fixes a scale, if you mean that one. Guess it can go in its own PR if you prefer.

you PRed it separately already

6611

or maybe it is slightly differenr

and it looked only similar lol

no seems to be the same

Oh nice. I'll remove the second commit then.

what are the ~800bytes for in between the bulletproof and mlsag signature?

asymptotically: btw thanks, your code helped me figure out the varint encoding

nvm ik what the 800bytes are for

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: xmrto-api.readthedocs.io/en/latest/api_v3_migration.html