NEXORA
Launch AppPreview / Development
On this page

NEXORA — Terms of Use

Document Version: v1.1 Applicable Products： NEXORA、NEXORA-WEBSITE and their associated smart contracts and on-chain services.

Welcome to NEXORA (the "Platform").

These Terms of Use ("Terms") govern your access to and use of NEXORA, NEXORA-WEBSITE, associated frontend applications, blockchain smart contracts, and related services.

By accessing or using the Platform, you acknowledge that you have read, understood, and agreed to these Terms, the Privacy Policy, and the Risk Disclosure.

If you do not agree, do not access or use the Platform.

NEXORA is designed as a decentralized, blockchain-based protocol. Its specified business rules are intended to be implemented through smart contracts; the frontend is a separate user interface designed for static distribution, including through IPFS and Arweave. Frontend availability and blockchain execution are separate: an unavailable interface does not by itself establish that a deployed contract has stopped operating, and an available interface does not establish that a contract or feature is live.

The current application is a Preview / Development build. The project documentation available for this release does not identify verified production contract addresses, ABIs, or a configured production RPC/data source. No live order submission, queue settlement, swap, referral claim, or TOKEN distribution is represented as available or verified by these Terms.

The design specifications describe features that may include:

  • Nexora Coin (NXC) order rules and on-chain records.

  • Address-level fair admission and one global FIFO settlement queue.

  • Independent standard orders, batch interleaving, and equal per-order reward weight.

  • A proposed maximum reward cap and optional internal rebuy.

  • Direct referral relationship rules and referral allocations.

  • NEXORA TOKEN (NEX) allocation eligibility.

  • Digital asset swaps subject to actual contract support and available liquidity.

  • Wallet, transaction, and on-chain information interfaces.

If deployed, contract execution is governed by the deployed code, blockchain consensus, and the contract's actual permissions and configuration. The project documentation available for this release does not verify a deployment, its upgrade architecture, privileged functions, or permission holders. Do not infer immutability, non-upgradeability, or the absence of administrative control. Contract execution does not require manual approval unless the relevant contract or its configuration requires it.

NEXORA does not guarantee 24/7 human support or monitoring, a staffed customer-service team, a permanent response channel, immediate responses, manual transaction processing, manual order matching or reward settlement, emergency intervention, dispute resolution, or recovery of failed, confirmed, or irreversible transactions. The protocol is designed for rules-based execution where and when deployed contracts and blockchain networks permit it; this does not mean that no person has contributed to the project or waive any legal duty that cannot lawfully be waived.

NEXORA does not promise a permanently staffed development, maintenance, or operations team; continuous maintenance, future upgrades, security patches, permanent frontend hosting by a particular operator, or restoration of discontinued third-party services. The frontend may become outdated or unavailable while a deployed contract may remain accessible through other compatible interfaces; neither continued contract operation nor alternative interface availability is guaranteed.

You must:

  1. Have reached the legal age of majority in your jurisdiction.

  2. Have legal capacity to enter into binding agreements.

  3. Control a wallet address lawfully.

  4. Not be prohibited by applicable law from participating.

  5. Not use the Platform for money laundering, fraud, terrorist financing, sanctions evasion, or other unlawful activities.

Sanctioned persons, residents of restricted jurisdictions, and persons legally prohibited from participating in relevant digital asset activities may not use the Platform.

You are responsible for determining whether your participation is lawful in your jurisdiction.

NEXORA does not require users to disclose private keys or recovery phrases.

You are solely responsible for:

  • Safeguarding your private keys and recovery phrases.

  • Verifying wallet addresses.

  • Reviewing the contract address, transaction contents, amount, and wallet prompts before signing.

  • Selecting a compatible network and asset.

  • Paying applicable GAS and transaction fees.

  • Understanding the consequences of the relevant contract call and any permissions you grant.

  • Protecting your digital assets and assessing the risks of irreversible transactions.

  • Managing wallet permissions and signatures.

  • Losses resulting from compromised keys, incorrect transfers, or malicious approvals.

Never disclose your private keys or recovery phrases to anyone claiming to represent NEXORA.

Nexora Coin ("NXC") is the internal unit of account described in the project specifications. NEXORA TOKEN ("NEX") is a separate asset.

The specified order-pricing reference is:

1 NXC = 1 USDT.

This denomination does not automatically constitute a USDT deposit, bank deposit, fiat currency, or unconditional redemption obligation.

This is a target reference only, not a fixed-price exchange, redemption, or liquidity guarantee. Any redemption is subject to actual reserve availability, applicable redemption rules, and legal requirements. Actual exchangeability also depends on verified deployed contracts, available trading pairs, and blockchain liquidity. No live swap or redemption mechanism is verified for the current Preview / Development application.

  1. The specified standard order amount is 10 NXC.

  2. Larger purchases are divided into independent standard-order records, each with its own order ID, state, and reward accounting.

  3. Each standard order has the same base reward weight. Holding more orders does not increase an individual order's weight or priority.

  4. Orders from the same address enter one global sequence through address-level admission rotation, at no more than one order per address per admission turn. Additional pending orders return to later turns; addresses without pending orders are skipped.

  5. Admission scheduling determines which pending order enters next. It is address-level scheduling, not a guarantee of real-world identity fairness or equal waiting times.

  6. Each admitted order receives a unique, monotonic global sequence number. Settlement follows global FIFO order, and a later order cannot skip an unfinished queue head.

  7. Batch interleaving changes neither order amounts nor the rights of already admitted orders. Administrators cannot manually insert orders.

NEXORA Sequence V2.1 distinguishes user admission scheduling from settlement. Fair admission selects which pending order enters the one global economic queue; global FIFO determines settlement after admission. The admission scheduler is specified to follow deterministic rules, but an address is not proof of a unique real-world person and the mechanism does not guarantee identity fairness or prevent Sybil behavior.

Queue segments or capacity limits, including a previously cited 100-order value if retained, are technical storage or processing units only. They do not create independent economic queues or reward priority.

Actual queue status, order status, and reward allocations can only be established from verified deployed contract data. No such production data source is configured for the current application.

The proposed maximum cumulative reward cap is 20 NXC per standard order. It is not a guaranteed reward, minimum payout, return of principal, or guaranteed completion amount. Actual settlement is constrained by funds actually available in the reward pool; expected but unfunded rewards are not confirmed assets.

Rebuy is voluntary and OFF by default. A voluntary rebuy creates a new independent order from internal recycled balances. The new order receives a new ID, re-enters user-level admission, and receives a new global FIFO sequence after admission; it does not inherit a prior queue position. External orders and internal rebuy orders are accounted for separately. Internal rebuy is not new external capital and does not automatically create repeated NEX eligibility.

These are proposed rules, not verified live behavior or a guarantee of payment. Actual rewards and timing depend on applicable implemented rules and available funds.

Under the current proposal, each eligible 10 NXC external order is allocated as follows:

AllocationPercentage
Direct referral allocation, if a valid eligible direct referrer exists5%
Maintenance pool5%
Global sequence reward pool90%

Whether the proposed referral allocation applies to internal rebuy, and how an unassigned referral portion is handled, remain subject to final rules and actual implementation. Maintenance-pool funds are not automatically available for reward settlement. Each standard order has equal base reward weight; order quantity does not increase per-order weight.

If deployed, the contract and actual on-chain execution govern. The current application does not provide verified live queue data.

The current proposal describes direct referral only, subject to eligibility and applicable legal review; it does not specify a multi-level referral reward structure. The Platform's preview does not verify live referral records.

  1. The specified referral relationship is bound according to contract rules.

  2. Each eligible address may have only the direct referral relationship permitted by the contract.

  3. A proposed 5% direct referral allocation may apply to an eligible external order if a valid eligible direct referrer exists.

  4. Whether an internal rebuy order is eligible for referral allocation remains subject to final rules.

  5. Referral allocation does not increase an order's base reward weight.

  6. Referral eligibility and operation remain subject to applicable legal review and verified implementation.

Referral rewards do not guarantee income and do not authorize unlawful recruitment or financial activities.

NEXORA TOKEN ("NEX") is a digital token separate from Nexora Coin ("NXC").

The current proposal states:

  • Proposed total supply: 10,000,000,000 NEX. Final supply and contract enforcement have not been verified.

  • Proposed initial allocation reference: 1,000 NEX eligibility per qualifying external order, subject to published rules.

  • Internal rebuy does not automatically create repeated TOKEN eligibility. Actual eligibility must follow the implemented rules.

  • A previously published 100,000,000 NEX milestone is pending confirmation under V2.1. Even if retained, it would trigger evaluation and preparation for a possible exchange-listing application only.

These are proposals, not evidence of deployed token or airdrop contracts, actual eligibility, or tokens already distributed. Actual distribution, if any, is subject to verified contract rules, available supply, and applicable conditions.

No listing, trading, appreciation, or particular market value is guaranteed.

The project specifications describe potential digital asset swaps through blockchain smart contracts and available liquidity. No live swap is verified for the current application.

You acknowledge that:

  1. Swap transactions require your confirmation and signature.

  2. Prices may fluctuate due to market supply, demand, and liquidity.

  3. Slippage, transaction fees, and network GAS fees may apply.

  4. Swaps may fail because of insufficient liquidity, contract restrictions, or network issues.

  5. You are responsible for GAS fees.

  6. Sufficient USDT liquidity is not guaranteed at all times.

  7. No unconditional fixed-price redemption is promised without an explicit contractual and adequately funded redemption mechanism.

The current proposal allocates 5% of each eligible external standard order to the maintenance pool. Proposed accountability includes multisig management and transparent balance and expenditure records; these controls and any actual uses are not verified. Maintenance funds are not automatically available for reward settlement.

The allocation and its actual authorized uses, addresses, and transactions are not verified for the current application. If a contract is deployed, its code, permissions, and on-chain records—not this description—determine actual operation.

Core rules are specified for smart-contract execution, but the current application has no verified production contract deployment or configured production RPC/data source.

You acknowledge that:

  • Blockchain transactions are generally irreversible.

  • Whether deployed contract rules can be modified depends on their actual code, upgrade architecture, permissions, and configuration, none of which has been verified for this release.

  • Smart contracts may contain vulnerabilities or unknown risks.

  • Blockchain networks may experience congestion, forks, or outages.

  • Third-party wallets, RPC providers, bridges, and trading protocols may fail.

  • Frontend availability is not guaranteed.

An immutable contract, if one exists, would not mean absolute security or guaranteed perpetual operation.

You must not:

  • Use the Platform for fraud, money laundering, or unlawful activities.

  • Attack smart contracts through malicious scripts or automated tools.

  • Falsify transaction records, referral relationships, or airdrop eligibility.

  • Exploit vulnerabilities to obtain unauthorized rewards.

  • Violate third-party intellectual property rights.

  • Disrupt the operation of the frontend or blockchain network.

  • Violate applicable laws or sanctions.

The Platform may rely on third-party wallets, blockchain networks, RPC providers, decentralized exchanges, bridges, and infrastructure.

Such services are independently operated and are not fully controlled by NEXORA.

To the maximum extent permitted by applicable law, the Platform and related service providers do not provide guarantees against:

  • Digital asset price fluctuations.

  • Loss of wallet private keys.

  • Incorrect signatures or transfers.

  • Blockchain network interruptions.

  • Smart contract vulnerabilities or third-party attacks.

  • Insufficient liquidity or failed swaps.

  • Failure to list or trade NEX.

  • Failure to reach expected queue rewards.

  • Economic losses arising from voluntary internal rebuy.

Nothing in these Terms excludes liability that cannot legally be excluded, including statutory consumer rights and liability for fraud where applicable.

Frontend announcements or unilateral statements cannot by themselves change blockchain state. Whether deployed contract rules can be changed depends on the actual code and permissions, which are not verified for this release.

Non-on-chain service terms and informational content may be updated where permitted by applicable law.

Updated versions will identify the applicable document version. Any legally required notice or effective date remains subject to applicable law and legal review.

The governing law, dispute resolution forum, and jurisdiction must be determined by the actual responsible entity in accordance with its place of operation, target-user jurisdictions, and applicable regulatory requirements. The project materials currently available for this release do not identify a verified operating entity; this documentation gap does not establish that no responsible entity exists or remove any legal responsibility.

The governing law and dispute provisions require qualified legal review and must not be treated as an established cross-border dispute resolution arrangement.

The project materials available for this release do not provide a verified legal contact channel, registered address, or guaranteed customer-support channel. This does not mean that no responsible entity or legal obligations exist. No permanent response time or staffed support service is promised. Any official contact details should be published only after they have been verified and approved.