Eligibility
Unlocked FEN only
P-FEN and locked/unclaimed FEN are excluded.
FENpool
Rewards start only after FEN is unlocked and claimed.
FENpool is the public reward-pool rule surface for FEN. It explains eligibility, lock plans, wallet caps, funded monthly reward epochs, and the no fixed APY boundary before any reward controls are exposed.
P-FEN cannot be staked in FENpool.
Locked or unclaimed presale FEN cannot be staked in FENpool.
Only unlocked and claimed FEN can enter FENpool rewards.
New FENpool positions begin earning from the next eligible funded epoch.
Minimum lock
6 months
The shortest supported lock plan is 180 days.
Reward model
Variable
Rewards depend on funded monthly epochs. No fixed APY.
Wallet cap
Fairness rule
Wallet caps may support retail-first access and reduce early concentration.
Abstract 1. Section Abstract
FENpool is a funded-epoch accounting section.
This section defines FENpool as the reward-accounting layer downstream of claimed FEN. It separates receipt state from reward inventory, lock duration from return guarantee, and plan weight from fixed yield. The section is intentionally conservative because a reward surface becomes misleading the moment it treats future funding, APY, or pool balance as if they already exist.
Reward theorem: eligibility is a state condition, and return language is inadmissible unless a funded epoch and receipt prove it.
Research Questions
Research Question 1. RQ-FP-01
When does a FEN balance become reward-eligible inventory?
Only after FEN is unlocked and claimed; P-FEN receipts and locked or unclaimed presale balances are excluded from reward entry.
Research Question 2. RQ-FP-02
How can rewards be described without implying fixed yield?
Rewards are documented as funded-epoch accounting with variable monthly allocations, zero-reward months, and pro-rata distribution rather than APY promises.
Research Question 3. RQ-FP-03
What evidence should a public reward pool publish?
Funding amount, eligible weighted stake, plan weights, claimed rewards, remaining balances, and receipt references should be visible when published.
Formal Claim Register
| Claim | Statement | Evidence | Boundary |
|---|---|---|---|
| Formal Claim 1. FC-FP-01 | FENpool accepts only unlocked and claimed FEN. | Eligibility rules, pool metrics, and the flow diagram all exclude P-FEN and locked or unclaimed presale FEN. | The section does not expose staking controls or imply that receipt balances can enter rewards. |
| Formal Claim 2. FC-FP-02 | FENpool rewards are variable and funded-epoch based. | Reward rules state funded monthly epochs, zero-reward validity, pro-rata distribution, and no fixed APY. | Plan weights are accounting weights, not fixed returns, investment guarantees, or price support. |
| Formal Claim 3. FC-FP-03 | Public reward evidence is receipt-driven. | The section states the expected public record: funding amount, eligible weighted stake, claimed rewards, remaining reward balances, and monthly receipts. | Receipt expectations do not expose reward-funding authority or private allocation procedures. |
Invariant Ledger
Invariant 1. INV-FP-01
Receipt state cannot enter the reward pool.
Eligibility cards and flow nodes state that P-FEN is excluded before the lock-plan selection step.
Invariant 2. INV-FP-02
A lock plan cannot become a fixed-return promise.
Plan weights are described only as pro-rata accounting modifiers inside funded epochs.
Invariant 3. INV-FP-03
A zero-reward epoch is valid public state.
Reward rules require zero-reward months to remain visible rather than hidden or treated as failure.
Evidence Matrix
| Row | Artifact | Observation | Limitation |
|---|---|---|---|
| Evidence Row 1. FP-01 | contracts/presale/FENStakingPool.sol | Defines the source contract associated with FENpool lock plans and reward claims. | The public page remains read-only and does not expose stake, withdraw, or claim controls. |
| Evidence Row 2. FP-02 | lib/public-evidence-source.ts | Includes FENStakingPool as a production trust source in the public source index. | Source publication does not imply an active funded epoch or reward balance. |
| Evidence Row 3. FP-03 | app/nexus/fenpool/page.tsx | Documents lock plans, reward rules, no fixed APY, and read-only boundary. | Explanatory UI must be reconciled with on-chain receipts when reward epochs are published. |
Limitations And Non-Claims
Limitation 1. L-FP-01
No fixed APY
The section intentionally refuses fixed-return language. Rewards depend on funded monthly epochs and may be zero.
Limitation 2. L-FP-02
No receipt staking
P-FEN and locked or unclaimed presale FEN are not reward inventory and cannot be interpreted as eligible pool balance.
Limitation 3. L-FP-03
No public funding authority
The public section can describe the reward evidence expected after funding, but it does not expose reward allocation, treasury, or operator controls.
FENpool funded-epoch diagram
Reward eligibility starts after claim, then moves through lock, epoch funding, pro-rata distribution, and public receipts.
FENpool is deliberately downstream from FENpresale. The page must show that receipt state and locked state are not reward inventory, and that epoch funding is a recorded protocol event rather than a guaranteed return stream.
receipt state
P-FEN excluded
Non-transferable presale receipts cannot enter FENpool.
claim state
unlocked FEN only
Locked or unclaimed presale FEN remains ineligible.
reward policy
variable
Funded epochs decide reward availability; no fixed APY.
minimum lock
180 days
Shortest listed lock plan for eligible claimed FEN.
01 / claimed FEN inventoryeligible inputFENpool begins only after FEN is unlocked and claimed. P-FEN receipt state and locked or unclaimed presale balances remain outside the reward system.
02 / lock plan selection180 / 360 / 540 daysA wallet chooses a lock plan whose weight can affect pro-rata accounting inside funded epochs without creating a fixed return promise.
03 / funded epochmonthly recordReward accounting depends on actual funded monthly epochs. A zero-reward month is valid and remains part of the public reward history.
04 / weighted distributionpro-rataEligible positions share the funded epoch according to recorded stake, plan weight, wallet constraints, and the published epoch balance.
05 / receipt publicationFENtrustThe public record should show funding amount, eligible weighted stake, claimed rewards, remaining reward balance, and published receipt references when available.
The public rule is strict: P-FEN cannot be staked; locked or unclaimed FEN cannot be staked; only unlocked and claimed FEN can enter FENpool rewards.
Lock plans
Plan weights support pro-rata accounting inside funded epochs. They are not a fixed return, not a market price, and not a guarantee that any month will be funded.
| Plan | Lock | Weight |
|---|---|---|
| 6 month | 180 days | 10,000 bps |
| 12 month | 360 days | 12,500 bps |
| 18 month | 540 days | 15,000 bps |
Funded epoch rules
FENpool rewards are variable and depend on funded monthly reward epochs.
No fixed APY is promised.
There is no fixed-rate reward policy.
Rewards are distributed pro-rata by epoch across eligible locked FENpool positions.
Plan weights may affect a wallet share of a funded epoch, but they are not a promised return.
Zero-reward epochs are valid and should remain visible in the public record.
Monthly reward funding depends on approved allocations, chain activity, ecosystem activity, policy, audits, liquidity, operations, and security needs.
Each monthly reward allocation should be published with an on-chain funding transaction and public receipt.
Read-only boundary
This page does not provide entry, withdraw, claim, approve, or reward-funding controls. Public FENpool records should show the actual funded amount, eligible weighted stake, claimed rewards, remaining reward balances, and monthly receipts when published.