🌊
SurferMonkey Litepaper
  • Introduction
  • The Evolution to DarkWeb3.0
  • Plug-In Strategy
  • Universal zkMixer
    • Cryptographic window
    • Anonymous interoperability
    • Easy dApp Integration via Front-End
  • DACT-v2 Messaging Protocol
    • Deposit phase
    • Withdraw phase
    • Revert phase
  • Security
    • Proactive security
    • Behavioral security
  • Enhanced Fairness and Security in Blockchain Transactions
    • Mitigating MEV
    • Censorship Resistance
  • Tokenomics - WaveGuard (WAGU)
    • Efficient Gas Management with zkMiners
    • Establishing a Sustainable Circular Economy
Powered by GitBook
On this page

Was this helpful?

  1. DACT-v2 Messaging Protocol

Withdraw phase

During the withdraw phase, the user creates the ZKP locally and submits the transaction to the target blockchain. Here, the ZKP gets verified along with its public signals. If all verifications are true, then the DACT Router makes the agnostic call to the target dApp, passing the user's intentions of the function to be called alongside its function parameters. It's important to treat the data structures from the deposit phase as private keys. These structures include the Secret and Nullifier number, the user commitment, plus the Smart Contract security parameters as all this creates the leaf. It's crucial to keep these data structures secure and not share them with anyone to prevent unauthorized access or unwanted interference in the transaction.

PreviousDeposit phaseNextRevert phase

Last updated 2 years ago

Was this helpful?