NEXORA — Terms of Use

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

1. Acceptance of Terms

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.

2. Nature and Scope of Services

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.

• FIFO queue-based reward allocation.

• Multiple parallel reward queues.

• Order reward targets and automatic repurchase.

• 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.

No guaranteed staffed operations

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.

No guaranteed permanent development or maintenance team

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.

3. User Eligibility

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.

4. Wallet and Private Key Security

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.

5. Nexora Coin and Orders

5.1 Nexora Coin

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. Actual exchangeability depends on verified deployed contracts, available trading pairs, reserves, and blockchain liquidity. No live swap or redemption mechanism is verified for the current Preview / Development application.

5.2 Order Purchases

1. Each specified standard order consists of 10 NXC.

2. Purchases must be in multiples of 10 NXC.

3. Larger purchases are automatically divided into standard orders.

4. Each standard order is specified to have an independent record and queue position if implemented by a deployed contract.

5. The specified queue order is based on confirmation order of valid blockchain payment transactions.

6. Order entitlements are calculated independently based on each standard order amount.

5.3 Global FIFO Sequence

The project specification describes a First-In, First-Out (FIFO) mechanism.

Valid orders are queued according to their blockchain transaction confirmation order.

If multiple parallel queues are implemented:

• Eligible queue-head orders participate in reward distribution.

• Available rewards are allocated equally among eligible queue heads.

• Orders exit upon reaching their reward targets.

• Subsequent orders advance according to the predefined rules.

• New orders preferentially fill existing incomplete queues.

• Queue operations are intended to be governed by smart contracts.

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.

5.4 Reward Target and Settlement

The specified reward target for each standard order is twice its order amount: 20 NXC for a 10 NXC order.

Upon reaching the target:

• 10 NXC (50% of the target) is allocated to the user's designated wallet address under the contract rules.

• 10 NXC (50% of the target) is specified to be used to purchase a new standard order under the contract rules.

• The repurchased order enters the queue as a new order according to the applicable ordering rules.

• Automatic repurchases are subject to applicable referral reward and TOKEN airdrop eligibility rules.

The reward target is a contractual system parameter, not a guarantee that a user will receive the stated amount.

These are specified rules, not verified live behavior or a guarantee of payment. Actual rewards depend on subsequent orders, distributable funds, queue conditions, deployed contract execution, and other on-chain factors.

5.5 Order Fund Allocation

Under the project specification, each valid new 10 NXC order is allocated as follows:

Automatic repurchase orders are subject to the same specified allocation rules. How an unassigned referral portion is handled is not established by this document and must be determined by the actual contract.

Rewards are allocated equally among eligible queue heads. If an order reaches its remaining reward target, any excess allocation remains in the reward pool for other unfinished queue-head orders.

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

6. Referral Relationships and Rewards

The Platform supports invitation codes and direct referral relationship 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. If there is a valid eligible direct referrer, qualifying orders generated by directly referred addresses have a specified 5% referral allocation.

4. Automatic repurchase orders are also subject to referral reward allocation.

5. Referral allocations are intended to be processed by smart contracts if deployed.

6. Whether a referral relationship can be changed after binding is determined by the deployed contract.

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

7. NEXORA TOKEN Airdrop

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

The project specification states:

• Specified total supply: 10,000,000,000 NEX. Whether a deployed contract enforces this as a maximum cap has not been verified.

• Reference allocation: 1,000 NEX eligibility units per qualifying standard order; qualifying automatic-repurchase orders are included.

• When 100,000,000 NEX has been distributed, evaluation and preparation for possible exchange-listing applications may begin. This is not an exchange approval or guaranteed listing.

These are specification statements, 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.

8. Swaps and Exchange

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.

9. Maintenance Pool

The project specification allocates 5% of each qualifying order to the maintenance pool, for smart contract GAS, community maintenance, and rewards to designated early contributors under predefined rules.

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.

10. Smart Contracts and Irreversible Transactions

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.

11. Prohibited Conduct

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.

12. Third-Party Services

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.

13. Limitation of Liability

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 automatic repurchases.

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

14. Amendments

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.

15. Governing Law and Disputes

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.

16. Contact and Support

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.