Skip to content

Transparency & Security

Clear words for every stage

Web3 projects often blur the line between an idea and a working feature. We don't. Every utility on this site is labeled with one of the stages below, and nothing moves up a stage without verified evidence.

Feature stages

Proposed → audited: what each word means

  1. Proposed utility

    Described in documentation only. Nothing has been implemented, and the design may still change.

  2. Feature in development

    Actively being built. Not available for use, and details may change before release.

  3. Tested feature

    Implementation is complete and has been verified internally by the project team.

  4. Deployed feature

    Live on-chain or in production and available to use under published rules.

  5. Verified feature

    Independently confirmable on-chain or through official project records.

  6. Independently audited feature

    Reviewed by an external security auditor with a published report. No SNVA component has an audit report at this time.

No audit claims

No SNVA component — the token contract, staking, liquidity, or any other part of the ecosystem — has been independently audited. No security certifications are claimed. If an independent audit is ever completed, its report will be published here verbatim.

On-chain

Token contract

The SNVA token lives on Sidra Chain. The address below is the one currently associated with the project, and it is subject to verification.

SidraNova (SNVA) token contract

Subject to verification
0x29c6c953e7436170f79d3106639194d506d15d37

The official Sidra Explorer link will be added here once the exact explorer URL has been confirmed. Until then, do not trust explorer links from unofficial sources — and always verify a contract address through more than one channel before interacting with it.

Our commitments

What we do and don't claim

We don't claim

  • That an entire utility is live merely because one component exists.
  • Locked liquidity, locked allocations, or completed distributions.
  • Partnerships, sponsorships, or partner benefits.
  • User counts, reward balances, votes, or any usage statistics.
  • Independent audits or security certifications.
  • Guaranteed returns of any kind.

We do commit to

  • Honest, evidence-based feature statuses on every page.
  • Publishing on-chain verification before claiming anything is deployed or verified.
  • Clear separation of proposed figures from verified facts.
  • Never asking for private keys or seed phrases.
  • Keeping financial transactions out of the site until features are officially approved and tested.
  • Updating this page when any claim changes — in either direction.

Questions about any claim on this site? Ask through the project's official channels before making decisions — and review the SNVA utility framework and proposed tokenomics.

Community platform status

Website community features. "Live" means implemented and verified working against the real backend.

Overall Community Platform

Remaining blocker: Super Admin and administrator management passed database security tests but has not yet been exercised through the website with a real second account; the second designated Super Admin has not registered yet; password sign-in and password reset still need end-to-end verification.

In Development
  • Automatic Daily Quiz and Community Points

    Hourly scheduled generation, server-side grading, one attempt per member and non-redeemable Community Points pass isolated database tests. No reviewed questions are approved yet, so no live quiz has been published or completed by a real member.

    In Development
  • Interactive community feed

    Member posts, comments, reactions, opt-in community profiles and moderated reporting are being implemented and acceptance-tested; not approved Live.

    In Development
  • Community guidelines

    Public page renders on desktop and mobile.

    Live
  • Public announcements feed

    Loads published announcements from the database; shows an empty state when none exist.

    Live
  • Account registration

    A real member account was created through the Join page and exists in the auth service.

    Live
  • Email verification

    That member account is marked email-confirmed, which happens only via the emailed link.

    Live
  • Email and password sign-in

    Built; not yet exercised end-to-end with a typed email and password during verification.

    In Development
  • Sign out and protected member area

    Signed-in tests: sign out from the mobile menu, dashboard, and settings clears the session; dashboard and settings then redirect to sign-in on desktop and mobile.

    Live
  • Password reset

    Reset request and new-password page built; email link not yet verified end-to-end.

    In Development
  • Member profiles

    Signed-in test edited the display name, saved, and read it back after reload; own-profile-only access enforced by database policy.

    Live
  • Administrator announcement management

    Now governed by individual permissions (read, create, edit, publish, archive). Database tests confirmed each permission is enforced separately; not yet exercised through the website by an appointed administrator.

    In Development
  • Super Admin and administrator management

    One designated Super Admin is provisioned (verified email). Rolled-back database tests passed for appoint, change duties, suspend, reactivate, revoke, self-escalation blocking, last-Super-Admin protection, and append-only audit log. The second designated account has not registered; website flow with a real appointed administrator not yet verified.

    In Development