[ANN]NADO - PoSEA: mine a post-quantum chain from your phone. Fair launch, no premine

[BoozyTalking]

Code:

08:00:45 Renewed with a Windows Hello confirmation — no attestation needed.
08:00:45 Submitting register tx 1f2b1082590dcdc3… (max_block 31264) via https://get.nadochain.com.
08:00:46 Register rejected by relay: Could not merge remote transaction: signature renewal rejected: RS256 signature does not verify

Something is broken again.

[HCLivess]

Code:

08:00:45 Renewed with a Windows Hello confirmation — no attestation needed.
08:00:45 Submitting register tx 1f2b1082590dcdc3… (max_block 31264) via https://get.nadochain.com.
08:00:46 Register rejected by relay: Could not merge remote transaction: signature renewal rejected: RS256 signature does not verify

Something is broken again.

thats just a second attempt on pending registration, wording fixed

[HCLivess]

Update — what changed on betanet since the last post

TPMs without a Microsoft certificate can now mine (AIK oracles).
For a large minority of PCs, Microsoft's attestation service answers 404: the chip is genuine, Microsoft just has no authority registered for it. On Linux no such service exists at all. NADO nodes now do that job: three are drawn at random, each seals a secret to your chip's endorsement key, and only the real chip can open all three. Open the wallet on the PC, press Start collecting, and run the TPM enrolment helper it offers (Windows or Linux). Nothing to paste, and the key never leaves the browser.

Staking is plain stake now.
Bond 10 NADO from the Savings tab and you are in the bonded draw, one coin, one weight. No device, no lease and no pool. We measured the device requirement and the knee curve on the live lane, and neither stopped anyone, so both are gone. The numbers are in the README.

Pools retired.
Once the bonded lane went device-free, a pool could only pay a delegator less than solo staking. Delegators were getting 51–79% of solo.

Still the same core:
- One device, one identity (Android TEE, TPM 2.0, Ledger, Trezor Safe)
- ML-DSA-44 signatures throughout
- Zero premine
- A keyless treasury that only a 2/3 stake vote can spend

Start: https://get.nadochain.com
Code: https://github.com/hclivess/nado
PoSEA paper: https://doi.org/10.5281/zenodo.22749219

[HCLivess]

Update: what changed on betanet since the last post

NFT marketplace: https://nft.nadochain.com
An NFT is a native asset (zero decimals, supply = editions), so it lives in any NADO wallet and the contract only escrows it while it trades. Collections, profiles, listings, offers, English and Dutch auctions. Upload a file and it's pinned to the site's IPFS node. Each token page shows its full history: mint, transfers, sales, auctions, burns.

Only the issuer can attach a royalty, up to 25%, checked in-circuit, and every completed trade pays it through one payout path. The marketplace takes no fee. Every escrow has an exit for whoever funded it, and anyone can settle an ended auction, so funds don't wait on a seller who vanished. Mint and royalty now take one wallet approval.

Stwo: betanet-10 moved the execution layer to it.
Contracts run on a zkVM with a 256-bit word and BLAKE2s, proved with Stwo, StarkWare's Circle STARK prover. Private sends use a Stwo-proved shielded pool, with the proof built on your device in the wallet. The old Goldilocks field, VM, pools and native crates are deleted.

Stwo settlement is built and running in shadow, with settled spans proven and verified off-chain. L1 settlement stays with the bonded quorum until that rule is switched on.

Multisig and auth keys in any signature scheme, from block 123000.
That includes hash-based SLH-DSA, so an SLH-DSA account can protect and rotate itself in its own scheme, and a multisig can mix schemes. Blocks and attestations stay ML-DSA-44. The same gate fixes ordinary sends to a multisig, which could sit unmined in the mempool, and the wallet's Send tab no longer refuses a multisig address.

Smaller things.
Shadow Accounts are offered on every official app, including the DEX, lending, the games and NFT. A protected account now signs dApp requests with its authorized key. Polish is the 17th language.

Start: https://get.nadochain.com
Code: https://github.com/hclivess/nado

[fairmuffin]

Update: what changed on betanet since the last post

NFT marketplace: https://nft.nadochain.com
An NFT is a native asset (zero decimals, supply = editions), so it lives in any NADO wallet and the contract only escrows it while it trades. Collections, profiles, listings, offers, English and Dutch auctions. Upload a file and it's pinned to the site's IPFS node. Each token page shows its full history: mint, transfers, sales, auctions, burns.

Only the issuer can attach a royalty, up to 25%, checked in-circuit, and every completed trade pays it through one payout path. The marketplace takes no fee. Every escrow has an exit for whoever funded it, and anyone can settle an ended auction, so funds don't wait on a seller who vanished. Mint and royalty now take one wallet approval.

Stwo: betanet-10 moved the execution layer to it.
Contracts run on a zkVM with a 256-bit word and BLAKE2s, proved with Stwo, StarkWare's Circle STARK prover. Private sends use a Stwo-proved shielded pool, with the proof built on your device in the wallet. The old Goldilocks field, VM, pools and native crates are deleted.

Stwo settlement is built and running in shadow, with settled spans proven and verified off-chain. L1 settlement stays with the bonded quorum until that rule is switched on.

Multisig and auth keys in any signature scheme, from block 123000.
That includes hash-based SLH-DSA, so an SLH-DSA account can protect and rotate itself in its own scheme, and a multisig can mix schemes. Blocks and attestations stay ML-DSA-44. The same gate fixes ordinary sends to a multisig, which could sit unmined in the mempool, and the wallet's Send tab no longer refuses a multisig address.

Smaller things.
Shadow Accounts are offered on every official app, including the DEX, lending, the games and NFT. A protected account now signs dApp requests with its authorized key. Polish is the 17th language.

Start: https://get.nadochain.com
Code: https://github.com/hclivess/nado

I am trying to verify using the TPM and the binary available on Win11 but I am getting this on the console:

Code:

chip       3 intermediate(s) read from the chip's EK certificate chain
  chip       638 certificate(s) available from this machine's stores to link with
  chip       endorsement chain is 7 certificate(s)
  chip       endorsement chain: 7 certificate(s), 5140 bytes
  enrolment  HIDDEN
  -> publishing this chip's endorsement chain
  .. confirmed on chain
  .. waiting for the enrolment to be included (10s)
  .. waiting for the enrolment to be included (20s)
  .. waiting for the enrolment to be included (30s)
  .. waiting for the enrolment to be included (40s)
  .. waiting for the enrolment to be included (50s)
  .. waiting for the enrolment to be included (60s)
  .. waiting for the enrolment to be included (71s)
  .. waiting for the enrolment to be included (81s)
  .. the enrolment did not land within 90s; sending again
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. still 0/5 after 180s. Waiting for the enrolment window to elapse; it then re-publishes with a freshly drawn set.
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. still 0/5 after 360s. Waiting for the enrolment window to elapse; it then re-publishes with a freshly drawn set.
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered
  .. 0/5 challengers have answered

Any steps should I take for that to work?