# ZKProof Proposal: J-R1CS - a JSON Lines file format for R1CS

**URL:** <https://community.zkproof.org/t/zkproof-proposal-j-r1cs-a-json-lines-file-format-for-r1cs/117>\
**Category:** 2nd ZKProof Workshop\
**Created:** [April 6, 2019, 5:43pm UTC](https://community.zkproof.org/t/zkproof-proposal-j-r1cs-a-json-lines-file-format-for-r1cs/117 "2019-04-06T17:43:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guillaume](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guillaume](https://community.zkproof.org/u/Guillaume)\
**Post date:** [April 6, 2019, 5:43pm UTC](https://community.zkproof.org/t/zkproof-proposal-j-r1cs-a-json-lines-file-format-for-r1cs/117/1 "2019-04-06T17:43:28Z")

</div>

Most ZK proof applications use R1CS to some extent, either as a producer (frontend) or as a consumer (backend). Having a standardized format for expressing R1CS will allow much better interaction and collaboration with-in the ZKProof eco-system.  
In response to the call for community standard, we have defined a JSON lines format for describing a R1CS. You can find the proposal [here](http://www.sikoba.com/docs/SKOR_GD_R1CS_Format.pdf).