# 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://surfermonkey.gitbook.io/litepaper/dact-v2-messaging-protocol/withdraw-phase.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.