# Transaction Lifecycle

#### Data Flow Breakdown

Understanding how a transaction moves from intention to execution without the private key ever touching disk.

**Phase 1: Construction (Dashboard)**

1. User clicks "Send 1 ETH".
2. Dashboard constructs an unsigned raw transaction object (nonce, gas price, to, value, data).
3. Dashboard serializes this object and encrypts it using the session's AES-256-GCM key.
4. Encrypted payload is sent via WebRTC to the Mobile App.

**Phase 2: Signing (Mobile)**

1. Mobile App receives and decrypts the payload.
2. App displays transaction details to the user (Verify Screen).
3. User taps NFC Card and enters PIN.
4. Instant Derivation: Private Key is generated in RAM.
5. Signature: The transaction is signed using the derived key.
6. Wipe: Private Key is zeroed out in RAM.

**Phase 3: Broadcast (Network)**

1. Mobile App sends the Signed Transaction (which contains no secrets, only the signature) back to the Dashboard.
2. Dashboard submits the signed transaction to the Ethereum network via RPC.
3. Blockchain confirms 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://docs.ethelock.xyz/5-technical-specifications/transaction-lifecycle.md?ask=<question>
```

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.