Fintech / Whitepaper

AEVION Fintech Architecture

Version 1.0 · 2026-05-12 · 5 modules · 33+ REST endpoints · production-ready

Abstract

AEVION operates its own financial substrate — not as a layer-1 chain or a stablecoin, but as a verifiable accounting layer where every meaningful financial event in the platform is hash-linked and externally auditable. Five interlocking modules form the substrate: VeilNetX (settlement), QMaskCard (privacy), QGood (transparency), Z-Tide (reputation), QChainGov (governance). Each is independently deployable but together they form a closed loop: contribution → reputation → governance → settlement.

1. Settlement: VeilNetX

VeilNetX is an append-only, hash-chained ledger. Every entry contains a domain-specific payload (donation, charge, transfer, vote tally) plus a prevHash pointer to its parent. The current head is publicly queryable via GET /api/veilnetx-ledger/head. Participants are HMAC-blinded — readers see opaque identifiers, but the chain operator can resolve them with the secret key.

Integrity guarantees

The chain is verifiable end-to-end via GET /api/veilnetx-ledger/chain/verify which recomputes every prevHash from the current head back to genesis. Any tampering breaks the chain and is detected by external observers.

2. Privacy: QMaskCard

QMaskCard issues single-use or recurring virtual PANs. The real funding source (QPayNet wallet or Stripe card) stays hidden behind the mask. Per-mask spend caps, merchant locks, and TTL give holders surgical control. Every authorization fires a VeilNetX entry — masks are private to the merchant but auditable to the holder.

3. Transparency: QGood

QGood is charity infrastructure with cryptographic receipts. Each donation is hash-anchored on VeilNetX so neither the platform nor the campaign operator can quietly redirect funds. Donors get verifiable proof-of-contribution; recipients get a public ledger they can show to auditors.

4. Reputation: Z-Tide

Z-Tide is a soft, decaying reputation layer. Every meaningful action — login streak, helpful comment, Bureau certification, QGood donation — emits a weighted event. The aggregate score unlocks ranks: seedling → current → wave → stream → tide → river → ocean. Downstream modules gate features on rank thresholds.

5. Governance: QChainGov

QChainGov runs proposal lifecycle + voting. Proposals carry a vote mode (yes/no/abstain, ranked-choice, or weighted), quorum, and pass threshold. One vote per user per proposal is enforced by a UNIQUE database constraint. Passed proposals can trigger admin-gated execution via POST /api/qchaingov/proposals/:id/execute.

6. Cross-Module Loop

The modules form a circular reinforcement: donations on QGood → reputation bump on Z-Tide → eligibility for QChainGov votes → settlement of treasury moves on VeilNetX → optionally funded via QMaskCard for privacy. Every step is observable; nothing is hidden between modules.

7. Trust Model

What is trustless

Chain integrity (VeilNetX hashes), donation receipts (QGood VeilNetX entries), proposal counts (QChainGov UNIQUE constraint), mask non-reuse (QMaskCard single-use TTL).

What is trusted

The platform operator (AEVION) for: identity assertions (JWT issuance), Stripe ↔ ledger bridge (fund inflow), and admin lifecycle (proposal open/close, campaign approval).

8. Observability

Every module exposes /health (uptime + dependencies) and /stats (aggregate counters). The /fintech/dashboard page polls all 5 in real time. CI runs three daily smoke tests against production: fintech-prod-smoke (21 read-only checks), fintech-cross-module-smoke (7-step flow audit), and fintech-flow-smoke (full E2E cross-product chain).