Public chain surface
Chain 978
Latest block
Reading
Sample move
+0
Chain ID
978
Public block read is pending; this card updates when the current block is returned.
Fenrua public thesis
Fenrua is being built for AI teams that need low-fee infrastructure they can actually explain: live work records, settlement context, support workflows, and public evidence in one place. Chain 978 carries the practical hosting lane. Chain 521 keeps the P-521 research lane separate.
The homepage works like a public cockpit for the protocol: live blocks, source-backed evidence, receipt rules, token-state boundaries, and FENiOS review context are visible immediately, while keys, routes, validators, and protected execution stay out of the browser.
The goal is simple: give serious builders a place where the chain, the research, the token accounting, and the AI workflow story all line up before anyone is asked to trust a promise, connect a wallet, or read a private operator document.
Chain 978 keeps the support lane practical: low-fee AI hosting, work records, settlement context, and public continuity.
Chain N521 keeps the research lane separate: P-521 signature evidence, N asset context, circuit shape, and release gates.
FENiOS turns project intent into chain-aware requirements, evidence obligations, and review-ready protocol language.
FENtrust keeps the public proof surface close to source excerpts, report hashes, trust statements, and non-claim boundaries.
FEN token state stays ordered: FENswap quote, P-FEN receipt, burn-to-claim FEN, then FENpool rewards or N migration.
Live chain progress
Chain 978 and Chain 521 stay visible from the first viewport. Last refresh: pending
Reading public block progress...
Public chain surface
Latest block
Reading
Sample move
+0
Chain ID
978
Public block read is pending; this card updates when the current block is returned.
Public chain surface
Latest block
Reading
Sample move
+0
Chain ID
521
Public block read is pending; this card updates when the current block is returned.
Live support-chain progress for FEN protocol and AI project hosting.
Isolated N/P-521 research lane with 132-byte signature evidence.
Protocol OS for chain-aware AI project context and evidence-conditioned review.
Contract source, report hashes, public statements, and source evidence rendered directly.
Ten FEN pillar table of contents
Each section has an object studied, a primary claim, an evidence corpus, and a non-claim so the protocol reads as a defended research system rather than a feature grid.
Vision first: dual-chain AI protocol research. Proof second: live chains, P-521 evidence, FENiOS, FENtrust. Token mechanics third: FENswap, P-FEN, FENpresale, FENpool. The table keeps those layers in order so readers meet the thesis before the mechanism. Each pillar names what it proves, what it does not prove, and where its evidence lives. Vision stays above acquisition, proof stays above promotion, and token mechanics stay downstream of claim boundaries.
System object: Dual-chain protocol system model.
Primary claim: Fenrua separates support-chain execution, research-chain evidence, token-state accounting, FENiOS review, and public trust proof into distinct surfaces.
Evidence corpus: Chain IDs, live progress, FEN token-state flow, source-backed trust records.
Non-claim: Not a single-token landing page or a browser control plane.
System object: Receipt-backed FEN acquisition section.
Primary claim: FENpresale defines P-FEN as non-transferable receipt state before burn-to-claim FEN.
Evidence corpus: PFENPresale source excerpts, reserve rules, stage facts, claim schedule.
Non-claim: Not liquid FEN, reward eligibility, or the Fenrua thesis itself.
System object: Ingress method for supported source assets.
Primary claim: FENswap normalizes source assets into stablecoin-value quote language and expected P-FEN output.
Evidence corpus: Quote preview language, route boundaries, receive-state copy.
Non-claim: Not the public identity of the protocol.
System object: Post-claim reward-accounting state.
Primary claim: Reward eligibility begins only after FEN is unlocked and claimed, then staked into funded epochs.
Evidence corpus: Eligibility exclusions, funded epoch rules, no fixed APY boundary.
Non-claim: Not a presale entitlement or P-FEN staking surface.
System object: Chain 978 support-chain lane.
Primary claim: Chain 978 is the low-fee execution and evidence layer for AI project hosting, FEN settlement context, builder workflow coordination, and public protocol observability.
Evidence corpus: Chain 978 identity, live block progress, support-chain boundaries.
Non-claim: Not proof for Chain 521 cryptographic research claims.
System object: Chain 521 N/P-521 research lane.
Primary claim: Chain 521 isolates P-521 signature evidence, Groth16 shape work, N asset research, and multisig-gated release posture.
Evidence corpus: 132-byte signature evidence, vector corpus, proof cases, constraints, gas rows.
Non-claim: Not a support-chain hosting claim or unrestricted production verifier release.
System object: Evidence-aware intelligence operating layer.
Primary claim: FENiOS converts AI project intent into chain-aware requirements, evidence obligations, risk boundaries, and review-ready protocol language.
Evidence corpus: OS flow map, review interface, state-separation invariants.
Non-claim: Not a generic chatbot or privileged execution interface.
System object: Economic-continuity policy section.
Primary claim: FENdef exposes public economic observability while protecting formula and route internals that would be adversarial to publish.
Evidence corpus: FENGad, FENGas, FENSup, signed quote discipline, policy boundaries.
Non-claim: Not formula disclosure or a market-performance guarantee.
System object: Source-backed evidence corpus.
Primary claim: FENtrust renders public statements, source indexes, source snippets, report hashes, and full contract panels directly in the UI.
Evidence corpus: Trust statement, SHA references, PFENPresale snippets, audit summary.
Non-claim: Not proof of price, liquidity, yield, or future audit scope.
System object: Public signal and governance appendix.
Primary claim: FENcouncil records public voice without turning holder sentiment into execution authority.
Evidence corpus: Proposal signals, non-binding voting context, execution boundaries.
Non-claim: Not funds movement, contract mutation, validator action, or privileged control.
public observations
Live Chain 978 support-chain progress.
Isolated Chain 521 research lane.
132-byte P-521 signature evidence.
FENiOS protocol OS for AI project context.
Source-backed FENtrust evidence corpus.
P-FEN receipt discipline prevents presale/liquid-FEN ambiguity.
FENiOS intelligence architecture
FENiOS is where the protocol stops being only chain infrastructure. It is the operating layer that converts AI project intent into chain-aware requirements, evidence obligations, risk boundaries, and review-ready protocol language. It binds project context, token-state separation, chain lane selection, and source-backed proof into one review architecture so builders can move between FENswap, Chain 978, Chain N521, FENtrust, and protected review without collapsing those surfaces together.
Open FENiOSFENn521 research corpus
The N/P-521 dossier is the second proof surface, not a lower route card. It keeps cryptographic research evidence, N asset context, circuit shape, gas observations, and release posture outside the Chain 978 hosting claim.
Vector cases
7
P-521 valid and adversarial signature cases.
Signature shape
132 bytes
P-521 r + s, each 66 bytes.
Groth16 proof cases
6
ECDSA-shaped proof and rejection cases.
Circuit constraints
13,361
Visible circuit traceability marker.
Chain progress
521
Research-chain liveness stays distinct.
Release boundary
multisig
Public evidence without premature release claims.
FEN token-state model
Token-state mechanics remain visible because they are part of the public proof burden. Receipt state, claimed FEN, reward eligibility, and N migration are ordered states, not interchangeable marketing words.
support chain
978 / 0x3d2
AI hosting support, settlement context, builder workflow, and continuity.
research chain
521 / 0x209
N/P-521 evidence, signature shape, and gated release posture.
receipt state
P-FEN
Non-transferable presale accounting before burn-to-claim.
eligible state
claimed FEN
Unlocked and claimed FEN only; P-FEN stays excluded.
FENpresale is receipt-backed acquisition, not the Fenrua thesis itself.
Lower-page mechanism section
The preview console remains useful for supported source assets, quote expiry, slippage discipline, route fees, and receive-path review. It appears after the protocol, research, OS, and trust thesis because the console is a mechanism inside the system.
Receipt-backed acquisition inside the broader Fenrua protocol thesis.
Ingress method for source value, with visible output kept in P-FEN language.
Reward eligibility begins after claimed FEN, not at presale receipt state.
FENswap
FENswap is the public quote-review surface for supported source assets. Users connect a wallet, select a source asset, review stablecoin-value basis, preview expected P-FEN, and continue toward FENpresale evidence. P-FEN is a non-transferable ERC-20 presale receipt token.
FENReLK / FENUnLK ratio
balanced continuityFEN / execution gas quote
source-chain gasFEN supply verdict / weekly epoch
weekly epochFENDEF indicators keep continuity, gas, and weekly supply posture clear before any final FENpresale entry can move.
Preview ratio
1 USDT = 100 P-FENStablecoin value
$125 source valueFENswap fee
refreshing quoteQuote status
receive path pendingGas cost
BNB gasBalance check
amount coveredLegal and support utilities
The protocol map is the main product surface; legal, privacy, security, accessibility, and support pages remain compact utilities that define what the public site is allowed to communicate and what remains protected.
Legal, privacy, terms, cookies, security, accessibility, and support pages remain available as compact trust utilities.
Public pages explain protocol evidence and boundaries; they do not ask users for private keys, seed phrases, privileged credentials, or regulated material.
FENswap, FENpresale, FENpool, FENchain, and FENn521 are described as separate states and lanes so receipt status, claimed inventory, rewards, and research migration do not blur.
Reference pages
These links are intentionally secondary to the protocol map, but they remain present so reviewers can inspect terms, risk language, privacy posture, accessibility commitments, and support contact paths without searching through the product.