---
title: Sui shipped an ML-DSA-65 signature scheme in a devnet release, and the rating held
description: On 13 October 2026 the index recorded Sui's devnet-v1.82.0 release registering ML-DSA-65 as signature scheme 7. Devnet only, so the rating held.
url: "https://hardyindex.com/news/sui-devnet-release-registers-ml-dsa-65-signature-scheme"
section: What was announced
type: development
published: 2026-11-05
updated: 2026-11-05
chains: sui
methodology_version: 1.8
---

# Sui shipped an ML-DSA-65 signature scheme in a devnet release, and the rating held

**On 13 October 2026 the index recorded Sui's devnet-v1.82.0 release, which registers ML-DSA-65 as signature scheme 7 and verifies those signatures end to end. It moves no rating. Devnet state is reset regularly, mainnet accounts still use Ed25519, and no SUI holder can protect funds with a post-quantum key today.**

*Published 5 November 2026. The rating below is current as of 17 November 2026. This is a security-readiness assessment, not investment advice.*

A devnet release gave Sui a working post-quantum signature path, but devnet is wiped on a schedule and mainnet accounts still sign with Ed25519.

## What shipped on 12 October

MystenLabs published the devnet-v1.82.0 release of the Sui node on 12 October 2026. The index read it and recorded it as a development on 13 October.

ML-DSA-65 is a lattice-based digital signature algorithm standardised by NIST as FIPS 204. It is designed so that a large quantum computer cannot forge a signature from a public key, which is the thing today's Ed25519 keys would not survive.

- ML-DSA-65 is registered as signature scheme 7, so the node has a slot for it rather than a patch bolted on the side.
- ExecuteTransaction accepts ML-DSA-65 signatures, including as members of a multisig.
- VerifySignature checks them, so the path runs from submission to verification.
- Matching GraphQL and Rust SDK types landed, which is what tooling needs before anyone outside the core team can use it.

This follows the merge we covered in [Sui's post-quantum account signatures landing in the node](https://hardyindex.com/news/sui-ml-dsa-65-account-signatures-merged-devnet-only). The release is the same work reaching a cut that people can actually run.

How Sui got here

- **13 August 2024**: NIST publishes FIPS 204, the final standard for ML-DSA, the signature algorithm Sui has adopted.
  Source: https://csrc.nist.gov/pubs/fips/204/final
- **12 October 2026**: MystenLabs publishes devnet-v1.82.0, registering ML-DSA-65 as signature scheme 7 with verification and SDK support.
  Source: https://github.com/MystenLabs/sui/releases/tag/devnet-v1.82.0

## What this does not do

Devnet is a throwaway network. Sui resets its state on a regular cadence, so an account you create there is not a thing you keep. Code that works on devnet has cleared an engineering bar, not an operational one.

Your SUI on mainnet is still secured by an Ed25519 keypair. Nothing in this release changes that, and there is no setting you can switch on to change it either. If you hold SUI, your exposure today is exactly what it was last month.

> **The short version.** A release that accepts post-quantum signatures is not the same as a chain where you can hold a post-quantum account. Sui has the first. It does not yet have the second.

Sui's stated plan also covers SLH-DSA-SHA2-128s, a hash-based scheme standardised as FIPS 205, for smart contract vaults. That is a separate line of work and this release is not it.

## Why the rating did not move

The index rates what a holder can use, not what a repository contains. Sui already scores well for having a credible plan with real code behind it, and this release is consistent with that plan rather than a step beyond it.

Two things would move the signature rating:

- ML-DSA-65 accounts usable by the public on a persistent test network, one that is not wiped, so the scheme survives contact with real users and real tooling.
- ML-DSA-65 available on mainnet as a first-class account type, not an experimental flag. Sui has scheduled this for the first quarter of 2027.

Until the first of those lands, the devnet work is evidence of intent and competence, both of which are already priced into where Sui sits.

**Where this stands today.**

- [Sui](https://hardyindex.com/chains/sui): Tier 3: Committed, Hardy Score 42.0 of 100.

As rated by the Hardy Index, current as of 17 November 2026. Ratings change when the evidence does, and every change is recorded at https://hardyindex.com/changelog.md.

## If you hold SUI

There is nothing to do and nothing to move. No action is available to you yet, because the account type does not exist on mainnet.

What's worth doing is watching for the right signal. Do not treat a devnet tag or a merged pull request as the moment. The moment is when Sui tells you that you can create an ML-DSA-65 account on mainnet and your wallet supports it. We will cover that when it happens, and the rating on [the Sui page](https://hardyindex.com/chains/sui) will move with it.

If you want the general picture of how key migration works and why it is slow, start with [how to protect crypto from quantum computers](https://hardyindex.com/guides/how-to-protect-crypto-from-quantum-computers).

## Where to go next

- [Sui: the full rating](https://hardyindex.com/chains/sui.md): every dimension score, with the source behind each one.
- [Which is the most quantum-resistant blockchain?](https://hardyindex.com/guides/most-quantum-resistant-blockchain.md): One question, one answer, with the working shown. This page is a summary of the Hardy Index, which is the live ranking behind it.
- [Quantum-safe wallets: what is real and what is marketing](https://hardyindex.com/guides/quantum-safe-wallets.md): Quantum-ready is the fastest-growing label in crypto hardware. Here is what it means, what it does not, and how to choose without paying for a promise nobody can keep yet.
- [How to protect your crypto from quantum computers](https://hardyindex.com/guides/how-to-protect-crypto-from-quantum-computers.md): If you hold crypto and the quantum headlines have been bothering you, this is the practical version. Four steps, in order, with the limits of each one stated.

## Sources

Every dated event above carries its own primary source. These are those sources, checked on the dates shown.

1. [Sui devnet-v1.82.0 release notes](https://github.com/MystenLabs/sui/releases/tag/devnet-v1.82.0): MystenLabs (primary, checked 5 November 2026)
2. [FIPS 204: Module-Lattice-Based Digital Signature Standard](https://csrc.nist.gov/pubs/fips/204/final): NIST (primary, checked 5 November 2026)
3. [FIPS 205: Stateless Hash-Based Digital Signature Standard](https://csrc.nist.gov/pubs/fips/205/final): NIST (primary, checked 5 November 2026)
4. [Pull request 27810: ML-DSA-65 signature verification](https://github.com/MystenLabs/sui/pull/27810): MystenLabs (primary, checked 5 November 2026)
5. [Making Sui Quantum Ready](https://www.sui.io/blog/making-sui-quantum-ready): Sui (primary, checked 5 November 2026)

---
Cite as: The Hardy Index, "Sui shipped an ML-DSA-65 signature scheme in a devnet release, and the rating held", https://hardyindex.com/news/sui-devnet-release-registers-ml-dsa-65-signature-scheme, published 5 November 2026.
