Settlement substrate
Chain 978
The FEN protocol lane is scoped for low-cost settlement, builder access, work accounting, and public continuity signals that AI teams can evaluate without seeing privileged operations.
FENprotocol
Low-fee AI project hosting, written as a verifiable protocol map.
FENprotocol frames Fenrua as a technical hosting candidate for AI projects that need affordable settlement, explicit support workflows, accountable public evidence, and a disciplined separation between the FEN protocol chain and the N/P-521 research chain. The page is intentionally evidence-first: Chain 978, Chain 521, FENiOS, FENtrust, and the FEN token-state rules are presented as separate parts of one system model rather than one vague participation narrative.
Receipt layer
P-FEN
FENpresale uses a non-transferable receipt token so public copy can describe contribution state, burn-to-claim behavior, and cliff-based unlocks without implying liquid presale FEN.
Coordination layer
FENiOS
The protocol OS concept gives AI builders a structured work surface for requirements, evidence, support context, and release sequencing rather than a disconnected token narrative.
Research isolation
Chain 521
The N/P-521 research lane has its own chain identity and block progress, keeping experimental cryptographic evidence separated from the FEN support chain.
Live RPC continuity
Chain 978 and Chain N521 side-by-side RPC continuity
FENprotocol keeps both public RPC continuity lanes visible across the full page while preserving their separate roles: Chain 978 for FEN protocol support, Chain 521 for N/P-521 research evidence. Last refresh: pending
Reading public block progress...
Public chain surface
Chain 978
Latest block
Reading
Sample move
+0
Chain ID
978
Block progressreading
Public block read is pending; this card updates when the current block is returned.
Public chain surface
Chain N521
Latest block
Reading
Sample move
+0
Chain ID
521
Block progressreading
Public block read is pending; this card updates when the current block is returned.
Why Fenrua Exists
The protocol thesis starts with infrastructure, research separation, and AI workflow intelligence.
Problem Statement
AI projects need low-cost settlement, public evidence, workflow support, and chain-aware operating context, but most crypto infrastructure either hides trust assumptions or collapses unrelated claims into token marketing.
Protocol Contribution
Fenrua separates protocol support, presale receipt accounting, N/P-521 research, economic continuity policy, and AI workflow intelligence into distinct public surfaces.
System Model
Chain 978 carries the FEN support-chain thesis, Chain 521 carries the N/P-521 research-chain thesis, FENiOS coordinates evidence-aware AI project review, and FENtrust keeps public claims tied to source evidence.
Abstract 1. Section Abstract
FENprotocol specifies the state machine that makes the rest of Nexus intelligible.
This section treats FENprotocol as the system model for the public site. Its purpose is to prove that Fenrua can describe a complex chain system without compressing receipt state, claimed-token state, reward state, support-chain state, and research state into one ambiguous participation story. The method is deliberately formal: every public claim is assigned to a lane, every lane has admissible evidence, and every downstream action has a precondition.
Protocol method: define state first, then attach evidence, then state the boundary.
Definitions
- Definition 1.Support-chain claim
- A public claim about FENchain 978, AI hosting context, FEN settlement intent, builder support, work records, or live support-chain continuity.
- Definition 2.Research-chain claim
- A public claim about Chain 521, N, P-521 signatures, vector behavior, circuit receipts, or multisig-gated research modules.
- Definition 3.Receipt state
- The P-FEN phase of the protocol in which user-facing accounting exists before FEN is unlocked and claimed.
- Definition 4.Protocol OS
- The FENiOS coordination layer that assembles project context, evidence requirements, review output, and protected-boundary language.
Research Questions
Research Question 1. RQ-P-01
What is the minimal public state machine for the FEN protocol?
The minimal machine is source-value intake, P-FEN receipt issuance, burn-to-claim scheduling, claimed FEN inventory, reward branch, and N research migration branch.
Research Question 2. RQ-P-02
Which chain owns which class of claim?
Chain 978 owns FEN support, hosting, settlement, and work-accounting claims; Chain 521 owns N/P-521 research, vector, circuit, and release-gate claims.
Research Question 3. RQ-P-03
How does FENiOS become protocol infrastructure rather than generic AI copy?
FENiOS is treated as a coordination layer that binds project context, token state, chain state, source evidence, and protected-execution boundaries into review artifacts.
Formal Claim Register
| Claim | Statement | Evidence | Boundary |
|---|---|---|---|
| Formal Claim 1. FC-P-01 | FENprotocol is a stateful protocol map, not a single token page. | The section diagram names source value, P-FEN, burn receipt, Chain 978, FENpool, and N521 as ordered nodes. | The page does not imply that receipt state, reward eligibility, and research migration are simultaneously available. |
| Formal Claim 2. FC-P-02 | Chain 978 and Chain 521 are separate evidence lanes. | The combined block-progress panel is accompanied by lane-specific definitions and separate section links. | A Chain 521 research receipt cannot validate a Chain 978 hosting claim unless the dependency is separately shown. |
| Formal Claim 3. FC-P-03 | Public protocol trust is source-backed and boundary-backed. | The page routes to FENtrust for source excerpts, hashes, report outcomes, public statement source, and full source panels. | Source-backed public proof does not expose private execution, custody, validator, or reserve controls. |
Invariant Ledger
Invariant 1. INV-P-01
A P-FEN balance is never treated as claimed FEN.
Copy, flow nodes, and section links keep P-FEN in the receipt layer until burn-to-claim mechanics are described.
Invariant 2. INV-P-02
A research-chain fact is never used as a support-chain fact.
Chain IDs, labels, block-progress panels, and section boundaries keep 978 and 521 claims assigned to their lane.
Invariant 3. INV-P-03
Public evidence never becomes public authority.
The section describes observability, source proof, and readiness while excluding private operator and protected execution controls.
Invariant 4. INV-P-04
Reward eligibility is downstream of unlock and claim.
FENpool is described only after unlocked and claimed FEN, with P-FEN and unclaimed FEN explicitly excluded.
Evidence Matrix
| Row | Artifact | Observation | Limitation |
|---|---|---|---|
| Evidence Row 1. P-01 | lib/site.ts | Defines the public token-flow summary and allowed verification vocabulary. | Language configuration is a public-claim control, not a smart-contract proof by itself. |
| Evidence Row 2. P-02 | components/nexus/live-chain-progress-dashboard.tsx | Renders live progress for Chain 978 and Chain 521 while preserving chain-specific labels. | Block progress proves liveness signals, not unrestricted safety or economic adequacy. |
| Evidence Row 3. P-03 | components/nexus/engineering-flow-map.tsx | Presents the state machine as ordered nodes with claim-specific details. | The diagram is an explanatory artifact and must stay consistent with source-level evidence. |
protocol flow diagram
FEN value, receipt accounting, reward eligibility, and research migration stay in separate lanes.
This diagram is the public engineering grammar for the protocol: it shows how a user-facing route moves from supported source value into a presale receipt, then into unlocked FEN, and only then into downstream protocol branches. The diagram is intentionally strict because most trust failures in token interfaces come from collapsing receipt state, locked state, reward eligibility, and research migration into one ambiguous sentence.
support chain
978 / 0x3d2
FEN protocol hosting, work settlement, support posture, and public block progress.
research chain
521 / 0x209
N/P-521 evidence lane with independent block progress and release boundary.
receipt token
P-FEN
Non-transferable presale receipt before burn-to-claim FEN settlement.
claim branch
FENpool / N
Unlocked FEN can move into rewards or published burn-to-mint migration logic.
01 / source value intakeFENswapSupported source assets are represented in the interface as stablecoin-value routing, with visible output staying on the P-FEN receipt path for this public pass.
02 / receipt issuanceP-FENThe receipt surface keeps presale accounting legible: P-FEN is not presented as transferable FEN, and its public role is constrained to the presale claim mechanism.
03 / scheduled claimburn receiptAfter presale finalization, P-FEN is burned into the presale contract and unlocked FEN is claimed according to the published cliff schedule.
04 / support chain978Unlocked and claimed FEN belongs to the Chain 978 protocol support lane, where AI project hosting, access review, settlement, and work records can be described as one coherent public system.
05 / reward branchFENpoolOnly unlocked and claimed FEN can enter FENpool reward accounting; P-FEN and locked or unclaimed FEN remain outside that rewards branch.
06 / research branchN521The N path remains a separately described research branch where any future N minting requires burned FEN under published migration rules and does not collapse Chain 521 into Chain 978.
The combined protocol page can show both chain progress panels, but the claims remain separated: Chain 978 is the FEN support chain, and Chain 521 is the N/P-521 research chain.
FEN token-state discipline is a section inside the larger Fenrua thesis. FENswap brings supported external source assets into a stablecoin-value quote. The quote returns a P-FEN receipt for the FENpresale path. P-FEN is a non-transferable ERC-20 presale receipt token. When the presale ends, users burn P-FEN into the presale contract to claim unlocked presale FEN according to the published cliff schedule. Only unlocked and claimed FEN can then move into later protocol choices: N migration under published burn rules or FENpool rewards.
hosting thesis
Why FENchain is a credible base for AI project hosting.
AI project hosting needs a settlement surface where gas cost, access review, support workload, and evidence publication are designed as a single operational surface rather than scattered across unrelated dashboards.
Fenrua’s public posture is strongest when every participation claim is attached to source excerpts, hashes, report outcomes, chain IDs, token-flow constraints, and live block progress that a technical reviewer can inspect before interacting.
The two-chain framing is deliberate: Chain 978 carries the FEN protocol support economy, while Chain 521 carries N/P-521 research evidence, and the public UI must preserve that boundary so hosting readiness and cryptographic research are not conflated.
FENiOS gives the protocol a coordination grammar for AI builders: project intake, work specification, access-review context, release state, support escalation, and evidence publication all become visible concepts without exposing protected execution infrastructure.
Public trust boundary.
Public pages show chain identifiers, block progress, contract names, curated source evidence, report hashes, token-flow rules, and legal boundaries.
Public pages do not expose private control paths, privileged procedures, reserve actions, validator credentials, or protected execution surfaces.
The protocol language keeps FEN, P-FEN, FENpool, and N521 in distinct roles so a reader can understand what is a receipt, what is claimed FEN, what is reward-eligible, and what remains research-gated.
FENtrust first
Source excerpts, report hashes, public trust language, and token-flow constraints are placed before participation copy so technical readers can verify claims before they evaluate access.
FENchain 978
The support chain is presented as the low-fee protocol lane for AI hosting, FEN settlement, builder support, and live continuity evidence.
FENn521
The research chain is presented as a separate N/P-521 evidence lane with its own block progress, release boundary, and cryptographic research vocabulary.