|
|
@@ -2,9 +2,9 @@
|
|
|
|
|
|
## renegade for dummies
|
|
|
|
|
|
-- renegade implemented for erc20 transparent token to be swapped between two parties, each party create a wallet $W = (B,O,F,K,r)$ of balance, order, fee, public keys, blinding value with transition state for every internal (within-darkpool) $T_I=(\telda(m_I),\telda(v_i))$ encrypted by the receiver key, or external transaction (transparent) $T_E=(\telda(m_E),\telda(v_E),\telda(d_E))$, each trader picks order o to be matched, it's corresponding covering balance b, and fee f, blinding r, and create commitments to o, b, f, r as $H_o$, $H_b$, $H_f$, $H_r$ and a VALID-COMMITMENT zk-snark proof that those commitments are derived from known private witnesses.
|
|
|
+- renegade[^1] implemented for erc20 transparent token to be swapped between two parties, each party create a wallet $W = (B,O,F,K,r)$ of balance, order, fee, public keys, blinding value with transition state for every internal (within-darkpool) $T_I=(\tilde{m_I},\tilde{v_i})$ encrypted by the receiver key, or external transaction (transparent) $T_E=(\tilde{m_E},\tilde{v_E},\tilde{d_E})$, each trader picks order o to be matched, it's corresponding covering balance b, and fee f, blinding r, and create commitments to o, b, f, r as $H_o$, $H_b$, $H_f$, $H_r$ and a VALID-COMMITMENT zk-snark proof that those commitments are derived from known private witnesses.
|
|
|
- from on-chain published VALID-COMMITMENT counterparties validate it's valid, and start matching process.
|
|
|
-- reconstruct commitment over MPC through secret shares [o], [b], [f], [r], first construct match tuple $M=(\telda(m_1), \telda(m_2), \telda(v_1), \telda(v_2), d, f_1, f_2)$ validate exchange coins match, $v_1==v_2$, directions, and that fee covers relay fee. reconstruct commitments shares $H_{o_1}$, $H_{b_1}$, $H_{f_1}$, $H_{o_2}$, $H_{b_2}$, $H_{f_2}$, open shares through third party, then exchange notes.
|
|
|
+- reconstruct commitment over MPC through secret shares [o], [b], [f], [r], first construct match tuple $M=(\tilde{m_1}, \tilde{m_2}, \tilde{v_1}, \tilde{v_2}, d, f_1, f_2)$ validate exchange coins match, $v_1==v_2$, directions, and that fee covers relay fee. reconstruct commitments shares $H_{o_1}$, $H_{b_1}$, $H_{f_1}$, $H_{o_2}$, $H_{b_2}$, $H_{f_2}$, open shares through third party, then exchange notes.
|
|
|
|
|
|
## dark renegade
|
|
|
|
|
|
@@ -12,11 +12,17 @@
|
|
|
- TODO eliminate third-party for opening shares.
|
|
|
|
|
|
# framework
|
|
|
-- mpc-stark is spdz mpc built over stark-curve (curve can change)
|
|
|
-- mpc-bulletproof mpc r1cs with mpc inner product proof built over mpc-stark
|
|
|
+
|
|
|
+- mpc-stark[^2] is spdz mpc built over stark-curve (curve can change)
|
|
|
+- mpc-bulletproof[^3] mpc r1cs with mpc inner product proof built over mpc-stark
|
|
|
- plug darkfi-p2p network into mpc-bulletproof
|
|
|
-- fork renegade
|
|
|
+- fork renegade[^4]
|
|
|
- if the aim is to use halo2 proof zk-proofs, fork mpc-stark, and replace stark-curve with pallas-curve.
|
|
|
- rewrite renegade zk-snark proofs with darkfi compiler
|
|
|
- replace wallet update with money transfer contracts
|
|
|
- TODO eliminate third-party for opening shares.
|
|
|
+
|
|
|
+[^1]: https://renegade.fi/whitepaper.pdf
|
|
|
+[^2]: https://github.com/renegade-fi/mpc-stark
|
|
|
+[^3]: https://github.com/renegade-fi/mpc-bulletproof
|
|
|
+[^4]: https://github.com/renegade-fi/renegade
|
ertosns