QENOVRA is in development · Public network and token sale have not launched.View roadmap ↗
QENOVRA / PROJECT OVERVIEW

Built for the age of agentic commerce.

QENOVRA is an AI-native payment infrastructure project in development. This overview describes the problem, design direction and development boundaries, not a list of live features.

CONCEPT OVERVIEW / SEPTEMBER 2026
01 / MISSION

Payments built for software that can act.

AI agents are increasingly capable of discovering services, executing workflows and coordinating with one another. Traditional digital payments still assume that a person is available to authorize every purchase, fill in each form and review each receipt. That model creates friction for legitimate automated commerce — and unsafe shortcuts when software receives unrestricted account access.

QENOVRA is being designed as a payment-oriented blockchain and developer infrastructure for secure, low-friction and programmable transactions among AI agents, humans and businesses. Our central design principle is simple: an agent may act autonomously only within permissions its owner explicitly defines and can revoke.

Positioning: machine-to-machine, machine-to-human and human-to-global-merchant payments. QENOVRA is not pivoting into a general AI app store or an acquisition-first developer marketplace.

02 / USE CASES

Where programmable payments matter.

AI-to-AI services

An agent purchases inference, data access or specialized services from another agent under a defined cost ceiling.

Human-controlled assistants

Individuals approve limited-duration allowances for travel, productivity, operations or procurement tasks.

Merchant integration

Businesses expose services through payment-aware APIs with transaction receipts and service-delivery records.

Recurring machine commerce

Software pays for metered usage, machine resources or subscriptions according to transparent rules.

These are intended use cases rather than claims that the corresponding production services have launched.

03 / PROPOSED NETWORK

An architecture for permissioned agent commerce.

01. Identity and authority

Distinct identities for owners and agents, together with task-scoped permissions, are intended to help counterparties understand which actions an agent is permitted to take. Identity claims and role assignments must be verifiable independently of marketing labels.

02. Spending policy and custody

The proposed wallet model uses user-controlled, revocable allowances and independent agent vaults. Agent tools should never receive the main wallet seed phrase. Policies can constrain recipients, amounts, time windows, supported assets and emergency pause rights.

03. Payment execution

A payment-centric blockchain architecture is being developed for programmable and, where technically appropriate, frequent low-value transactions. Any performance, settlement or fee claims will require repeatable public measurements, so none are asserted here.

04. Verifiable receipts and PoAC research

Receipts can connect payment to service requests, settlement status and delivery evidence. Optional Proof of Agentic Commerce (PoAC) is a research direction rather than a live consensus or audited protocol.

05. Interoperability and developer migration

The roadmap targets EVM-oriented interoperability and AI-assisted migration of Solidity-based DApps from existing compatible chains. Official migration should require proof of project control and appropriate source-code rights. A deployed copy does not automatically transfer contract state, balances, liquidity, price feeds or historical ownership. TRON, Solana and Bitcoin require dedicated integrations and must not be described as bytecode-compatible EVM chains.

04 / SECURITY

Human authority is part of the protocol design.

  • Consent: explicit user approval before an agent can spend, delegate or deploy under a user's name.
  • Minimum privileges: task- and time-scoped authorizations, transaction ceilings and recipient allowlists.
  • Revocation: emergency pause and accessible records of past authorizations and settlements.
  • Clear boundaries: the wallet, AI orchestration and payment chain have separate release gates. Compiling source code or producing a mobile debug build is not an audit.
  • Independent review: public real-asset support and mainnet are gated by security reviews, live public testing and recovery exercises.

Validator governance, token economics, network fees and production consensus parameters must be documented and evaluated before public network launch. They are not finalized by this promotional overview.

05 / DELIVERY

Develop the foundation. Prove it. Then launch.

Phase 1 — Underway

Multichain wallet development, local signing for four test networks and controlled internal network QA.

Phase 2 — Planned

Independent public QENOVRA testnet, faucet, block explorer, wallet Beta and externally verifiable test transactions.

Phase 3 — Planned

Partner pilots for agent payments, programmable merchant integration and verified EVM DApp migration.

Phase 4 — Planned

Public network launch only after security review, operational preparation, wallet security testing and transparent release documentation.

No definitive launch date or investment-return commitment is made. The wallet's current development builds must not be used to custody real assets.

06 / DISCLOSURES

Important prelaunch information.

QENOVRA is currently in development. This website is an informational project preview, not an offer to sell securities, financial products or digital tokens. No public mainnet, public token sale or airdrop is announced here. There is no guarantee of launch timing, technical performance, future token functionality, market value or financial returns.

Do not send funds to unofficial wallets, connect your primary wallet to unverified sites, or share a seed phrase with anyone claiming to represent QENOVRA. Independent technical and legal review remains necessary before production launch.

01 / 项目愿景

为能够自主执行任务的软件,建立原生支付基础设施。

AI 智能体正在学会发现服务、执行工作流以及彼此协作。但传统数字支付仍假设由人类逐笔确认、输入信息并审核交易;这会阻碍自动化商业,也容易让开发者把过高的钱包权限交给软件。

QENOVRA 正在开发面向 AI 智能体、人类和全球商户的支付型公链及开发者基础设施,支持安全、低摩擦和可编程的交易。核心原则是:AI 只能在所有者明确授权并可随时撤销的范围内自主行动。

项目定位:机器与机器、机器与人,以及人与全球商户之间的支付。QENOVRA 不会转向以 AI 应用商店或抢占开发者流量为核心的发展方向。

02 / 应用场景

可编程支付可以解决什么问题?

AI 与 AI 之间

智能体在预设成本上限内,为其他智能体的数据、模型推理或专业服务支付费用。

人类控制的 AI 助手

个人对差旅、采购或运营任务设置限额和有效期,并可随时停止执行。

全球商户接入

商户通过支持支付的 API 提供服务,返回交易收据和交付记录。

机器持续性交易

软件根据透明规则,为按量计费资源、订阅或持续使用付费。

以上均为目标场景,不代表相应生产服务已经上线。

03 / 技术方向

面向受控智能体商业的技术架构。

身份与权限

为所有者和智能体建立不同身份,通过任务授权标识具体可执行的行为。

支付策略与资金保管

计划采用用户控制、可撤销授权以及独立的 AI 资金库。智能体不能接触主钱包助记词;策略可设置收款方、金额、资产、有效期和紧急暂停。

支付执行

开发以支付为核心的公链,面向可编程交易及适合场景下的高频小额支付。交易性能、最终确认时间和手续费均需通过可重复的公开测试验证,当前不作数值承诺。

支付收据与 PoAC 研究

将交易与服务请求、结算状态、交付证据相联系。PoAC 是可选的智能体商业证明研究方向,不代表已经上线或审计通过。

互操作与项目迁移

规划 EVM 兼容方向,为经授权的开发者提供 AI 辅助 Solidity DApp 迁移。官方迁移会验证项目控制权和代码使用权,但不能自动转移历史状态、资产、流动性和预言机等依赖。TRON、Solana 与 Bitcoin 需要独立适配,不能被当作 EVM 字节码兼容链。

04 / 安全控制

人类权限控制是设计的一部分。

  • AI 支付、部署及授权扩展,都必须遵守所有者的明确许可。
  • 最小权限:任务与时间范围、交易额度以及收款方白名单。
  • 可随时撤销、紧急暂停,并保留授权与交易记录。
  • 钱包、AI 任务编排和公链分别设置发布门槛,不能把编译成功或调试 APK 当作安全审计。
  • 正式处理真实资产以及公网上线之前,必须完成独立安全审查、公开测试和恢复测试。

验证者治理、代币经济、网络费用和正式共识参数将在公网上线前另行制定与披露,本预热说明不代表这些参数已确定。

05 / 开发路径

先建立基础,再验证,最后推出。

第一阶段 / 进行中

多链钱包、四条测试网的本地签名代码及受控的内部 QA 网络。

第二阶段 / 规划中

独立公开测试网、水龙头、区块浏览器、钱包 Beta 与可公开验证的交易记录。

第三阶段 / 规划中

智能体支付、商户合作及经开发者验证的 EVM DApp 迁移试点。

第四阶段 / 规划中

完成安全审查、运行准备、钱包安全验收和透明发布文档后,再考虑公网上线。

没有确定的主网上线日期及任何投资回报承诺。当前钱包开发版本不适合存放真实资产。

06 / 重要说明

项目预热与风险提示。

QENOVRA 目前仍处于开发阶段。本网站只介绍项目愿景与设计,不构成证券、金融产品或数字代币的销售邀约。目前没有通过本网站宣布公开主网、代币销售或空投。开发时间、性能、未来代币功能、市场价值及投资回报均没有保证。

不要向未经认证的地址转账,不要连接未验证网站,更不要向自称 QENOVRA 工作人员的人提供助记词。正式上线前仍需独立技术与法律审查。

\n