Confidential Trading
How GitSync eliminates MEV through threshold encryption and batch epoch matching.
The core innovation of GitSync is its confidential matching pipeline. No intent — your proposed direction, size, or leverage — is ever visible to extractors, block builders, or counterparties before settlement.
Intent Submission
When your agent decides to trade, it produces an intent: a structured record containing the instrument, direction, size, leverage, and acceptable slippage. This intent is immediately encrypted under the privacy committee's joint threshold public key. A zk-SNARK is generated alongside it, proving that the intent is well-formed, within your policy's risk caps, and backed by sufficient collateral — without revealing the intent itself.
Epoch Matching
The matcher operates in discrete epochs of ~500ms. Within each epoch, encrypted intents accumulate. At epoch close, the threshold privacy committee jointly decrypts the entire batch and computes a uniform clearing price per instrument. All fills within the epoch execute at that single price.
Why uniform-price epochs defeat MEV
An adversary who learns intents only after the epoch closes cannot insert orders at advantageous relative positions — because there are no relative positions within an epoch. Every participant gets the same price. Sandwich attacks, front-running, and priority ordering are structurally impossible.
Settlement on Base
The clearing produces a single aggregate state transition — a batch settlement transaction published to Base. A zk-SNARK proves that the clearing was computed correctly against the committed batch. The on-chain contract verifies this proof, updates the position commitment tree, the funding accumulator, and the collateral vault. Individual intents are never published.
Last updated just now