FENGad
0.328
FENReLK / FENUnLK
Continuity balance between possible burn-capacity support and approved supply unlock capacity.
FENDEF
FENDEF explains how Fenrua presents economic-continuity signals without turning the public UI into a formula map for adversaries. The useful public language is precise: timestamped indexes, signed quote posture, separated gas and route fees, visible slippage discipline, weekly supply verdicts, and explicit statements that indexes are not price guarantees, fixed returns, or hidden token taxes.
FENGad
0.328
FENReLK / FENUnLK
Continuity balance between possible burn-capacity support and approved supply unlock capacity.
FENGas
0.024 FEN
execution guidance
Timestamped gas guidance. Final wallet-facing quotes must recheck source-chain gas before approval.
FENSup
weekly
supply verdict
The signed weekly FENDEF schedule decides burn capacity, hold posture, or approved unlock capacity.
Abstract 1. Section Abstract
This section treats dynamic economic flows as a public policy interface. Its role is to show timestamped indexes, route-cost discipline, weekly posture, and signed-quote requirements without leaking the formulas that would make abnormal-flow mapping easier. The public contribution is therefore not a promise of price or liquidity, but a method for communicating economic context with explicit non-claims.
Policy theorem: public signals are useful only when quote decomposition is explicit and formula disclosure is constrained.
Research Question 1. RQ-DEF-01
Timestamped indexes, gas guidance, route-cost categories, weekly posture, and signed-quote requirements can be public while weights, thresholds, and anomaly heuristics remain protected.
Research Question 2. RQ-DEF-02
Every quote must separate source value, gas, route fee, exit fee, slippage, expiry, and expected P-FEN output before final review.
Research Question 3. RQ-DEF-03
An index is not a price guarantee, liquidity guarantee, hidden token tax, APY, execution layer, or per-wallet allocation right.
| Claim | Statement | Evidence | Boundary |
|---|---|---|---|
| Formal Claim 1. FC-DEF-01 | FENDEF exposes public policy signals without exposing abuse-sensitive formulas. | The section lists FENGad, FENGas, FENSup, public rules, and protected formula boundaries. | Exact formulas, thresholds, route weights, and anomaly heuristics are intentionally withheld. |
| Formal Claim 2. FC-DEF-02 | FENDEF is P-FEN-aware during FENswap and presale intake. | Policy metrics and footer language require quote output to preserve receipt-output language. | FENDEF guidance cannot transform a quote preview into claimed FEN or reward-eligible inventory. |
| Formal Claim 3. FC-DEF-03 | Weekly posture is a review checkpoint. | FENSup is presented as a weekly verdict layer that can approve burn capacity, hold, or unlock capacity after logged activity review. | The weekly schedule is not an automatic execution authority or unlimited supply permission. |
Invariant 1. INV-DEF-01
Public rules state that dashboard indexes are timestamped guidance and not final per-wallet transaction terms.
Invariant 2. INV-DEF-02
Rules require gas, route fee, exit fee, slippage, quote expiry, and expected output to remain separate.
Invariant 3. INV-DEF-03
Formula boundary language excludes thresholds, scoring weights, route formulas, abnormal-flow heuristics, and manipulation controls.
| Row | Artifact | Observation | Limitation |
|---|---|---|---|
| Evidence Row 1. DEF-01 | chainstack/fen-route-fees.v51.json | Supplies phase, status, activity rows, and public policy surface labels. | The public model does not disclose the protected formulas behind final review. |
| Evidence Row 2. DEF-02 | chainstack/quote-planner.v51.json | Links quote discipline to configured preview plans and source-asset families. | Preview plans do not equal live execution availability or final wallet terms. |
| Evidence Row 3. DEF-03 | deployments/ui-stale-language-audit-20260704.json | Records prior public-copy cleanup around FENswap and stale route language. | A copy audit is not a formal security audit of economic mechanics. |
Limitation 1. L-DEF-01
FENDEF policy language does not change the stated 0% ERC20 transfer-tax claim for FEN.
Limitation 2. L-DEF-02
FENGad, FENGas, and FENSup are policy indicators and review signals, not promises of price support, route depth, or exit liquidity.
Limitation 3. L-DEF-03
The monograph intentionally withholds exact scoring and anomaly logic to reduce adversarial mapping of route and supply controls.
FENDEF policy diagram
FENDEF is an economic-continuity language for public review. It gives users enough structure to understand route cost, gas guidance, supply posture, and weekly verdicts without publishing the exact mechanisms that would help abnormal flows map the system.
phase
v51-fenchain-hardening
Public economic-flow phase label from the configured policy model.
status
pre-execution-fee-model
Public readiness status for the FENDEF policy surface.
activities
15
Published activity rows represented as policy surfaces, not formula internals.
quote mode
P-FEN aware
FENswap quotes must preserve receipt-output language.
FENDEF must stay aligned with FENswap: public quote output remains P-FEN when the user is still in the receipt path.
Dashboard indexes are timestamped guidance, not final per-wallet transaction terms.
Final wallet-facing quotes must show gas, route fee, exit fee, slippage, quote expiry, and expected output separately.
FENReLK is possible burn-capacity support. It is not an execution layer, liquidity promise, or price-support signal.
FENUnLK is approved unlock capacity. It does not create unlimited supply or per-wallet allocation rights.
FENSup is the weekly verdict layer and can approve burn capacity, hold, or approved unlock capacity after logged activity is reviewed.
Exact formulas, thresholds, route weights, velocity scoring, pool-depth math, and anomaly heuristics stay protected to reduce manipulation risk.
The public surface can name economic rails and quote requirements, but it should not render private route weights, threshold math, scoring heuristics, integration mechanics, or abuse-control internals. That boundary is part of the engineering design, not an omission.
Supported FENswap routes must separate source value, gas, route cost, slippage, expiry, and P-FEN output.
Public indexes help reviewers understand continuity posture without receiving protected scoring formulas.
The weekly signed FENDEF schedule is the public checkpoint for hold, burn-capacity, or approved unlock posture.