StableNexus
Docs

Stablecoin

A stablecoin is issued by a named issuer under a defined legal basis, backed according to the published reserve model, and redeemed under explicit operating terms.

Introduction

This stablecoin is issued by [Issuer SPV] under [Applicable Legislation]. [Reserve Bank] holds eligible reserves, [Attestor / Auditor] publishes assurance outputs, [Redemption Agent] executes fiat redemption, and StableNexus operates the policy, workflow, evidence, and publication layer.

Read this family when you need the issuer, reserve, redemption, technology, and legal record in one place.

Boundary note

This stablecoin family remains distinct from bank-issued tokenized deposits, tokenized fund shares, and partner-bank cash legs inside tokenized-asset programmes.

Those adjacent families are linked below so readers can compare the money form, appointed roles, and close conditions without blurring them together.

Program at a glance

Issuer
[Issuer SPV]
Legal basis
[Applicable Legislation]
Reserve bank
[Reserve Bank]
Attestation / audit
[Attestor / Auditor]
Redemption execution
[Redemption Agent]
Primary chain
[Primary Chain]
Contract
[Contract Address]

SNXU demo token record

Current public proof entry for the active SNXU demo token surface.

DemoUnbackedNon-redeemable
Public token
SNXU
Canonical mint
F5Se1mWY6BW2MgpoJF618hSRYqno8guWnMVPBaFDm523
Claim state
demo_emulated
Metadata path
/tokens/snxu.json
Inspect SNXU demo token recordMetadata JSONCanonical mint on Solana Explorer

Participant and responsibility map

Each role stays separate so readers can see who issues, who holds reserves, who redeems, and who publishes the workflow evidence.

RoleResponsible for
[Issuer SPV]Issuance authority, redemption authority, program notices, and legal responsibility for the instrument.
[Reserve Bank]Holding eligible reserve balances and confirming reserve-side funds receipt before issuance.
[Attestor / Auditor]Independent review of reserve balances, supply reporting, methodology, and publication cadence.
[Redemption Agent]Fiat payout workflow, settlement handling, and redemption completion operations.
StableNexusPolicy controls, workflow orchestration, evidence outputs, section publishing, and operational visibility.
Holders and counterpartiesAcquisition, holding, transfer, redemption requests, and compliance submissions where required.

Issuance and lifecycle map

  1. Eligibility and onboarding are completed under the applicable legal and compliance standard.
  2. Fiat funds are received into the reserve-side banking structure operated with [Reserve Bank].
  3. [Issuer SPV] authorizes issuance only after funding and control checks are complete.
  4. Tokens are issued on [Primary Chain] under the published contract and authority model.
  5. Circulation, transfer restrictions if any, and holder records follow the published operating rules.
  6. Reserve reconciliation, circulating-supply publication, and assurance outputs are published on the documented cadence.
  7. Redemption requests are submitted through the documented process, then completed through token return, supply reduction, and fiat payout.

Key issuance controls

  • Issuance occurs only against received funds and approved operating instructions.
  • Reserve coverage is defined at the documentation level, not only inside a marketing statement.
  • Independent assurance has a named scope, cadence, and archive path.
  • Redemption follows a documented workflow with refusal, suspension, and notice handling.
  • Token authorities, transfer rules, and contract references are published in technical references and reader-facing docs.

Issuance prerequisites

  • An enabling legal basis and issuer authority.
  • A named issuer entity with documented operating agreements.
  • Reserve banking and account structure.
  • Independent attestation or audit arrangement.
  • Redemption execution setup and settlement path.
  • Published chain, contract, and operational notice framework.