RMOR Sale Terms

Effective date: September 1, 2026, 00:00 UTC

Terms version: 1.0

Canonical link to the Terms: https://rmor.morana.network/terms

Sale Interface: https://rmor.morana.network/buy

Sale Contract page on the Base explorer: https://basescan.org/address/0x4103Ebb6A855E774a18AC71f4d6B416ee3107892#code

Morana Network Pte. Ltd., a company incorporated in Singapore, develops the Morana network and organizes the sale of RMOR.

These RMOR Sale Terms (the "Terms") are entered into between the Company and each person participating in the sale (the "Buyer"). The Company and the Buyer are collectively referred to as the "Parties" and individually as a "Party".

Before a transaction is formed, the Interface must show the Buyer the canonical link, the version number, and the effective date of the Terms, and must require a separate active confirmation of consent. By making such a mark and submitting the purchase transaction, the Buyer confirms that they have read, understood, and accept precisely the stated edition of the Terms.

A Buyer who calls the Sale Contract directly without the Interface confirms that, before the call, they obtained the link to the Terms from the official website or from the Sale Contract's page on the block explorer, checked the version number and effective date, and accepts that edition. The mere technical ability to call the Contract does not waive the Terms and does not mean the participation is lawful.

1. Eligibility

By participating in the sale, the Buyer represents and warrants that:

• they have reached the age of majority and are entitled to enter into these Terms;
• if acting on behalf of a legal entity, that entity is duly established and they hold the necessary authority;
• participation, payment, holding RMOR, and the subsequent receipt of MOR do not violate any law applicable to them;
• they are not a person with whom the Company is prohibited or restricted from dealing under sanctions and restrictive measures binding on the Company, the Buyer, or the relevant transaction, including United Nations Security Council sanctions as implemented under the law of Singapore, and other applicable national measures;
• they are not listed on an applicable sanctions list, are not owned or controlled by a listed person, and are not acting directly or indirectly on behalf of or for the benefit of such a person;
• the assets used for payment lawfully belong to them, were not obtained through criminal conduct, and are not connected with money laundering, terrorist financing, sanctions evasion, fraud, or other unlawful conduct;
• they are acting for their own account, unless they have expressly disclosed otherwise to the Company in a manner permitted by law.

The technical ability to call the Sale Contract does not mean that a particular person's participation is lawful or permitted by these Terms.

There is no single universal "global sanctions list." The Buyer must independently check and monitor all sanctions and other legal restrictions applicable to them, their address, the source of funds, and the transaction. The absence of a person or country from any one particular list does not guarantee that participation is lawful. This obligation of the Buyer does not relieve the Company of its own obligations under applicable law.

2. Token sale

2.1. The Morana network, MOR, and RMOR

Morana or the Network means the blockchain network under development by Morana. Mainnet means the main operating Network after the genesis block is created. MOR means the Network's native coin, which is to come into existence at Mainnet launch.

RMOR is a non-transferable receipt token on the Base network evidencing the Buyer's contractual right to claim delivery of the corresponding amount of MOR after Mainnet launches and redemption opens.

RMOR is not MOR, wrapped MOR, or an existing Network coin. As of the date of the sale, Mainnet has not launched and MOR does not yet exist.

RMOR does not confer any equity or ownership interest in the Company, voting rights, dividends, interest, a share of profit or revenue, a right to a liquidation preference, or any other corporate right. RMOR is not intended for use as a means of payment. These characteristics reflect the Company's intent and do not by themselves determine the regulatory classification of RMOR or MOR.

2.2. Sale period

The sale begins on September 1, 2026, at 00:00 UTC and ends on December 31, 2026, inclusive. For the Sale Contract, the end of the period is January 1, 2027, at 00:00 UTC: from that moment, no new purchases are accepted.

The sale may end earlier if the stage limit is reached. The Company may place the sale on a general pause for reasons of security, legal compliance, or fixing an error, and does not guarantee its continuous availability throughout the period.

2.3. Price, minimum, and payment

The stage price is 0.01 USDC per 1 RMOR. The minimum purchase is 5,000 RMOR, i.e. 50 USDC. Purchases may only be made in whole numbers of RMOR.

Payment is accepted exclusively in native USDC issued by Circle on the Base network, chain ID 8453. Bridged USDbC and any other tokens are not accepted. The Buyer pays the Base network fee.

The price, minimum, limit, start and end time, USDC address, and funds-recipient address are set at the deployment of the Sale Contract. If the text and the published parameters diverge, the Company must pause the sale and publish an explanation; the divergence does not mean the Buyer has agreed to less favorable parameters.

2.4. Making a purchase

Contracts means the sale, RMOR, address-registration, and redemption smart contracts published by the Company. Interface means the software on the Company's website for convenient interaction with the Contracts; the Contracts may also be accessible without the Interface.

A purchase is completed when the Sale Contract, in a single confirmed transaction, receives USDC from the Buyer and transfers RMOR to that same Buyer address. USDC is sent directly to the Company's published treasury address; the Sale Contract does not hold it.

Transactions on the Base network are irreversible. The Company cannot guarantee the cancellation or refund of a mistakenly sent or already-confirmed transaction.

2.5. Non-transferability of RMOR

RMOR cannot be sold, gifted, or transferred to another ordinary address, including another address of the same Buyer. The Contract permits only the transfer directions provided for by the system, in particular transfer from the treasury, return to the treasury, and burning through the redemption procedure.

No secondary market for RMOR is provided or supported by the Company.

2.6. Planned Mainnet launch, the team's efforts, and use of proceeds

The Company plans to launch Mainnet during the first or second quarter of 2027, i.e. approximately between January 1 and June 30, 2027. This period is a development target, not a guaranteed launch or delivery date.

The Company undertakes to organize the team's work and to use commercially reasonable, good-faith efforts to develop, test, secure, and launch Mainnet. This is an obligation of effort, not an unconditional guarantee of a technical outcome or of launch by a particular date.

The purchase price is consideration for the contractual right evidenced by RMOR, and not the Buyer's contribution to the Company's capital, a transfer of funds into trust, or an instruction to invest funds on the Buyer's behalf. Once received, the purchase price becomes the Company's property. The Buyer does not acquire any proprietary, equity, or beneficial interest in the proceeds, the Company's assets, or any specific result of their use, and does not obtain any right to direct spending.

The Company undertakes to direct the proceeds to the ordinary business of developing, bringing to launch, and operating the Morana project. Project expenses include, among others, software development and testing, compensation for the team and contractors, infrastructure, security and audits, legal, accounting, and regulatory support, the Company's taxes and duties, and reasonable operating and communications expenses. The Company manages the funds within this purpose according to good-faith business judgment. Use of the proceeds does not give the Buyer any right to profit, income, interest, appreciation in value, or a share in the Company's results.

Proceeds are not held as a separate refund reserve, collateral, deposit, or trust property, and may be spent before Mainnet launches.

The planned source of delivery is a launch reserve basket of 26,250,000 MOR, to be created in the Network's genesis block. The Network's rules must require the correct amount and script of this basket as a condition for accepting the first block. Because MOR does not exist before Mainnet launch, as of the date of the sale this basket is not yet an existing pledge, deposit, trust property, or other legally segregated security.

The expiry of the target period does not by itself terminate development or the right to redemption. That right survives until it is performed or until the project's final termination under Section 2.7.

2.7. Final termination of the project and force majeure

Mainnet may never be launched. This is possible as a result of an unfixable technical defect, the inability to ensure safe operation, the final loss of necessary resources or key infrastructure, a prohibition or requirement of a government authority, a change in applicable law, or a combination of technical, economic, operational, and regulatory circumstances that makes continuing the project impossible or commercially unreasonable.

A Force Majeure Event means an event beyond the Company's reasonable control that could not reasonably have been prevented or overcome, including a natural disaster, fire, flood, epidemic, war, terrorism, mass civil unrest, a prolonged large-scale failure of electricity, internet, cloud, or blockchain infrastructure, a large-scale cyberattack, a mandatory act, prohibition, or sanction of a government authority, and the termination of a critically important third-party service where no reasonably available replacement exists. A lack of funding, an ordinary change in market price, an internal decision to cease operations, or ordinary technical difficulty are not, by themselves, force majeure.

Force majeure suspends the affected performance only for the duration and to the extent of its effect. The Company must take commercially reasonable steps to mitigate the consequences and must publish on the official website material information about the effect of such an event, where publication is lawful and practically possible.

If, after commercially reasonable, good-faith efforts, the Company's board of directors determines that the safe launch of Mainnet is finally impossible, or that the project has no reasonable prospect of continuing, the Company may announce the project's final termination. The decision must be made in good faith, based on documented circumstances, and may not be made merely to extract remaining funds or to escape obligations. The Company publishes on morana.network a notice describing the principal reasons and, to the extent practically and legally possible, final information on the use of the proceeds.

On final termination of the project, MOR is not created and cannot be delivered, and RMOR loses its practical purpose and may have no value whatsoever. Because the proceeds are earmarked for development and are not reserved for refunds, the Company does not accept a contractual obligation to refund the purchase price in connection with the project not launching or being terminated, except where a refund is required by mandatory law or separately and expressly announced by the Company in writing. To the maximum extent permitted by mandatory law, the obligation of future MOR delivery terminates upon publication of the notice of final termination of the project.

2.8. Redemption

After Mainnet launches and redemption opens, the Buyer must:

1. obtain a compatible Morana address; 2. register it through the registry contract on the Base network; 3. verify the registered address before redemption; 4. call the redemption function, which irreversibly burns the corresponding RMOR; 5. wait for the Company to send MOR to the registered Morana address.

Burning RMOR and sending MOR occur on different networks and are not an atomic operation. A delay is possible between the burning of RMOR and the arrival of MOR. The Company must keep a verifiable log of claims and must fulfill valid claims in reasonable batches after redemption opens.

The Contract checks the format and checksum of the Morana address, but cannot confirm that the address belongs to the Buyer. MOR sent to a correctly formed but incorrect address may be irretrievably lost.

2.9. AML, sanctions, and source-of-funds verification

The Company does not plan to conduct standard prior identity verification of every Buyer as a technical condition for calling the Sale Contract.

The Company may request documents or information about identity, beneficial ownership, source of funds, or a specific transaction if:

• this is required by applicable law, a court, a regulator, a law-enforcement authority, a bank, or another obliged financial intermediary;
• the address or transaction is connected to a sanctions list or to a credible warning from a blockchain-analytics provider;
• the Company has reasonable grounds to suspect the criminal origin of funds, money laundering, terrorist financing, fraud, or sanctions evasion.

Pending completion of the check, the Company may restrict access through the Interface, place the sale on a general pause, and, to the extent permitted by mandatory law, temporarily suspend further off-chain performance of the affected operation. The Company may not finally appropriate assets solely on the basis of an unconfirmed suspicion; further action is determined by applicable law and the binding directions of competent authorities.

The Contracts do not allow the Company to block a particular address, cancel a completed purchase, seize RMOR from a Buyer's address, or guarantee the refund of USDC already transferred. The Buyer understands this technical limitation.

2.10. No general right of refund

Unless the mandatory law of a particular jurisdiction requires otherwise, a purchase of RMOR is final, and no general right of voluntary refund or withdrawal after a transaction is confirmed is provided, including where Mainnet launches later than the target period or the project is finally terminated under Section 2.7. Nothing in these Terms excludes a consumer's rights or other remedies that cannot be excluded by contract.

3. Taxation

3.1. The Buyer's tax obligations

The Buyer independently determines the tax consequences of participating in the sale and is responsible for the correct calculation, declaration, and timely payment of all taxes, duties, levies, mandatory charges, and interest applicable to them. These may arise in connection with the purchase, receipt, holding, valuation, redemption, use, transfer, or other disposal of RMOR or MOR, and from changes in their value or tax classification.

The tax treatment depends on the Buyer's country of tax residence, citizenship, location, status, and activity, the nature of RMOR and MOR, and the Buyer's subsequent actions. It may include, among other things, income tax, corporate or capital-gains tax, GST, VAT or a similar indirect tax, property, inheritance, or gift tax, withholding tax, and reporting obligations. Mentioning a possible tax does not mean it necessarily applies.

The Buyer must independently keep the necessary records, determine the value of assets in the applicable reporting currency on the relevant dates, file returns, and obtain professional tax advice if they need it.

3.2. Price and taxes on purchase

The price displayed by the Sale Contract is the amount of USDC transferred for the corresponding amount of RMOR and does not include the Buyer's network fee. The Company does not charge, through the Sale Contract, any separate tax on top of the displayed price.

If mandatory law requires the Company to charge the Buyer GST, VAT, or a similar tax on top of the price, the Company must disclose this before the relevant purchase and implement a lawful method of collecting it. No additional tax may be retroactively debited by the Sale Contract from the Buyer's wallet.

3.3. Withholding and providing information

The Company is not obliged to calculate, withhold, or remit tax on the Buyer's behalf, except where such an obligation is expressly imposed on it by applicable law. Where withholding is mandatory, the Company may withhold or remit the required amount and provide the Buyer with the available confirmation. The Company is not obliged to increase the payment or delivery of MOR to compensate for such mandatory withholding, unless applicable law or a separate written undertaking requires otherwise.

The Buyer must provide reasonably requested tax information and forms where the Company needs them to comply with mandatory reporting, withholding, or a government authority's request.

3.4. No tax advice and liability

The Company and persons connected with it do not provide the Buyer with tax advice and do not guarantee any tax classification or outcome. The Buyer must not treat the materials on the website, the Interface, or these Terms as individual tax advice.

To the maximum extent permitted by applicable law, the Buyer indemnifies the Company for reasonable, documented losses, assessments, and expenses arising from claims by a tax authority or a third party that directly arise from the Buyer's failure to fulfil their own tax obligations, from the Buyer providing materially incorrect tax information, or from an unlawful demand by the Buyer that the Company not carry out mandatory withholding. This does not extend to the Company's own taxes, its own miscalculation, or its own breach of applicable law.

3.5. The Company's taxes

The Company is independently responsible for its own taxes, accounting, and mandatory reporting. The tax treatment of the sale proceeds depends on the actual rights and functions of RMOR and on applicable law; these Terms do not establish the tax classification of the proceeds, RMOR, or MOR.

4. Risks

The purchase of RMOR, the development and launch of Mainnet, and the subsequent receipt and use of MOR involve significant risks. The list below is not exhaustive. By accepting the Terms, the Buyer confirms that they have independently assessed and accept these risks.

4.1. Project and Mainnet-launch risks

Development may encounter a shortage of funding or personnel, delays, architectural errors, failed tests, third-party software dependency problems, disagreements among participants, forks, attacks, the cessation of contractors' work, or other circumstances. Mainnet may launch later than the target period, with different features, or may never launch at all. The project may be suspended, materially changed, or terminated. The proceeds may be fully spent on good-faith development without reaching launch. On final termination under Section 2.7, the Buyer may receive neither MOR nor a refund of the purchase price and may lose the entire amount paid.

4.2. Regulatory risks

Rules relating to blockchain, digital assets, tokens, payments, securities, consumer protection, and sanctions/AML-CFT differ between countries and may change. A government authority may classify RMOR or MOR as a security, a debt instrument, a collective investment scheme, a payment token, a financial product, or another regulated instrument, regardless of its description or intended function.

Regulatory action may delay, restrict, change, or prohibit the sale, the launch of Mainnet, redemption, or the transfer or use of MOR in one or more jurisdictions. The Company may be forced to change the Network's features, restrict the Interface, stop offering to particular persons, or comply with a government authority's mandatory directive.

4.3. Tax risks

Purchasing, holding, redeeming, receiving, using, or subsequently transferring MOR may have unforeseen tax consequences. The tax treatment may change or differ from the Buyer's expectations. The Buyer bears the risk of penalties, interest, and other consequences of incorrect reporting.

4.4. Malicious-conduct risks

The Contracts, the Interface, the domain, DNS, the domain registrar, hosting, the repository, wallets, RPC, and other infrastructure may become the target of phishing, website spoofing, social engineering, malware, key theft, DDoS, malicious-code injection, exploitation of vulnerabilities, or compromise of a service provider.

An attacker may create a fake interface, contract address, project account, or similarly named token. Interacting with such an object may lead to the irreversible loss of assets.

4.5. Technical risks

Smart contracts, client software, and the Network are experimental systems and may contain known or unknown bugs, defects, incompatibilities, and vulnerabilities. Audits, testing, open-source code, and formal verification reduce but do not eliminate these risks.

The Base network or Morana may stop, reorganize, split, come under attack, or change its rules. A transaction may be delayed, not included, executed with an unexpected result, or require a higher fee. Third-party wallets, RPC providers, explorers, and other infrastructure may show inaccurate or outdated information.

4.6. Private-key, wallet, and address risks

Access to RMOR is determined by the private key of the corresponding address. Loss, theft, or compromise of the key, seed phrase, password, or device may lead to the irreversible loss of RMOR and of the practical ability to call redemption. The Company does not hold the Buyer's keys, cannot restore access, and cannot move RMOR to a new address.

The Contract can check the format and checksum of a Morana address, but not ownership of it. An error in selecting a correctly formed address may lead to the irreversible sending of MOR to another person.

4.7. USDC, Base network, and transaction-finality risks

USDC depends on its issuer, applicable regulation, reserves, banking partners, its smart contract, and the Base network. USDC may lose its peg, be frozen by the issuer, or become unavailable. The Company does not control Circle or the Base network.

An incorrect amount, the wrong network, an incorrect contract, an insufficient fee, an erroneous approve allowance, a front-end attack, or another error by the Buyer may lead to failure or irreversible loss. A confirmed blockchain transaction generally cannot be reversed by the Company.

4.8. Redemption and cross-network-delivery risks

Burning RMOR on Base happens before MOR is sent on the Network and cannot be combined with it into a single atomic transaction. Processing delays, technical errors, the need to re-verify data, congestion, or a stoppage of one of the networks are possible. After burning RMOR, the Buyer depends on the Company's proper off-chain performance.

4.9. Market and liquidity risks

RMOR is non-transferable and has no secondary market. The Company does not promise that a market, a listing, liquidity, or any value will emerge for MOR. The price of MOR may be extremely volatile or equal to zero. The Buyer may lose the entire amount paid and the fees incurred.

4.10. Publicity and privacy risks

The Buyer's address, purchase amount, and subsequent actions are visible on the public Base network. Registration creates a permanent public link between the EVM address and the Morana address. Analytics services, counterparties, or third parties may link these addresses to the Buyer's identity. The Company cannot delete data from a public blockchain.

5. Limitation of liability

To the maximum extent permitted by mandatory law, neither Party is liable to the other for indirect, incidental, special, punitive, or consequential damages, including lost profits, loss of business opportunity, data, reputation, or expected token value, arising out of these Terms, the sale, the Contracts, the Interface, RMOR, MOR, or the Network.

The Company's aggregate liability to a particular Buyer for all related claims, regardless of the basis, does not exceed the price actually paid by that Buyer for the corresponding RMOR purchase.

These limitations do not apply to liability that cannot be excluded or limited by mandatory law, including applicable cases of fraud, gross negligence, willful breach, or death or personal injury. Nothing in this Section turns the expressly established obligation to deliver MOR after Mainnet launches and valid redemption occurs into a right of the Company to decline performance at its discretion. This does not limit the expressly disclosed consequences of the project's final termination under Section 2.7.

6. Indemnification of the Company

To the extent permitted by applicable law, the Buyer indemnifies the Company, its directors, officers, employees, and contractors for reasonable, documented losses and expenses arising from third-party claims directly caused by:

• a material breach by the Buyer of these Terms or of the Buyer's representations and warranties;
• unlawful use of the Contracts or the Interface;
• the Buyer's violation of a third party's rights or of law applicable to the Buyer.

The Company must promptly notify the Buyer and give them a reasonable opportunity to participate in the defense. The Company may not agree to an admission of liability or a settlement at the Buyer's expense without the Buyer's reasonable participation, except to comply with a mandatory directive of a government authority.

7. Disclaimer of warranties by the Company

To the maximum extent permitted by mandatory law, and except for the obligations expressly established by these Terms, RMOR, the Contracts, the Interface, and related technical components are provided on an as-available basis, without additional express, implied, or statutory warranties.

In particular, the Company does not warrant:

• the continuity, error-free operation, security, currency, or compatibility of the Contracts, the Interface, Base, Morana, or third-party infrastructure;
• that all defects will be fixed, or the absence of viruses, malicious code, and unknown vulnerabilities;
• the exact timing of Mainnet launch, or that the Network's features, architecture, and economics will remain unchanged;
• particular features, performance, or availability of MOR after launch;
• the future price, stability, liquidity, listing, or existence of a market for MOR;
• the absence of forks, reorganizations, duplication, stoppage, or change of the networks it relies on;
• a particular regulatory or tax classification of RMOR or MOR in any jurisdiction;
• the operation of wallets, RPC providers, explorers, USDC, Circle, and other independent products or services.

Some jurisdictions do not permit the exclusion of certain warranties or implied conditions, in particular in dealings with consumers. In that case, this Section applies only to the extent permitted. It does not exclude the Company's expressly established obligation under these Terms to deliver MOR after Mainnet launches and RMOR is validly redeemed, and it applies subject to the expressly disclosed consequences of the project's final termination under Section 2.7.

8. Buyer's representations, warranties, and acknowledgements

8.1. Capacity and authority

The Buyer confirms their legal capacity, authority, and the lawfulness of their participation under Section 1. If the Buyer is a legal entity, entering into and performing these Terms has been duly approved and does not violate its constitutional documents or its obligations to third parties.

8.2. Acknowledgements

The Buyer acknowledges and confirms that:

• these Terms and the website's materials are not represented by the Company as a prospectus, an investment memorandum, personal advice, or a guarantee that RMOR or MOR will be admitted to offering in any jurisdiction;
• they have independently studied the Terms, the available technical materials, the code, and the risks, and are not relying on oral promises, unofficial communications, a price forecast, or any statement not included in the Terms;
• purchasing RMOR does not confer shares, equity, corporate control, dividends, interest, a right to proceeds, intellectual property, or any other proprietary interest in the Company;
• the purchase price is not transferred to the Company for investment or management on the Buyer's behalf, and the use of the proceeds does not give the Buyer a right to profit or to the results of the Company's activity;
• RMOR confers only the rights expressly described in these Terms;
• a regulator may classify RMOR or MOR differently from what the Company intends;
• the Contracts can be called directly, so restricting the Interface does not guarantee that a particular person or transaction is blocked;
• the Company may place the sale on a general pause, restrict the Interface, or comply with a government authority's mandatory directive, but cannot technically reverse a purchase that has already been completed;
• RMOR is non-transferable, the risk may persist until redemption or the project's final termination, and in the event of termination the Buyer may lose the entire amount paid without receiving MOR;
• all information they have provided to the Company is accurate, complete, and current.

8.3. Sophistication and technical understanding

The Buyer confirms that they have knowledge and experience sufficient to understand:

• the operation of blockchains, smart contracts, tokens, wallets, private keys, and seed phrases;
• the Base network, USDC, ERC-20 approvals, network fees, and transaction finality;
• the difference between RMOR, the future MOR coin, and a wrapped asset;
• the non-transferability of RMOR and the impossibility of recovering a lost key;
• the non-atomic nature of burning RMOR and the subsequent delivery of MOR on a different network;
• the technical, economic, regulatory, tax, and market risks described in Section 4.

The Buyer is able to independently assess the purchase and bear the total loss of the amount paid without harm incompatible with their financial position. Where necessary, they have obtained independent legal, tax, technical, and financial advice, or have knowingly decided to proceed without it.

9. Data and privacy

The Company does not plan to routinely collect documents and identifying information from every Buyer. Public blockchains, however, automatically disclose addresses and transaction details.

If, in the cases described in Section 2.9, the Company obtains personal data, it is processed only to the extent necessary for verification, performing a legal obligation, protecting legitimate interests, and interacting with the relevant service providers or authorities. The terms of processing must be described in a privacy notice published on morana.network: <EXACT LINK TO THE PRIVACY NOTICE>.

The Company cannot change or delete information already recorded on a public blockchain.

10. Miscellaneous

10.1. Entire agreement and severability

These Terms, together with any documents expressly incorporated into them by reference, constitute the entire agreement of the Parties regarding the sale of RMOR and supersede prior oral and written discussions, communications, and statements on this subject.

If any provision is held invalid, unlawful, or unenforceable, in whole or in part, the remaining provisions continue in effect. An invalid provision applies to the maximum extent permitted, or is replaced by a valid provision that most closely reflects its lawful commercial purpose.

10.2. Class-action waiver

To the maximum extent permitted by applicable mandatory law, the Buyer agrees to bring claims against the Company only in their own name and waives the right to participate as a plaintiff, class member, or representative in any class, group, or representative action or proceeding relating to the sale, RMOR, MOR, the Contracts, the Interface, or these Terms.

This waiver does not limit the powers of a government authority and does not apply where the right to a class or representative remedy cannot lawfully be waived by contract. If the waiver is unenforceable in a particular jurisdiction or dispute, this does not affect the remaining provisions of the Terms.

10.3. Governing law and dispute resolution

These Terms and any related non-contractual claims are governed by the law of Singapore, without regard to its conflict-of-laws rules.

Unless the mandatory law of the Buyer's country requires otherwise, the courts of Singapore have exclusive jurisdiction over disputes. Before going to court, a Party must send the other Party written notice and allow at least 30 days for a good-faith resolution of the dispute.

10.4. Amendments, succession, and assignment of obligations

The Company may amend the Terms only prospectively, to fix an error, comply with the law, or reflect a technical change. An amendment may not retroactively reduce the amount of MOR owed for RMOR already acquired, cancel a Buyer's valid claim, or increase a price already paid. Material amendments are published together with their effective date.

Each purchase is governed by the version of the Terms published at the time the corresponding transaction is confirmed. The Company must maintain an accessible archive of prior versions on the official website, with their dates of effect and separate permanent links, so that the Buyer can determine the edition applicable to their purchase.

The Company may transfer the project and its RMOR obligations to a successor as part of a reorganization only if the successor accepts the corresponding obligations in writing and the Buyer's rights are not impaired. The Company publishes information about the successor and the date of transfer. This does not guarantee the feasibility of a corporate redomiciliation and does not waive any mandatory consents or procedures.

10.5. Official website and notices

The project's official website is https://morana.network/. All official project information intended for public disclosure is published on this website, including information about the sale, Contract addresses, development progress, the Mainnet launch, the opening of redemption, changes to the Terms, and succession.

Unless mandatory law requires individual notice, publication on the website is deemed official notice to the Buyer. The Buyer must independently check the website and verify Contract addresses before a transaction. The Company will never ask for a private key or seed phrase.

Before the sale begins, the same canonical link, version number, and effective date of these Terms must be posted on the Sale Interface and on the verified Sale Contract's page on the block explorer. A new edition must be published as a new version at a separate permanent link. Changing the current page does not change the Terms applicable to a purchase already made.

Addresses to verify before purchasing:

• RMOR (MoranaClaim): 0x08f712aD1dC2F33d66A5a7FDb83C7a36e1A06C03;
• Sale Contract (MoranaSale): 0x4103Ebb6A855E774a18AC71f4d6B416ee3107892;
• Registration/Redemption Contract (MoranaRedeemer): 0x453F6824EEd658c7fAD385dBF1b2A9E4B2f56Ed8;
• native Circle USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (chain ID 8453; verified against circle.com/usdc, the EIP-55 checksum matched, name() = "USD Coin", decimals() = 6; this is NOT the bridged USDbC at 0xd9aAEc86B65D86f6A7B5B1b0c42FFA531710b6CA, which is not accepted).

10.6. No waiver, headings, and language

Failure or delay in exercising a right does not constitute a waiver of it. Headings are for convenience only and do not affect the interpretation of the Terms.

If a translation diverges from the version the Company designates as legally prevailing, the prevailing version applies, subject to the mandatory law applicable to the Buyer. Before publication, such a version must be designated and posted on morana.network.