V1: EVM-Compatible Runtime (QRC)
What V1 Includes
- EVM-compatible bytecode execution for Solidity contracts.
- QRC token standard aligned with ERC patterns (Transfer/Approval).
- Protocol-level shard quorum gate before execution.
- Deterministic execution with bounded gas and opcode filters.
What V1 Does Not Do
- No dynamic interpreters or non-deterministic opcodes.
- No unbounded external calls without safety checks.
- No contract deploys without validation by the checker node.
Shard-Gated Execution Model
Shard approval is enforced at the transaction layer, so every contract call inherits quantum-safe 2FA without altering contract code.
| Step | Action | Effect |
|---|---|---|
| 1 | User signs tx with QP key | Produces standard signature + shard request |
| 2 | Validator quorum approves shards | Tx becomes eligible for execution |
| 3 | EVM executes bytecode | Deterministic state update |
| 4 | Receipt published | Gas/swap fees logged inline |
Contract Validation (Separate Checker Node)
Pre-Deploy Rules
- Bytecode size limit (default 24KB)
- Opcode denylist (SELFDESTRUCT, DELEGATECALL, CALLCODE)
- Determinism and bounded computation
Checker Output
- Pass/fail with issue list
- Bytecode size report
- Deployment-ready payload if clean
Gas & Fees
Gas is accounted inline on each transaction and credited to the protocol fee pool. Explorer views surface gas paid per tx without creating separate “gas transactions.”
Contract Calls
Gas is paid in QP (or USDT where configured) at execution time. Failure to meet gas requirement rejects execution before state changes.
Deploys
Deploys require higher gas and pass the checker node. This discourages spam and keeps chain state clean.
Transparency
Receipts include gas paid, fee destination, and shard approvals for full auditability.
V2: AI-Scored Contracts & External Data
V2 introduces contract risk scoring and graded oracle inputs. The goal is to make non-deterministic data safe for on-chain execution.
AI Scoring
- Scores external inputs (A–F)
- Simulates volatility and failure modes
- Publishes rationale and mitigation steps
External Data
- Source registry with trusted tiers
- Multi-provider quorum and fallback rules
- On-chain provenance and audit trail
Roadmap
V1 (Now)
EVM-compatible runtime, QRC token standard, deterministic execution, shard-gated authorization.
V2 (Feb 2026)
AI-scored contracts, external data grades, oracle safety registry, contract risk dashboard.
V3 (2026+)
Advanced contract policies, appchain support, and enterprise-grade verification tooling.