Community: CIP for Transactions and Reports on chain data

[matiwinnetou]

A community member: @Crypto2099 is requesting that not only on-chain format specification / documentation would be available from main Reeve website (https://www.cardanofoundation.org/reeve) but also that we put CIP regarding's reeve metadata format regarding Transaction and Reports with explanation of all fields.

This ticket is a placeholder for both items:

• linking PDF with documentation as in the blog post on the main website: https://www.cardanofoundation.org/blog/boosting-transparency-on-chain-financial-report
• formalising current Transaction 1.0 and Reports 1.1 formats (including ver field) and creating Cardano CIP for it.

Learnings and insights:

• @Crypto2099 is not intrested in Reeve itself yet (e.g. because it is java, they don't want to operate it, they think it may be over complicated) but they are intersted to write their own software and manage the process to put on chain data
• @Crypto2099 and others maybe missing deep accounting knowledge so would like to piggy back on existing CF's format with explanation (very well understandable)
• @Crypto2099 expressed they wouldn't like the on chain format to change (there are no such plans but additive changes are unavoidable)

CC: @cleanerm5 @Kammerlo @M4rc0Russ0

[Crypto2099]

Thanks for creating the issue @matiwinnetou :)

I know enough Java that I can read the code and understand what it's doing if I have to, I just don't like to 😄

There were a few blog posts and other pieces of documentation that have been published so far around the Reeve project and would like for this to be discoverable from the main Reeve page https://cardanofoundation.org/reeve rather than simply a "Contact Us" page that led to me making the Twitter/X post in the first place.

I understand that sometimes on-chain formats need to adapt and change but this is what versioning is for, the CF has already begun publishing some transactions on-chain as a proof of concept and things like this must be supported forever (ideally) which is why a versioning scheme should be a first order priority in such situations where the schema may be actively being manipulated and changed as new learnings arise during the development process.

[Kammerlo]

@Crypto2099 I followed the X Thread and thanks also from my side for your feedback, we will take this into account!
I'm currently working on improving the documentation and the on-chain formats are one crucial part.

Besides that there will also be other explanation of e.g. modules, data flow and a demo app. We hope that this will increase the transparency and reusability. When I'm done, I'm happy to hear your feedback :)