QBridge Docs
  • Introduction
  • Problem Statement
  • The QBridge Solution
  • Protocol Architecture
  • Use Cases
  • Compliance & Legal Framework
  • Integration Guide
  • Token Utility — $QB
  • Tokenomics
  • Roadmap
  • FAQ — Frequently Asked Questions
Powered by GitBook
On this page

FAQ — Frequently Asked Questions

🔒 What makes QBridge quantum-secure?

QBridge uses CRYSTALS-Dilithium and Kyber, two NIST-standard post-quantum algorithms. These replace vulnerable ECDSA and RSA signatures used in traditional bridges. Even if a quantum computer existed today, QBridge’s cryptographic core is resistant by design.

🌍 How does QBridge handle jurisdiction-based compliance?

Each transfer checks:

  • The user's jurisdiction (via zkKYC or attestation)

  • The asset’s whitelist/blacklist rules

  • Regional transfer restrictions (e.g. U.S. investor bans)

This is enforced on-chain through smart policies — not just in the frontend.

📡 What metadata travels with each RWA token?

Every bridged asset can carry:

  • Jurisdiction + license IDs

  • Ownership rights and tenancy tags

  • Oracle-bound valuation snapshots

  • Compliance flags (e.g. “retired carbon credit”)

This metadata is preserved and verifiable across chains.

🧠 Is the AI engine deterministic?

QBridge’s AI models produce probabilistic risk scores based on:

  • Identity validation

  • Past transaction behavior

  • Jurisdictional legality

You can tune enforcement thresholds, but models evolve — making compliance adaptive to real-world law changes.

📜 What audit features are built in?

QBridge includes a zkLedger — a zero-knowledge ledger that logs every mint, burn, lock, and unlock event. Auditors can request access (with user consent) to verify trails without exposing sensitive data.

🪙 Why does $QB have real utility?

$QB is used to:

  • Pay for bridge transfers and metadata relay

  • Stake in validator pools

  • Unlock compliance modules and audit dashboards

  • Vote on governance decisions and protocol upgrades

Without $QB, you cannot use QBridge as a full feature set.

🔧 How long does integration take?

Typical setup time:

  • RWA Issuer: ~15 minutes using the wrap SDK

  • DeFi Protocol: ~10 minutes using API and oracle hooks

  • Custodian: ~10 minutes to access zkLedger

All integrations are modular and require no smart contract rewrites.

⚖️ Is QBridge compliant with MiCA, GDPR, and HKPDPO?

Yes. QBridge was built to be:

  • GDPR & HKPDPO privacy-compliant

  • MiCA-ready via enforceable asset policies and proof-based disclosures

  • Compatible with regulated tokenization frameworks (e.g. ERC-3643, SPL-RWA)

PreviousRoadmap

Last updated 2 days ago