Terms of use

The Fenrua Nexus website provides public information, contact links, and public planning tools for the FEN protocol, N521 research, and FENiOS. Protected Fenrua workflows may require wallet verification, access review, legal acknowledgement, and operator approval. By using the site, you agree to use it lawfully, respectfully, and in a way that does not interfere with the site, protected systems, or other visitors.

Protected access review may require a wallet address, selected participation path, acceptance of the current legal and privacy notices, and acknowledgement of protected-access boundaries before participation continues.

• Wallet verification does not guarantee immediate protected protocol execution.
• Fenrua Nexus may delay, limit, suspend, or decline protected access for abuse prevention, access review, security, operator-readiness, or operational reasons.
• Users are responsible for keeping wallet recovery material secure and for using the correct wallet address for public protocol actions.

Public planning outputs are structured drafts for review, comparison, and iteration. They are not legal, financial, medical, security, or professional advice.

• Review outputs before use.
• Do not submit sensitive or confidential material to public planning tools.
• Do not treat public planning output as a final decision or a substitute for specialist review.

Fenrua Nexus uses access tracks to describe how a visitor wants to engage with the protocol surface: read-only observation, builder collaboration, or operator-level readiness conversations. Access tracks are not stored value, custody, retail subscriptions, token allocations, or automatic execution rights.

• Public pages are for protocol evidence, education, and readiness review, not open execution.
• Public planning outputs are drafts for shaping work intent before protected workflows.
• Protected execution, relay work, validator paths, and reserve operations remain guarded.
• Access tracks are not subscriptions, stored value, token custody, or guaranteed execution rights.

Protected participation follows a conservative sequence: wallet verification, participation-path selection, legal acknowledgement, access review, and explicit operator approval where privileged protocol actions are involved.

• Start with FENswap and the non-custodial wallet you expect to use for public quote review.
• Use approved FENswap paths for FENpresale entry and P-FEN receipt previews.
• Fenrua reviews protected participation separately from public planning access.
• Privileged protocol paths stay locked until the relevant operator gate is explicitly approved.

• Do not attempt to disrupt, overload, scrape aggressively, or interfere with the site.
• Do not use the site to generate harmful, deceptive, infringing, or unlawful material.
• Do not submit credentials, private keys, sensitive keys, or sensitive third-party information.
• Do not misrepresent Fenrua Nexus outputs as reviewed, approved, or produced by a third party.
• Do not use bots, coordinated wallets, stale quotes, sandwich-style behavior, rapid round trips, or split orders to bypass route caps, manipulate pricing, exhaust liquidity, or interfere with normal user access.

FENpresale and routing surfaces may include protocol fees, slippage settings, account-level caps, quote expiry, one-time quote IDs, velocity limits, liquidity preflights, cooldowns, anomaly pauses, and manual review. These controls exist to reduce abuse, preserve system continuity, protect retail access, and keep route behavior transparent before execution.

• Fenrua may reject, delay, split, pause, or require review for transactions that appear designed to create price manipulation activities, bypass caps, or exploit stale route information.
• Users should receive the final signed quote, fee, slippage, expiry, and review state before approval, but exact anti-abuse formulas and scoring thresholds may remain internal.
• Sell-side and exit route fees may be higher than acquisition route fees to support productive protocol activity and ecosystem growth adaptability; they should remain disclosed before approval.
• System-continuity fees are protocol-level fees and are different from gas fees. Gas fees are chain execution costs and should remain displayed separately from route fees, exit fees, slippage, stake, collateral, principal, and expected received amount.
• External network gas is network-determined, but Fenrua gas support, buffers, sponsorship, rebate lanes, pacing, and review categories may adapt to system activity, retail acquisition demand, sell-side pressure, and pool-depth conditions. Native FENchain gas may support chain activity, validators, pool-depth support, and FENReLK/FENDEF continuity only when routed through explicit signed schedules.
• The current public FENGas Index should be visible before approval as an actual quoted value denominated in FEN per execution gas quote, alongside estimated execution gas amount, estimated execution gas asset, estimated FEN gas-equivalent cost, gas support amount, gas support mode, and quote expiry, while exact thresholds and formulas may remain internal.
• The FENGas Index may also appear on a live dashboard before a user starts a transaction. Dashboard values should use signed snapshots, show last updated timing, and act as timestamped indicator guides, not final per-wallet transaction bounds; the final wallet quote must recheck the value before approval.
• FENDEF, or FEN Dynamic Economic Flows, may unify FENGad, FENGas, FENSup, FENUnLK, FENReLK, FENConti, route fees, exit fees, ecosystem fees, treasury depth, pool depth, system traffic, and verified activity into one public economic-continuity framework. Live dashboard indexes are timestamped indicators, not final execution instructions.
• FENGad is different from FENGas. FENGad may show a signed continuity ratio between FENReLK possible burn-capacity support and FENUnLK supply unlock capacity. It is not a price signal, treasury execution promise, burn promise, guaranteed allocation, profit claim, or appreciation promise.
• FENConti may connect route fees, exit fees, caps, review lanes, FENGad Index snapshots, FENGas Index snapshots, FENUnLK Index snapshots, FENReLK Index snapshots, FENSup Index snapshots, and ecosystem fees to system traffic, route volume, pool depth, treasury depth, access-review demand, work settlement, and validator or relay load, while exact traffic weights, pool-depth formulas, scoring thresholds, and ramp math may remain internal.
• FENUnLK may show epoch unlock capacity from governance-approved reserves, incentive buckets, liquidity support buckets, or scheduled allocations. It does not create unlimited supply and should not be treated as a final per-wallet allocation, redemption promise, price-support signal, profit claim, or appreciation promise.
• FENReLK and FENSup are continuity rails with different roles. FENReLK is a possible burn-capacity support indicator, not an execution layer, and should not be treated as a guaranteed treasury trade, burn, unlock, or re-lock. FENSup may log verified system activity throughout the week and act as the FENDEF supply verdict layer for approved weekly burn capacity or approved weekly unlock capacity through the signed weekly FENDEF schedule. The live FENGad, FENReLK, and FENSup indexes are indicators only; the signed weekly FENDEF schedule finalizes the FENReLK/FENUnLK continuity posture, and FENSup makes the final weekly supply verdict after review of logged activity, treasury state, pool depth, burn source, unlock pressure, FENReLK indicator state, FENUnLK capacity, FENGad posture, and governance caps. They should not be treated as guaranteed liquidity, guaranteed scarcity or unlock, redemption value, price support, profit, or appreciation.
• Fees and caps are separate from any initial FEN reference ratio shown for planning or quote previews.
• No fee, treasury, liquidity, or routing control should be understood as a guarantee of FEN price, profit, market support, or redemption value.

The Fenrua Nexus name, site design, copy, and public interface are owned by Fenrua Nexus or its licensors. You may use your own inputs and copied forge outputs for evaluation, review, or internal planning, subject to these terms and applicable law.

Links to social platforms, email clients, or other websites are provided for convenience. Fenrua Nexus is not responsible for third-party websites or their practices.

The public site and public planning tools are provided as available. Fenrua Nexus does not promise uninterrupted availability, error-free operation, continuous access, or suitability for a particular purpose.

Fenrua Nexus may update the public site, tools, legal pages, notices, and contact paths over time. Continued use of the public site after updates means you accept the updated terms.

Questions about these terms can be sent to partnerships@fenrua.ai.