Shell Chain

Quantum-Safe from Day One

[Shell Chain @orgShell]

A quantum-safe signature answers 'was this key forged?' It does not answer 'should this key have unlimited power?' Shell Chain's PQ session keys can be limited by target, value and expiry block, with the root key authorizing the scope. Strong keys still need least privilege.

[Shell Chain @orgShell]

Block assembly should not make transaction admission wait on heavy copies. Shell Chain's mempool holds its read lock only to select lightweight references, then clones full transactions after release. Fee priority and nonce order stay intact without stretching writer contention.

[Shell Chain @orgShell]

PQ signatures stop key forgery; they do not stop replay of a valid signed transaction. That needs message context. Shell Chain binds chain ID and nonce into the signing preimage, then enforces nonce equality before execution. Strong math still needs protocol discipline.

[Shell Chain @orgShell]

A wallet can be cryptographically correct and still trust the wrong transport. Crystal Wallet requires HTTPS for remote Shell RPC endpoints and hardens quantity parsing before values reach account logic. Post-quantum authorization does not excuse classical network hygiene.

[Shell Chain @orgShell]

Key rotation fails if the old key remains a valid fallback. In a quantum threat model, Shor-recovered signing power would survive the upgrade. Shell Chain resolves the active PQ key from protocol state, so rotation changes what the chain accepts, not just what the wallet stores.

[Shell Chain @orgShell]

Builder note: pruning and proving need an explicit handoff. Shell Chain will not prune a block's PQ witness bundle until the block is finalized and below the STARK proof frontier. Storage savings cannot delete the evidence the prover still needs.

[Shell Chain @orgShell]

A PQ public key is incomplete without its verification rule. Treat the same bytes under different algorithms as one identity and crypto agility becomes ambiguity. Shell Chain binds algorithm ID + public key into the full 32-byte address, so an account names both key and scheme.

[Shell Chain @orgShell]

Post-quantum only works if nodes can afford it. Shell Chain pairs PQ authorization with parallel signature verification, STARK witness compression and configurable storage profiles. The goal is not cryptography in isolation; it is an operable chain.

[Shell Chain @orgShell]

A post-quantum base layer cannot rescue an app with an ECDSA admin bypass. Quantum safety must cover every authority path: upgrades, treasuries, bridges and sessions. Shell Chain provides protocol-native PQ accounts so apps can keep control on the post-quantum path.

[Shell Chain @orgShell]

Pruning that marks every committed state root as permanently active is not pruning. Shell Chain removed that pinning path so finalized canonical mappings can age out under retention rules, while archive mode keeps complete history. Storage policy must match node behavior.

[Shell Chain @orgShell]

A quantum-safe wallet on a classically signed chain is only half a defense. Shor-style forgery can target block proposer seals too, changing who appears to have authorized ledger history. Shell Chain verifies post-quantum signatures for both transactions and proposer seals.

[Shell Chain @orgShell]

PQ infra needs a compatibility lab, not isolated demos. Shell Chain invites ecosystem partners, infra teams, wallet and app builders, researchers, strategic collaborators and aligned prospective investors to pressure-test key rotation and protocol validation. [email protected]

[Shell Chain @orgShell]

Does quantum break every 256-bit hash? No. Grover roughly halves the security exponent; Shor attacks classical public-key assumptions much more directly. Shell Chain answers both: PQ signatures for authorization and full 32-byte address hashes for margin.

[Shell Chain @orgShell]

Builder boundary: Shell Chain's 20-byte address mapping exists only inside the PQVM/revm compatibility layer. RPC, storage and user-facing systems must keep the canonical 32-byte address. An interoperability shim should never redefine account identity.

[Shell Chain @orgShell]

Crypto agility has a bootstrap trap: if a chain must retire an algorithm, the vote cannot depend only on that same algorithm. Shell Chain governance accepts ML-DSA-65 or hash-based SLH-DSA votes for algorithm changes, preserving a path out if one family is questioned.

[Shell Chain @orgShell]

Builder note: PQ verification belongs in the performance budget. Shell Chain's block import path can verify transaction signatures in parallel with a batch verifier across available cores. Cryptography choices shape node architecture; they are not a wallet-only concern.

[Shell Chain @orgShell]

Post-quantum is not a forever algorithm. If research changes, a chain needs to introduce a replacement without making nodes disagree. Shell Chain stages signature algorithms through pending, active and deprecated states; deprecated schemes stop authorizing new transactions.

[Shell Chain @orgShell]

Why can a wallet accept a huge balance but reject a nonce of the same size? Balances are values, so Crystal Wallet keeps them as exact big integers. Nonces drive transaction sequencing and must stay safely representable. RPC quantities need semantics, not just hex parsing.

[Shell Chain @orgShell]

Post-quantum signatures do one job: protect authorization from quantum forgery. They do not hide balances, encrypt transactions or secure a stolen device. Shell Chain changes the signing assumption; wallets still need strong keystore encryption and operational security.

[Shell Chain @orgShell]

A post-quantum chain manages more than signatures. Shell Chain gives operators archive, full and light storage profiles: keep everything, retain transaction history while replacing PQ witnesses with compact proofs, or run a rolling window. Security must fit real hardware.