$NEXUS — risk factors and issuer disclosures

VDM Nexus is operated by a Spain-resident autónomo (self-employed natural person, registered with the Agencia Tributaria and Spanish Social Security). The operator is not a legal person under Spanish law — there is no SL (Sociedad Limitada), no SA, and no separate corporate vehicle as of publication. The CNMV (Comisión Nacional del Mercado de Valores) is the relevant supervisor under MiCA (EU Regulation 2023/1114) and Spanish Royal Decree-Law 7/2024. Spain's MiCA transitional regime ended on 30 December 2025 — CNMV enforcement is active.

The protocol code is open-source under MIT (github.com/vdmnexus/vdmnexus). The website, packages, and operational infrastructure are maintained by the autónomo. A legal-entity structure (Spanish SL or partner foundation) may be formed before or after token launch; status will be disclosed on this page when finalized.

• Total supply: 100,000,000,000 $NEXUS, fixed forever. Mint authority disabled at deploy.
• Launch venue: a Uniswap v4 $NEXUS/USDC pool with a custom fee-burn hook on Robinhood Chain (an Ethereum L2; testnet chain id 46630). ERC-20 token. Dollar-denominated MCAP (no ETH beta). The launch is gated on Robinhood Chain mainnet availability, an external audit of the hook + vault contracts, and legal review — no launch date is announced until all three clear. This venue supersedes the previously published pump.fun/Solana plan.
• Allocation: 70% liquidity pool (Uniswap v4 LP position burned at deploy), 15% treasury vault (multisig-controlled vesting contract, 90d lockup + 12mo linear vest), 10% retroactive airdrop (non-spendable multisig, criteria within 90d, 6mo distribution vest), 5% community pool (publicly tracked multisig, no lockup). Multisig tooling (Safe or equivalent) finalized before addresses are published.
• Team allocation: None. No presale, no insider rounds, no vesting bypass, no configurable distribution path. The deployer wallet does not hold a team allocation.
• Utility wires: Disclosed on a dated 0/30/60/90 calendar on /whitepaper (published at launch) Section 03. Final structure of Wires 3 (reputation bond) and Wire 4 (verifier staking + revenue share) is subject to a Spanish legal scoping memo under ESMA March 2025 Guidelines on the qualification of crypto-assets as financial instruments and CNMV MiCA Q&A. Wires 3-4 may be restructured, replaced with non-yielding alternatives (e.g. soulbound reputation tokens), or deferred if scoping finds CASP authorization or MiFID II exposure.
• Multisig addresses: Published 24-48 hours before launch. Verifiable on the Robinhood Chain explorer as three distinct allocations, not as a clustered wallet.

• Not a security — not an investment contract, not a profit-share, not a revenue claim, not a share certificate. No return is promised, implied, or guaranteed.
• Not a regulated financial instrument under MiFID II Annex I, to the best of the issuer's current understanding, pending the legal scoping memo.
• Not a governance token — no voting rights, no governance authority over the protocol or any related entity.
• Not insured, not custodied by Nexus — holders self-custody. There is no FDIC, FSCS, Fondo de Garantía de Inversiones, or equivalent protection.
• Not available, intended, or marketed in jurisdictions where the offer would be unlawful — including but not limited to restricted persons under applicable EU, UK, US, or other regulations.
• Not financial advice. Nothing on this site or in the whitepaper is a solicitation, recommendation, or guarantee of any outcome.

The following risks are not exhaustive. Read carefully. Participate only with funds you can lose without consequence, and only where it is lawful for you to do so.

• Beta protocol. No third-party security audit has been performed at time of publication. No SLA, no SOC 2, no ISO 27001. The API surface is stable; the operational rail is mainnet live; v1 ships at $NEXUS launch. Bugs, downtime, and unexpected behavior are possible.
• Solo founder, single point of failure. One Spain-resident autónomo operates the rail, the marketing, the legal compliance, and the support. Incapacitation, illness, or operator absence may pause development indefinitely.
• Regulatory risk. CNMV may issue public warnings against the issuer, the token, or related activities. MiCA enforcement is active in Spain since 30 December 2025. EU AI Act Article 12 (extended to 2 December 2027) and other applicable regulations may shape what wires can be shipped and in what form. ESMA may publish guidance that reclassifies $NEXUS as a financial instrument even after launch.
• Smart contract risk. The Uniswap v4 pool and its custom fee-burn hook, the vesting contract, the Rienda vault contracts, the future bond contract (Wire 3), and the future verifier-staking contract (Wire 4) are smart contracts. Smart contracts can have bugs, can be exploited, and can fail in ways that result in permanent loss of tokens or funds. The fee-burn hook and the Rienda vaults are custom, unaudited code at time of publication — they do not ship to mainnet before an external audit.
• Liquidity risk. A newly created Uniswap v4 pool can be thin. Liquidity is subject to traded volume on Robinhood Chain DEX infrastructure, which is itself new. Slippage on size can be high. Exits may not be available at expected prices.
• New-chain risk. Robinhood Chain is a new Ethereum L2. Its mainnet availability, sequencer uptime, bridge liquidity, tooling (explorers, multisigs, indexers), and USDC availability are outside the issuer's control. If the chain's mainnet, tooling, or USDC support do not materialize as expected, the launch plan will be re-venued again and this page updated.
• Volatility risk. Fair-launch tokens are volatile. Infrastructure tokens are doubly so. Price movements of 50% or more in a single day are common and possible.
• Wire-ship risk. Wires 2, 3, 4 are commitments with timelines, not shipped features. Each may slip, be restructured, or be deferred indefinitely based on legal scoping, engineering capacity, or market conditions. Status of each wire will be disclosed on /roadmap in public.
• Total-loss risk. $NEXUS can lose its entire value. Treat any allocation as fully at risk.

Rienda is the VDM Nexus product: smart-contract vaults on Robinhood Chain that hold an LLM trading agent's capital and enforce risk guardrails in contract code (position caps, loss limits, drawdown throttles, kill switch), paying the agent's inference via x402 out of realized PnL. Its status, stated plainly:

• Not live. The spec is complete; the contracts are in development. Nothing described as Rienda accepts deposits today.
• Testnet first. Contracts deploy to Robinhood Chain testnet (chain id 46630) before any mainnet deployment. Mainnet is gated behind an external security audit and legal review. No mainnet date is announced or implied.
• Unaudited until stated otherwise. No third-party audit of the Rienda contracts exists at time of publication. Audit status will be disclosed on this page and on /security when it changes.
• Trading losses are the operator's. The vault bounds downside; it does not prevent it. An agent can lose up to its configured limits, and contract bugs could lose more. Guardrails are code, not guarantees.
• No performance claims. Nothing about Rienda is a claim that LLM trading agents are profitable. The performance-metered compute design exists precisely because most trading strategies lose money.
• Legal characterization pending. Whether operating Rienda vaults for third parties triggers MiCA, MiFID II, or AIFMD obligations is part of the legal scoping work. Until that review concludes, Rienda is planned as self-custodied, operator-deployed vaults — each operator deploys and owns their own vault; Nexus does not custody vault capital.

The signed-inference rail (nexus.vdmnexus.com, packages, SDKs, verifier) is in Beta. v1 ships at $NEXUS launch. Beta means: API surface stable, mainnet live since 2026-05-21, no SLA, no paid support tier, no external audit. Beta status is disclosed visually on every public surface. See /security for security architecture and responsible disclosure contact.

/whitepaper (published at launch) · /token (published at launch) · /security · /roadmap · github.com/vdmnexus/vdmnexus

Last updated at deploy. This page is the canonical disclosure surface for $NEXUS and the VDM Nexus rail; changes are versioned in git.