Skip to content

Support Readiness

Support readiness

Use this page before contacting Fenrua Nexus about wallet access, FEN protocol support, N521 research context, FENiOS workflows, access-review status, or protected participation questions.

Last updated: July 2, 2026

Public trust statement

Fenrua Nexus is a public protocol monograph for the FEN protocol, N521 research, and FENiOS. Public pages show abstracts, research questions, formal claims, chain IDs, live block progress, published contract names, source status, readiness labels, evidence tables, source excerpts, and legal boundaries. Protected execution details and private operations stay out of the UI.

Allowed public verification data includes chain 978, chain 521, live block progress, contract names, source status, receipt or audit hashes, token supply facts, reserve facts, and user-facing readiness labels.

Open FEN trust and SHA evidence

When to contact support

  • Wallet connection, receive-address flow, or FENswap quote readiness is not completing as expected.
  • Access review or protected participation status looks missing, incorrect, or out of date.
  • A FENchain, FENswap, N521 research, FENiOS, treasury, validator, or governance readiness question needs a human review path.
  • A council holder comment, FENvault send, or receive-lane check behaves unexpectedly.

What to include

  • Wallet address and selected participation path, if relevant.
  • Which step is blocked: wallet connection, FENswap P-FEN preview, FENpresale receipt review, or protected participation readiness.
  • Approximate time of the issue and the browser or device where it happened.
  • For FENpresale, access review, protocol, or FENchain questions, include only public transaction hashes or non-sensitive context.

What not to send

  • Do not send passwords, private keys, seed phrases, recovery phrases, privileged credentials, or third-party credentials.
  • Remove regulated, confidential, financial, medical, or third-party private data from screenshots before sending.
  • Use the official Fenrua Nexus support email path instead of replying to unknown wallet, funding, or relay instructions.
  • Support can review account and access-track context, but protected execution remains gated.

Admin and operator boundary

  • Privileged decisions are not made in browser code, and public pages do not expose private operator account details.
  • Access review, privileged action approval, relay operation, and abuse-review outcomes stay in protected operational systems.
  • The public account page can show readiness metadata when available; it does not reveal private credentials, privileged internals, private keys, or relayer secrets.
  • Manual support review may delay or decline access when security, abuse-prevention, or account-integrity checks require it.

Contact path

Send support requests to partnerships@fenrua.ai. Keep the message concise, include the non-sensitive details above, and avoid sending secrets or regulated data through email.