# Safe Interaction with DApps

### Introduction

Interacting with decentralized applications (DApps) on **Quranium Chain** and **EVM-compatible networks** (e.g., Ethereum, Polygon) requires vigilance to protect your assets. Q Safe Wallet automates critical security features like post-quantum cryptography (SLH-DSA) for Quranium DApps and ECDSA for EVM chains—but **your proactive validation is key**. This guide explains how to use DApps securely while minimizing risks.

***

### Quranium Chain DApps: Post-Quantum Security

#### Key Features

Quranium Chain uses **SLH-DSA**, a quantum-resistant signing algorithm, to future-proof transactions. Q Safe Wallet ensures:

| **Feature**                     | **How It Works**                                                                                 | **User Action Required**                             |
| ------------------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------- |
| **Automatic Network Detection** | Wallet switches to SLH-DSA signing when interacting with Quranium DApps.                         | Confirm the network is "Quranium" before proceeding. |
| **Signature Validation**        | All transactions are signed with your SLH-DSA private key (derived from your mnemonic).          | Keep your mnemonic offline and never share it.       |
| **Gas Fee Handling**            | Gas fees are paid in **QRN** (Quranium’s native token). Wallet checks balance before submitting. | Ensure sufficient QRN balance for transactions.      |

***

### EVM-Compatible DApps: Standard Security

#### Key Features

For EVM chains (Ethereum, Polygon, BSC), Q Safe Wallet uses **ECDSA** (secp256k1 curve) for signing.

| **Feature**                   | **How It Works**                                                               | **User Action Required**                                  |
| ----------------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------- |
| **Automatic Chain Detection** | Wallet detects EVM chains (e.g., Ethereum, Polygon) and uses ECDSA signing.    | Confirm the correct chain (e.g., “Ethereum Mainnet”).     |
| **Gas Fee Optimization**      | Supports dynamic gas tiers (Economy/Fast/Fastest) based on network congestion. | Select appropriate gas tier to avoid failed transactions. |
| **DApp Permissions**          | Manages token allowances (e.g., ERC-20 approvals) and lets you revoke access.  | Periodically revoke unused approvals.                     |

***

### Best Practices for All DApps

#### 1. Verify DApp Authenticity

* **Check URLs**: Ensure you’re on the official DApp website (e.g., `app.uniswap.org`, not `uniswaap.com`).
* **Audit Smart Contracts**: Use block explorers (Etherscan, Quranium Explorer) to confirm contracts are verified.

#### 2. Limit Token Approvals

* **Set Allowance Caps**: Approve only the amount needed for the transaction.

#### 3. Confirm Transaction Details

* **Recipient Addresses**: Match them to official DApp contracts or known addresses.
* **Slippage Tolerance**: Use conservative values (1-3%) to avoid front-running.

***

### Step-by-Step Workflow

#### Safe Quranium DApp Interaction

1. **Connect Q Safe Wallet**:
   * Ensure the DApp URL is correct.
   * Confirm the wallet switches to **Quranium Chain**.
2. **Review Transaction**:
   * Check gas fees in QRN and validate your balance.
   * Confirm SLH-DSA signing is active (look for "Quantum-Safe" badge).
3. **Sign and Monitor**:
   * Track the transaction.

#### Safe EVM DApp Interaction

1. **Connect Q Safe Wallet**:
   * Verify the DApp’s domain and chain (e.g., Ethereum Mainnet).
2. **Adjust Gas Fees**:
   * Select **Economy/Fast/Fastest** based on urgency.
3. **Set Allowances**:
   * Approve only the amount needed (e.g., 1 ETH, not unlimited).
4. **Sign and Track**:
   * Use Etherscan/Polygonscan to monitor progress.

***

### Common Risks & Mitigations

| **Risk**                      | **Mitigation**                                                          |
| ----------------------------- | ----------------------------------------------------------------------- |
| **Phishing DApps**            | Bookmark trusted DApps and avoid Google ads.                            |
| **Unlimited Token Approvals** | Revoke unused approvals monthly.                                        |
| **Mismatched Network**        | Double-check the chain (e.g., Quranium vs. Ethereum) before signing.    |
| **Malicious Contracts**       | Reject transactions with unrecognized payloads or unverified contracts. |

***

### Troubleshooting

#### Insufficient Gas Fees (Quranium)

* **Cause**: Low QRN balance.
* **Fix**: Acquire QRN from a supported exchange.

#### Pending EVM Transactions

* **Cause**: Gas too low for network congestion.
* **Fix**: Speed up the transaction with a higher gas tier.

#### Unrecognized Contract Interaction

* **Cause**: Compromised DApp or accidental approval.
* **Fix**: Revoke permissions immediately via Q Safe Wallet.

***

### Note :

Q Safe Wallet automates critical security measures, but **your attention to detail prevents disasters**. Always verify DApp URLs, limit token approvals, and confirm chain settings. Quantum-safe SLH-DSA (Quranium) and battle-tested ECDSA (EVM) protect your transactions—but vigilance is irreplaceable.

***


---

# 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.qsafewallet.com/best-practices/safe-interaction-with-dapps.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.