Fenrua Nexus legal and trust center

Fenrua Nexus currently operates this public trust surface for the FEN protocol, N521 research, and FENiOS. Public planning tools are designed for inspection, review, and draft generation. Protected Nexus, FENchain, treasury, validator, and governance workflows remain separated behind account checks, access review, and operator gates.

• Public planning outputs are drafts and should be reviewed before use.
• Public planning tools should not be treated as protected account workflows.
• The public trust surface should not receive confidential, regulated, or highly sensitive material.
• Protected workflow data should be handled with explicit controls, retention boundaries, and monitoring.
• Support guidance explains what to include for account, access-review, FENchain, or operator-readiness issues.

Fenrua is designing FENpresale and routing surfaces with visible fees, wallet-level limits, slippage controls, and market-integrity checks. These controls are intended to keep the system continuous and fair for normal users while reducing bot loops, stale-quote abuse, organized arbitrage, cap bypassing, and large single-account routes that could create price manipulation activities.

Fenrua is a protocol-operations system. If acquisition flow is dominated by large price shocks, access review, work rewards, treasury planning, and validator settlement become harder to price. The routing controls are designed to support predictable participation for retail users and operators without promising any market price.

Sell-side and exit route fees may use a higher disclosed fee band than acquisition routes. That design is intended to support productive protocol activity, treasury depth, work settlement, and ecosystem growth adaptability while keeping exits available through final signed quotes.

System-continuity fees are different from gas fees. System-continuity fees are protocol-level fees for Fenrua treasury depth, liquidity reserves, validation, relayer work, risk reserves, and ecosystem growth adaptability. Gas fees are chain execution costs paid to the network that processes the transaction, and native FENchain gas may support chain activity, validators, pool-depth support, and FENReLK/FENDEF continuity when routed through explicit signed schedules.

External chain gas is network-determined, but Fenrua may operate an adaptive gas-support meter for quote buffers, sponsorship eligibility, rebate lanes, pacing, and review categories. Retail acquisition can receive smoother gas guidance where supported, while large, heavy sell-side, overselling, or price manipulation activities may receive stricter gas handling.

The current public FENGas Index should be visible before approval as an actual quoted value. It is denominated as FEN per execution gas quote and should sit next to estimated execution gas amount, estimated execution gas asset, estimated FEN gas-equivalent cost, gas support amount, gas support mode, and quote expiry. The FENGas Index value is visible; exact thresholds, support weights, and formulas may remain internal.

The public dashboard may also show the current FENGas Index before a user starts a transaction. Dashboard values should come from signed snapshots, include a last updated time, and be rechecked inside the final wallet quote before approval. Dashboard index values are timestamped indicator guides, not final per-wallet transaction bounds.

FENDEF, or FEN Dynamic Economic Flows, is Fenrua's public economic-continuity framework. It may unify FENGad, FENGas, FENSup, FENUnLK, FENReLK, FENConti, route fees, exit fees, ecosystem fees, treasury depth, pool depth, traffic, and verified system activity. Live dashboard indexes are timestamped indicators for visibility, not final execution instructions.

The public FENGad Index is different from FENGas. FENGad is a signed continuity ratio between FENReLK possible burn-capacity support and FENUnLK supply unlock capacity. It may show the ratio value, capacity references, epoch, last updated time, and recheck requirement. FENGad is not a price signal, treasury execution promise, burn promise, guaranteed allocation, profit claim, or appreciation promise.

FENConti is the continuity rail that 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. Exact traffic weights, pool-depth formulas, scoring thresholds, and ramp math may remain internal.

FENUnLK is a supply-continuity index for unlock capacity from governance-approved reserves, incentive buckets, liquidity support buckets, or scheduled allocations. It may show epoch, max epoch unlock, available unlock capacity, unlocked amount, remaining capacity, reserve source, and last updated time. FENUnLK 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 may describe possible burn-capacity support from approved treasury budgets or ecosystem fee buckets, but it is not an execution layer and does not execute treasury trades, burns, unlocks, or re-locks by itself. FENSup may describe the weekly supply verdict for approved burn capacity or approved unlock capacity after logged system activity is balanced 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. Neither provides liquidity commitments, scarcity or unlock commitments, redemption value, price support, profit, or appreciation.

• The initial FEN reference ratio is a quote anchor for planning and interface previews, not a promise of market price, redemption value, profit, or appreciation.
• Route fees, ecosystem fees, slippage tolerance, gas costs, and market-clearing price are separate values and should be shown separately before wallet approval.
• The final signed quote and review category should be visible to users, but exact scoring formulas, ramp thresholds, cooldown thresholds, and pool-depth math may remain internal to prevent abuse.
• Large acquisitions may be capped, delayed, split, routed through time-weighted execution, or sent to manual review to reduce market impact.
• Sell-side route fees must be disclosed separately and should not be treated as a lock-in mechanism, price-support promise, or redemption guarantee.
• External-chain gas should not be described as Fenrua route-fee revenue, and system-continuity fees should not be hidden inside gas estimates. Native FENchain gas may support chain activity, validators, pool-depth support, and FENReLK/FENDEF continuity only when routed through explicit signed schedules.
• Gas support categories, sponsorship, rebates, buffers, pacing, and review gates may adapt to system activity without publishing exploitable formulas.
• Signed one-time quotes, wallet velocity limits, liquidity-depth checks, balance preflights, route cooldowns, and anomaly pauses are market-integrity safeguards.
• These controls are not designed to create artificial price outcomes; they are designed to reduce abuse, preserve continuity, and keep public rules transparent.

Fenrua legal notices and interface explanations are provided for transparency. They are not legal, financial, investment, tax, compliance, or professional advice. Users are responsible for understanding wallet self-custody, transaction risk, market movement, network gas, timing, and local legal obligations before using protocol surfaces.

• Fenrua does not guarantee that FEN will maintain or increase value.
• Treasury and liquidity-support mechanisms can support operational resilience but do not create a guaranteed redemption right.
• Any production route, fee, cap, or market-integrity setting may change through documented governance, security, or operational updates.

Questions about the public site, legal notices, privacy posture, or partnerships can be sent to partnerships@fenrua.ai.