chore(patterns): add context and crops_profile frontmatter to group 1 - #111
Conversation
|
we skipped the L2 Privacy Evaluation Framework pattern, crops doesn't apply here |
97e5f86 to
214776b
Compare
| - Requires new infra (MPC nodes, co-prover setup). | ||
| - Delegated proving possible, but introduces new trust assumptions. | ||
| - Honest-majority assumption: if a majority of proving parties collude, proof integrity is compromised. | ||
| - **CROPS improvement path**: CR → high by adding economic incentives (bond-backed provers with slashing for Byzantine behavior); OS → yes by open-sourcing the full co-SNARK implementation (TACEO/ABY3 primitives); Security → high by replacing trusted setup with universal setup. |
There was a problem hiding this comment.
Should we align on the same format for this line?
| context: both | ||
| crops_profile: | ||
| cr: medium | ||
| os: partial |
There was a problem hiding this comment.
https://github.com/TaceoLabs/co-snarks
The above is open and MIT licensed. Should we promote it to yes?
| - No built-in privacy of amounts. | ||
| - Irreversibility: once one chain finalizes, that leg cannot be rolled back. | ||
| - Refunds/time-locks are required to mitigate stuck or one-sided settlements. | ||
| - **CROPS improvement path**: CR → high by adding protocol-enforced timelocks with forced-withdrawal on both chains; OS → yes by open-sourcing coordination logic under permissive license; Privacy → full by routing commitments through a shielded pool before attestation; Security → high by replacing irreversibility risk with guaranteed revert paths and verifiable finality proofs. |
There was a problem hiding this comment.
Not sure to understand the path using a shielded pool. But a commit and reveal scheme can be turned fully private, with a ZKP proving knowledge of the pre-image without revealing it for example.
| - ERC-7573, EAS (commit attestations) | ||
| context: both | ||
| crops_profile: | ||
| cr: low |
There was a problem hiding this comment.
Not sure what motivates this to be low.
You just need a hash function. For privacy, you can combine hash + zkp, both primitives have open tools to build it.
|
|
||
| ## Trade-offs | ||
|
|
||
| ### Trust Model Comparison |
There was a problem hiding this comment.
Should we split all these? How do you feel about having all these paths within the same CROPS assessment?
There was a problem hiding this comment.
unsure, can address in follow up pr
There was a problem hiding this comment.
Feel this could be discarded, it's redundant with patter-shielding, plus it feels closer to an approach (shielding + ERC-7573).
214776b to
15fa677
Compare
What are you adding?
Description
adding crops_profile and context frontmatter to group 1
Checklist