# Eureka Nexus — Technical White Paper Version: **Pre-Launch Technical Draft 2026** Status: **PUBLIC TECHNICAL DOCUMENT — EKNX GENESIS MARKET LIVE ON-CHAIN** Project: **Eureka Nexus** Origin: **Portugal 🇵🇹** Official website: https://eurekanexus.pt Official GitHub: https://github.com/Eureka-Nexus Official contact: `official@eurekanexus.pt` --- # Important notice This document describes the Eureka Nexus technology, ecosystem, EKNX framework and current development direction. It is a technical and informational document. It is not represented as: - an approved regulatory prospectus; - a completed MiCA crypto-asset white paper; - investment advice; - financial advice; - tax advice; - legal advice; - a guarantee of token value; - an active public token offer. The EKNX Launch Curve and planned DEX transition are currently: **PLANNED — NOT ACTIVE** Any legally required final crypto-asset white paper, notification, publication or other regulatory documentation must be completed before the applicable public market activation. --- # 1. Executive summary Eureka Nexus is a Portuguese technology project developing an ecosystem that combines artificial intelligence, personal digital identity, distributed computation, mining infrastructure and EKNX. The project is built around several connected layers: 1. Eureka AI 2. Eureka 2026 Miner 3. Eureka Nexus Mining Network 4. EKNX 5. Automatic mining payout infrastructure 6. Future Launch Curve 7. Future decentralised exchange liquidity 8. Future Eureka applications and agents The project's objective is broader than launching a crypto-asset. Eureka Nexus aims to build a persistent digital intelligence ecosystem where each user can progressively shape their own Eureka. EKNX is intended to operate as one economic and utility layer within that broader ecosystem. --- # 2. Project vision ## 2.1 Beyond Crypto. Beyond AI. Eureka Nexus is based on the idea that digital intelligence should be capable of developing continuity over time. Instead of every user receiving an identical temporary chatbot, the long-term Eureka architecture is intended to allow a user to shape a persistent digital entity through: - identity; - appearance; - personality; - voice; - memory; - goals; - permissions; - knowledge; - tools; - experiences; - specialised agents. The project refers to this direction as a digital being or persistent digital intelligence. This terminology describes the product vision. Eureka Nexus does not claim that the current system is conscious, sentient or biologically alive. --- # 3. Eureka AI ## 3.1 Personal digital identity Eureka AI is being developed so that individual users can define their own Eureka. Planned and prototype identity elements include: - Name - Adult age profile - Gender / presentation - Appearance - Voice - Personality - Communication style - Role - Goals - Boundaries - Capabilities - Degree of permitted autonomy --- ## 3.2 Visual identity The Eureka identity architecture is being designed around a persistent canonical visual identity. The intended workflow is: 1. User creates an Eureka profile 2. User describes the desired appearance 3. A temporary visual preview is generated 4. User may regenerate another preview 5. User confirms the preferred identity 6. The system preserves a canonical identity representation 7. A persistent reference is associated with that identity 8. Future Eureka applications may recover the same profile and visual identity Production authentication and recovery mechanisms remain under development. A simple public reference code must not be treated as production-grade authentication until the final recovery architecture is implemented. --- ## 3.3 Memory and continuity The long-term architecture is intended to support memory such as: - Projects - Decisions - Preferences - Events - Goals - User instructions - Learned context - Previous interactions - Relevant experiences The objective is continuity instead of restarting from zero in every interaction. --- ## 3.4 Voice Eureka is intended to support natural voice interaction. Planned architecture includes: - Speech input - Speech output - Voice selection - User-defined voice characteristics - Real-time conversational interaction --- ## 3.5 Permission-based vision Future Eureka versions may use visual context through devices such as a webcam only when explicitly permitted by the user. Possible uses include: - Understanding objects - Visual context - Assisting with tasks - Interaction with the user's environment Camera access must remain permission-based. --- ## 3.6 Tools and agents The Eureka architecture is intended to support specialised capabilities and agents. Potential areas include: - Research - Coding - Planning - Creativity - Automation - File interaction - Application interaction - Web research - Business support - Market analysis - Personal productivity Capabilities should only be described as LIVE when they are genuinely operational. --- ## 3.7 Persistent digital environment The long-term vision includes persistent Eureka environments that may continue to maintain state even while the user's primary computer is offline. This is a development objective. It should not be interpreted as a claim that all Eureka instances currently operate continuously. --- # 4. Existing technical foundation Eureka Nexus has already deployed several operational components. These include: - EKNX on BNB Smart Chain Mainnet - Eureka Nexus Mining Server - Public mining network endpoints - CPU mining - GPU mining - Server-side share validation - Reward accounting - Automatic EKNX payouts - Eureka 2026 Miner - Public project website - Public technical documentation --- # 5. EKNX ## 5.1 Network EKNX operates on: **BNB Smart Chain Mainnet** Chain ID: `56` Decimals: `18` Token symbol: `EKNX` --- ## 5.2 Official token contract Official EKNX contract: `0xF54913A8d5E2AEBD0B62c6411cCf1b5B4aB069c9` Users should independently verify the contract through official project sources and BscScan. --- # 6. EKNX supply framework Maximum supply framework: | Allocation | Maximum | |---|---:| | Market Reserve | 1,000,000 EKNX | | Mining / reward capacity | 99,000,000 EKNX | | Maximum supply | 100,000,000 EKNX | Maximum supply is not the same as circulating supply. The mining allocation must not be interpreted as 99,000,000 EKNX already circulating. Mining-related issuance follows the official mining and reward architecture. --- # 7. Eureka Nexus Mining Network ## 7.1 Purpose The Mining Network provides computational participation and the reward layer associated with EKNX mining. --- ## 7.2 Mining algorithms CPU: `RANDOMX-EUREKA-V1` GPU: `KAWPOW-EUREKA-V1` --- ## 7.3 Eureka 2026 Miner Current official public release: **Eureka 2026 1.0** Software version: `2026.1.0` Supported public platforms: - Windows x86-64 - Linux x86-64 Official releases: https://github.com/Eureka-Nexus/eureka-miner/releases --- ## 7.4 Mining economics Current official pool rule: - Miner: **99%** - Project fee: **1%** --- ## 7.5 Automatic payouts Eureka Nexus uses automatic EKNX payout infrastructure. The public Miner does not require a user to execute a manual on-chain claim transaction. Current production payout threshold: **5 EKNX** Users only need to provide their public BNB Smart Chain wallet address for mining reward attribution. The official Miner must never require a seed phrase or private key. --- # 8. Public network infrastructure Official public network endpoints currently include: Health: `https://pool.eurekanexus.pt/health` Network information: `https://pool.eurekanexus.pt/v1/network` Public statistics: `https://pool.eurekanexus.pt/v1/public/stats` These endpoints are intended to expose public operational information. Administrative credentials and signing secrets must remain private. --- # 9. Market Reserve The EKNX Market Reserve is: **1,000,000 EKNX** The Market Reserve is intended for the future public market architecture. Current status: **COMING SOON — NOT ACTIVE** Publication of the Market Reserve or planned market parameters does not mean that a public Launch Curve is currently active. --- # 10. Planned Launch Curve Current planned allocation: - Up to **650,000 EKNX** for the Launch Curve - **350,000 EKNX** preserved for the future DEX / liquidity stage The final allocation remains subject to launch validation. --- ## 10.1 Pricing model The current intended design uses a continuous progressive curve. The design avoids artificial fixed price tiers such as: - €5 - €10 - €15 The intended price should progress continuously according to the final curve formula and market state. Current pricing model: **Price is calculated live on-chain by the deployed Genesis bonding curve** This is a planned launch parameter. It is not a guarantee of future market value. The final mathematical formula, slope, limits and contract parameters must be published before activation. --- ## 10.2 Launch Curve objective The present project direction is to attempt to distribute the Launch Curve allocation progressively through market demand before the planned DEX transition. Eureka Nexus does not guarantee that: - All Launch Curve EKNX will be purchased - The Launch Curve will complete - Demand will reach a specific level - EKNX will appreciate - A future DEX price will exceed any Curve price --- # 11. Planned payment architecture The Launch Curve is intended to operate on BNB Smart Chain. Payment execution must therefore use assets and token contracts compatible with BNB Smart Chain. Current design direction may support: - BNB - USDT on BNB Smart Chain - USDC on BNB Smart Chain - Compatible BNB Smart Chain representation of ETH - Compatible BNB Smart Chain representation of BTC The exact supported token contracts, routers and conversion mechanisms must be verified and published before activation. Users must never assume that a token with the same symbol on another network is automatically supported. Sending assets through an unsupported blockchain or unsupported token contract may result in loss of funds. --- # 12. Planned use of Launch Curve proceeds Current planning framework: - **70% — liquidity / future DEX market structure** - **30% — Eureka Nexus development, infrastructure and operations** The 70% allocation is intended to support future liquidity and the market-transition architecture. The 30% allocation is currently intended to support areas such as: - Eureka AI development - Infrastructure - Servers - Mining systems - Security - Software development - Research - Operations - Ecosystem development This is a planning framework. Final treasury routing, accounting treatment and legally required disclosures must be established before public activation. --- # 13. Future DEX reserve From the 1,000,000 EKNX Market Reserve, the current architecture intends to preserve: **350,000 EKNX** for the future DEX / liquidity stage. Current planned Market Reserve structure: | Purpose | Planned allocation | |---|---:| | Launch Curve | Up to 650,000 EKNX | | Future DEX / liquidity reserve | 350,000 EKNX | | Total Market Reserve | 1,000,000 EKNX | The final configuration must be verified on-chain before market activation. --- # 14. Genesis Curve to DEX graduation The current market architecture is: **Launch Curve → liquidity preparation → DEX** The Launch Curve is intended to provide the initial continuous market mechanism for the planned EKNX market launch. A later stage is intended to transition market activity toward a decentralised exchange environment. The final transition mechanism is not active yet. Before a DEX transition, Eureka Nexus intends to publish and verify: - Selected DEX - Official trading pair - Liquidity amount - Pool contract - EKNX token contract - Liquidity addresses - Treasury routing - Migration mechanism - Relevant transaction hashes - Official public links No unofficial liquidity pool should be considered an official Eureka Nexus market solely because it contains an EKNX trading pair. --- # 15. Market price and liquidity risks A decentralised exchange price is determined by market mechanisms. Eureka Nexus does not guarantee: - Initial DEX price - Future DEX price - Liquidity depth - Trading activity - Trading volume - Ability to sell a specific amount - Absence of slippage - Appreciation - Profit - Return on investment Liquidity can increase or decrease. Market value can rise or fall. Large transactions may experience significant slippage when liquidity is limited. The existence of a DEX pool does not guarantee that users will always be able to buy or sell EKNX at a desired price. --- # 16. Official market verification Before interacting with a future EKNX market, users should verify: - Official EKNX contract - Official Launch Curve contract - Official payment-token contracts - Official DEX - Official trading pair - Official liquidity pool - Official project links Official information should be checked through: - https://eurekanexus.pt - https://github.com/Eureka-Nexus - BscScan for BNB Smart Chain transactions and contracts Users should not rely only on: - Direct messages - Social-media comments - Unofficial groups - Unverified contract addresses - Unofficial liquidity pools --- # 17. EKNX utility direction EKNX is intended to operate as an economic and utility layer within the broader Eureka Nexus ecosystem. Potential future uses may include eligible: - Eureka AI services - Subscriptions - Agent services - Digital services - Ecosystem applications - Mining-related functions - Software features - Other Eureka Nexus products A planned utility must not be considered operational until the related product or service is genuinely deployed. Future utility does not guarantee market value. --- # 18. Relationship between EKNX and Eureka AI Eureka AI and EKNX are separate but potentially connected layers. Eureka AI represents the artificial-intelligence, identity, memory, agent and digital-environment architecture. EKNX represents a blockchain-based economic and utility layer. EKNX does not define the intelligence, capability or quality of Eureka AI. Future Eureka products may integrate eligible EKNX functions. Those integrations must be separately documented before activation. --- # 19. Eureka Nexus ecosystem structure The Eureka Nexus ecosystem is organised into three main layers: ## Eureka AI - Identity - Appearance - Memory - Voice - Permission-based vision - Tools - Applications - Agents ## Mining Network - CPU mining - GPU mining - Share validation - Reward accounting - Automatic EKNX payouts ## EKNX - Mining / reward capacity - Market Reserve - Planned Launch Curve - Future DEX reserve - Future ecosystem utility These layers are connected but should not be confused with one another. Eureka AI is the digital-intelligence layer. The Mining Network is the computational and reward infrastructure. EKNX is the blockchain-based economic and utility layer. --- # 20. Current product status Eureka Nexus distinguishes operational components from demonstrations, development work and future plans. | Component | Status | |---|---| | EKNX contract on BNB Smart Chain | LIVE | | Market Reserve / Genesis Market contract | LIVE | | Eureka Nexus Mining Server | LIVE | | CPU mining | LIVE | | GPU mining | LIVE | | Server-side share validation | LIVE | | Mining reward accounting | LIVE | | Automatic EKNX payouts | LIVE | | Public mining network endpoints | LIVE | | Eureka 2026 Miner Windows | LIVE | | Eureka 2026 Miner Linux | LIVE | | Eureka Nexus Website 2026 | LIVE | | Eureka AI browser profile prototype | LIVE DEMO | | Eureka AI final public product | IN DEVELOPMENT | | Persistent Eureka memory architecture | IN DEVELOPMENT | | Photorealistic Eureka identity service | IN DEVELOPMENT | | Production-grade identity recovery | IN DEVELOPMENT | | Persistent 24/7 Eureka environment | IN DEVELOPMENT | | Eureka AI Capital Agent | IN DEVELOPMENT | | EKNX Launch Curve | PLANNED / NOT ACTIVE | | Public EKNX Curve sale | NOT ACTIVE | | Launch Curve payment gateway | PLANNED | | DEX transition | PLANNED | | Official EKNX DEX liquidity pool | NOT ACTIVE | | Eureka mobile applications | PLANNED / IN DEVELOPMENT | A component marked PLANNED, NOT ACTIVE or IN DEVELOPMENT must not be represented as an operational production service. A LIVE DEMO indicates functioning demonstration functionality but does not mean that the complete production service is available. --- # 21. Public transparency principle Eureka Nexus documentation must clearly distinguish between: - Operational production infrastructure - Browser or local demonstrations - Components under development - Planned future functionality - Components that are not yet active A feature must not be represented as LIVE solely because it appears in documentation, source code, a prototype or a development branch. The same transparency rule applies to: - Eureka AI - Mining infrastructure - EKNX - Launch Curve - DEX - Mobile applications - Agents - Payment systems - Market infrastructure Production status should be supported by actual deployment and official public verification. --- # 22. Technical risks Eureka Nexus depends on multiple software and blockchain components. Technical risks may include: - Software defects - Smart-contract defects - Network outages - RPC failures - Mining-server failures - Database failures - Dependency vulnerabilities - Configuration errors - Compatibility problems - Hardware failures - Cybersecurity incidents No software system can be guaranteed to operate without interruption or without vulnerabilities. --- # 23. Smart-contract risks Blockchain smart contracts can contain implementation errors, unexpected behaviour or vulnerabilities. Potential risks include: - Access-control failures - Incorrect token accounting - Incorrect market calculations - Incorrect treasury routing - Incorrect liquidity routing - Reentrancy or interaction risks - Dependency or router risks - Upgrade or administration risks - Configuration mistakes Future Launch Curve or DEX-related contracts should undergo appropriate testing and review before public activation. Official contract addresses must be published through official Eureka Nexus sources. --- # 24. Mining risks Mining depends on software, hardware, network connectivity and server infrastructure. Risks may include: - Rejected shares - Temporary server unavailability - Hardware instability - Driver incompatibility - High electricity consumption - GPU or CPU overheating - Incorrect wallet configuration - Network interruptions - Reward-accounting defects Mining rewards are not guaranteed. Actual rewards may vary according to network rules, validated work, technical conditions and future protocol changes. --- # 25. Wallet and custody model The official Eureka Nexus Miner is designed to use a public BNB Smart Chain wallet address for reward attribution. The official Miner must never require: - Seed phrase - Private key - Wallet recovery phrase - Exchange password - Exchange API secret Users remain responsible for securing their own wallets and recovery credentials. Loss of a private key or recovery phrase may result in permanent loss of access to blockchain assets. --- # 26. Automatic payout security Automatic payout infrastructure must keep signing material private. Sensitive infrastructure may include: - Relayer signing keys - Operator credentials - Private RPC credentials - Administrative tokens - Infrastructure passwords These must not be exposed in: - Public GitHub repositories - Website JavaScript - HTML - Public API responses - Public documentation Public payout information should expose only data intended for public verification. --- # 27. Privacy and personal data Eureka Nexus intends to minimise unnecessary collection of personal data. Future Eureka services may process information selected or provided by the user in order to provide personalised functionality. Depending on the service, this may include: - Profile information - Preferences - Voice settings - Generated identity data - User-created memories - Files voluntarily provided by the user - Application permissions - Service configuration Production services must define the applicable privacy rules before public activation. --- # 28. Eureka digital identity data The Eureka identity architecture may process: - User-selected profile attributes - Appearance descriptions - Generated character images - Canonical identity references - Personality settings - Voice preferences - User-selected roles and capabilities Production deployment must define: - Purpose of processing - Data controller information - Legal basis where applicable - Storage rules - Retention periods - Deletion mechanisms - Access and correction mechanisms - Security controls - Third-party processors where applicable Private user identity data must not be committed to public GitHub repositories. --- # 29. Camera and microphone permissions Future Eureka capabilities may use: - Microphone input - Camera or webcam input - Visual environmental context These capabilities must be permission-based. Access to camera or microphone should not be treated as permanently granted merely because a user enabled it once. Production applications should provide clear user controls for enabling and disabling these permissions. --- # 30. AI memory and user control Persistent memory is part of the long-term Eureka architecture. Memory may include information such as: - User preferences - Projects - Goals - Previous decisions - Relevant conversation context - User-selected persistent information Production memory systems should provide appropriate controls for: - Viewing stored information - Correcting information - Deleting information where applicable - Controlling what is retained - Controlling what is used by Eureka Persistent memory must not be interpreted as unlimited permission to collect unrelated user information. --- # 31. Sustainability and environmental considerations Eureka Nexus uses blockchain and mining infrastructure that can consume electrical energy and computing resources. The environmental impact depends on factors such as: - Mining hardware - Hardware efficiency - Electricity consumption - Duration of mining activity - Energy source - Server infrastructure - Network usage - Geographic energy mix The project should not publish environmental-impact figures unless they are based on verifiable measurements or an appropriate methodology. --- # 32. Mining energy use CPU and GPU mining consume electrical energy. Actual consumption varies according to: - CPU model - GPU model - Power limits - Mining configuration - Cooling - Driver configuration - Hardware efficiency - Operating time Users are responsible for evaluating: - Electricity cost - Hardware temperature - Cooling requirements - Equipment wear - Local energy conditions Mining profitability is not guaranteed. --- # 33. Hardware efficiency The Eureka Nexus ecosystem should encourage efficient use of computing resources. Potential efficiency measures may include: - Appropriate power limits - Efficient hardware configuration - Temperature monitoring - Avoidance of unnecessary computation - Server optimisation - Software optimisation - Efficient network communication These measures may reduce energy use but do not eliminate environmental impact. --- # 34. BNB Smart Chain environmental dependency EKNX operates on BNB Smart Chain. Part of the environmental footprint associated with EKNX transactions therefore depends on the operation and infrastructure of BNB Smart Chain. Eureka Nexus does not control the complete underlying blockchain infrastructure. Changes to the underlying network may affect: - Energy characteristics - Transaction processing - Fees - Availability - Performance --- # 35. Environmental disclosure methodology Before any legally required environmental disclosure is finalised, Eureka Nexus should determine the applicable methodology and data requirements. Where required, the project should document: - Measurement methodology - Data sources - Relevant time period - Infrastructure included - Infrastructure excluded - Assumptions - Limitations - Material environmental indicators Estimated values must be clearly identified as estimates. Measured values must identify the measurement basis. --- # 36. No unsupported sustainability claims Eureka Nexus should not describe the project as: - Carbon neutral - Zero emission - Environmentally neutral - Green mining - Sustainable mining unless the relevant claim can be supported by appropriate evidence. Environmental communications should remain factual, measurable and capable of verification. --- # 37. Project governance Until a separate governance mechanism is formally implemented and published, Eureka Nexus project decisions are managed through the official project maintainership. No decentralised governance or token-holder voting mechanism should be assumed unless it is explicitly deployed and documented. Official production behaviour is defined by verified releases, production infrastructure and official public documentation. A proposal, branch, issue or pull request does not automatically become an official Eureka Nexus decision. --- # 38. Intellectual property Original Eureka Nexus material is governed by the applicable repository licence, copyright notices and applicable law. This may include original: - Source code - Architecture - Documentation - Website material - Interfaces - Visual design - Protocol implementations - Eureka AI implementations - Mining integrations - EKNX-related technical work Public visibility of source code does not automatically make the project open source. Third-party materials remain subject to their own licences and copyright terms. See: - `LICENSE` - `COPYRIGHT.md` - `NOTICE.md` - `docs/IP-AND-GOVERNANCE.md` --- # 39. Official maintenance and releases Official software releases should be distributed through verified Eureka Nexus channels. Release practices should include, where appropriate: - Version numbers - Release notes - Platform identification - Checksums - Verified download locations - Security review - Reproducible release information where practical Users should avoid software distributed through unofficial mirrors or unknown third parties. --- # 40. Project roadmap The Eureka Nexus roadmap represents current project direction. It does not guarantee delivery dates. Current major development stages include: ## Operational foundation - EKNX on BNB Smart Chain - Mining Server - CPU mining - GPU mining - Automatic EKNX payouts - Public network data - Eureka 2026 Miner ## Eureka AI development - Persistent identity - Photorealistic character identity - Voice - Memory - Permission-based vision - Tools - Applications - Agents - Automation - Persistent digital environment ## EKNX market development - Final Launch Curve formula - Curve smart-contract validation - Security review - Market launch legal gate - Payment-token validation - Public Launch Curve activation - Liquidity preparation - Future DEX transition ## Future ecosystem - Eureka AI Capital Agent - Mobile applications - Additional Eureka agents - EKNX ecosystem utility - Additional integrations --- # 41. Project continuity Eureka Nexus is being developed as an evolving modular ecosystem. Software, infrastructure and documentation may change as the project develops. Future versions may: - Improve architecture - Replace components - Add capabilities - Remove obsolete functionality - Improve security - Change implementation details - Introduce new applications Such changes must not silently alter published financial or market conditions that require explicit disclosure. --- # 42. Change-control principle Material changes affecting EKNX market architecture should be clearly documented before activation. This includes material changes to: - Maximum supply framework - Market Reserve - Mining economics - Launch Curve allocation - Curve formula - Payment assets - Treasury routing - Liquidity allocation - DEX transition - Market terms Development plans can evolve. Active market rules must remain publicly identifiable and verifiable. --- # 43. Regulatory framework Eureka Nexus is developed in the European Union and the future public market architecture must be assessed against applicable European and national law. A principal regulatory framework requiring assessment is: **Regulation (EU) 2023/1114 on Markets in Crypto-Assets (MiCA)** This technical White Paper does not itself determine the final legal classification of EKNX. Before public market activation, qualified legal analysis must determine whether EKNX and the planned activity fall within: - MiCA Title II; - another MiCA crypto-asset category; - an applicable exemption; - another European or national regulatory framework; - or an exclusion from MiCA. The classification must be completed before relying on any exemption or launch route. --- # 44. Public-offer requirements Where the planned EKNX public offer is subject to MiCA Title II without an applicable exemption, the launch process must address the applicable requirements of Regulation (EU) 2023/1114. These may include: - Legal-person requirements applicable to the offeror - Crypto-asset white paper - Notification to the competent authority - Publication of the notified white paper - Marketing-communication requirements - Offeror conduct requirements - Required risk statements - Website publication requirements - Required regulatory format No Launch Curve activation should occur solely on the basis of this technical document. The final legal offeror and applicable home Member State must be identified before regulatory notification. --- # 45. Exemptions require legal verification MiCA contains circumstances in which particular white-paper, notification or Title II requirements may not apply. The existence of an exemption in the Regulation does not mean that Eureka Nexus automatically qualifies for it. Potentially relevant factors can include: - Number and type of persons receiving an offer - Total consideration during the applicable period - Qualified-investor restrictions - Whether a crypto-asset is offered for free - How the crypto-asset is created or distributed - Whether utility relates to an existing operational service - Limited-network conditions - Admission to trading - Other facts surrounding the offer Any intended exemption must be documented and legally verified before it is relied upon. A business decision to limit an offer must not be designed or described as regulatory compliance unless the legal conditions for that exemption are actually satisfied. --- # 46. Final crypto-asset white paper content Where a MiCA crypto-asset white paper is legally required, the final regulatory document must contain the information required by the applicable legal framework. Depending on the final classification and launch structure, this may include information relating to: - The offeror - The issuer, where applicable - The operator of a trading platform, where applicable - The Eureka Nexus project - The planned public offer - Admission to trading, where applicable - EKNX characteristics - Rights and obligations attached to EKNX - Underlying technology - Blockchain and smart-contract infrastructure - Consensus or transaction mechanisms - Principal technical risks - Market risks - Legal and regulatory risks - Environmental and climate-related information required by the applicable framework The final legally required document must be prepared against the regulatory requirements applicable at the time of launch. This Technical White Paper is not a substitute for that final regulatory document. --- # 47. Required risk and value warnings Any final regulatory white paper must include the warnings required by the applicable legal framework. Eureka Nexus must not state or imply that: - EKNX is guaranteed to increase in value - EKNX is guaranteed to remain liquid - Purchasers are guaranteed to recover their purchase price - Mining guarantees profit - Launch Curve participation guarantees profit - DEX participation guarantees profit - Future ecosystem utility guarantees market value Users must be able to understand that a crypto-asset may: - Lose value - Lose part or all of its market value - Experience limited liquidity - Become difficult to transfer or sell - Be affected by technology failures - Be affected by regulatory changes - Be affected by market conditions --- # 48. No future-value claims Project documentation and marketing must not contain unsupported statements regarding the future value of EKNX. Planning information such as: - Launch Curve parameters - Live on-chain curve price - Market Reserve allocation - Liquidity allocation - Planned utility must not be presented as evidence that EKNX will appreciate. The live on-chain curve price is determined by the deployed Genesis bonding curve and is not a prediction of future EKNX value. --- # 49. Notification before publication Where notification under MiCA is legally required, the applicable crypto-asset white paper must be notified to the competent authority of the home Member State. Under the applicable MiCA Title II framework, notification is made at least: **20 working days before the planned publication date** where those provisions apply. The notification process may also require information explaining why the crypto-asset should not be considered: - Outside the scope of MiCA under the relevant exclusion - An asset-referenced token - An e-money token The final procedure must be verified against the law and regulatory requirements applicable at the time of launch. --- # 50. Notification is not regulatory approval Under the applicable MiCA Title II notification framework, competent authorities do not provide prior approval of the crypto-asset white paper merely through the notification process. Eureka Nexus must therefore not describe a notified document as: - Approved by MiCA - Approved by the European Union - Approved by ESMA - Approved by a competent authority unless a separate legal basis actually supports such a statement. Regulatory notification and regulatory approval are different concepts. --- # 51. Publication of the final white paper Where the MiCA publication requirements apply, the final crypto-asset white paper must be made publicly available on the relevant official website before the public offer or admission to trading begins. The published white paper must correspond to the applicable version notified to the competent authority. The document should remain publicly accessible for the legally required period. The technical GitHub draft must not silently replace a formally notified regulatory version. --- # 52. Marketing communications Where the MiCA marketing-communication requirements apply to EKNX, public communications relating to an offer or admission to trading must follow the applicable regulatory requirements. Marketing communications should be: - Clearly identifiable as marketing communications - Fair - Clear - Not misleading - Consistent with the applicable crypto-asset white paper - Consistent with the actual status of the project - Consistent with the actual status of the Launch Curve and DEX Where legally required, marketing communications must also identify the published crypto-asset white paper and provide the required contact and website information. The exact mandatory regulatory statement applicable to the relevant marketing communication must be inserted in the final launch materials in the form required by the applicable law. --- # 53. Marketing before market activation Where a crypto-asset white paper is required under the applicable MiCA provisions, marketing communications relating to the relevant public offer or admission to trading must not be disseminated before the required crypto-asset white paper has been published. This does not change the separate legal treatment of legitimate market soundings where permitted by the applicable framework. Until the EKNX market launch gate is completed, project communications must continue to distinguish clearly between: - Existing EKNX technology - Existing mining infrastructure - Development work - Planned Launch Curve architecture - Planned DEX transition - An actual active public market A COMING SOON announcement must not be presented as an active public token sale. --- # 54. Prohibited or misleading marketing direction Eureka Nexus marketing must not make unsupported claims such as: - Guaranteed profit - Guaranteed return - Guaranteed appreciation - Guaranteed liquidity - Risk-free participation - Guaranteed DEX listing price - Guaranteed sale of the complete Launch Curve allocation - Regulatory approval that has not actually been granted - Functionality being LIVE when it is only planned or in development Marketing should not use the live on-chain curve price, token allocation, future utility or liquidity plans as proof that EKNX will increase in value. --- # 55. Marketing consistency control Before public market activation, marketing material should be checked against the final applicable: - Crypto-asset white paper - Tokenomics - Risk disclosures - Launch Curve configuration - Smart-contract configuration - Market terms - Supported payment assets - DEX information - Regulatory status Material inconsistencies should be corrected before publication.