Read before using the testnet

Risk and accuracy disclaimer.

What “post-quantum protected” means, what it does not mean and why no testnet asset should be treated as money or an investment.

Test assets onlyPublic ledgerNo auditNo investment offer

1. Testnet disclaimer

sps-testnet-1 is a public engineering test network. It may halt, fork, reset, lose state, change rules or be discontinued. The current two-validator topology requires both cities online for liveness and is not production decentralization.

Nothing on the testnet should be used for a real payment, custody decision, financial record, production application or safety-critical process.

2. No investment, financial or tax advice

No website statement, whitepaper passage, token, faucet distribution, explorer label or roadmap item is an offer to sell, solicitation to buy, recommendation, promise of profit, investment contract, deposit, security, commodity interest or financial advice.

SPS, SUSD, DEMO and user-created testnet tokens have no monetary value and no guaranteed relationship to a future production asset. There is no promise that a testnet balance, address, allocation or token will be recognized on another network. Consult qualified legal, tax and financial professionals before making decisions involving real value.

3. Post-quantum claim boundary

Sentinel uses ML-DSA-65 for validator and native-account signatures, ML-KEM-768 in hybrid peer-key establishment and ML-DSA-verifying smart contracts. These are meaningful engineering protections; they do not make the system “quantum-proof.”

  • Ordinary Ethereum EOAs and MetaMask signatures remain classical secp256k1.
  • Node identity is hybrid: ed25519 and ML-DSA-65 must both verify.
  • Server SSH identity remains classical even where hybrid key exchange is negotiated.
  • Software, operating systems, dependencies, websites and people remain attack surfaces.
  • Future cryptanalysis or implementation flaws may affect standardized primitives.

The correct description is: “post-quantum protected where documented, not independently audited.” “Impossible to hack,” “unbreakable” and “quantum-proof” are not accurate descriptions.

4. Software and cybersecurity risk

Smart contracts may contain logic errors. Consensus or networking changes may contain implementation defects. Dependencies may be compromised. Keys may be stolen, lost or misused. Rate limits and firewalls reduce risk but cannot guarantee availability or prevent every attack.

No independent cryptography, smart-contract, consensus, infrastructure or application audit has been completed. Internal tests, fuzzing, NIST vectors, live upgrades and geographic operation are not substitutes for independent review.

5. Public and trackable activity

Sentinel’s public testnet is not anonymous and does not implement confidential transactions. Addresses, balances, transaction values, token holdings, contract calls and relationships may be analyzed, indexed and correlated. Post-quantum authorization protects a signature boundary; it does not hide activity.

6. SUSD test contract

The Sentinel Dollar contract on this testnet is a technical demonstration. Its reserve attestation contains conspicuous TEST language. No bank account, permitted issuer, reserve custodian, accounting opinion, redemption program, KYC/AML operation or legal right to dollars is represented by the test deployment.

Reserve-cap logic can verify only on-chain values supplied by an authorized attestor. It cannot inspect a bank account or prove that off-chain assets exist.

7. Availability and data risk

The RPC, faucet, explorer and website may be unavailable, rate-limited or changed. Testnet data may be pruned, replaced or reindexed. Wallet software may display stale or incorrect information. Users must independently verify chain ID, contract address and transaction status.

8. Forward-looking statements

Roadmaps, production targets, performance plans, validator expansion, legal structures, audits, SUSD plans and future features describe intentions, not commitments. Timing, scope and feasibility may change materially.

These disclosures are operational transparency, not legal advice. A production launch requires a designated legal entity, counsel-approved terms and privacy notices, regulatory analysis, security-review program and complete contact and dispute provisions.