Quantova

Foundational blockchain platform powering decentralized apps, stablecoins, and post quantum resistant smart contracts via QVM.

[Quantova @QuantovaGlobal]

Building a Post Quantum Layer 1 from the ground up.

Not upgrading cryptography, redesigning consensus, execution, and verification for new constraints.

If you’re working on infrastructure, research, or exploring this space, open to connect.

[Quantova @QuantovaGlobal]

@coinjoined The issue is that quantum risk introduces irreversibility.
If key recovery becomes feasible, failure is catastrophic and non recoverable at the UTXO level

[Quantova @QuantovaGlobal]

This is why PQ isn’t just about stronger primitives

You need systems that assume imperfect coordination and adversarial conditions by default. Quantova approaches this at the protocol level

[Quantova @QuantovaGlobal]

State desynchronization is an under discussed risk in post-quantum systems

Many PQ schemes (e.g., hash based signatures) rely on
stateful usage bounds. Break that assumption across devices → you risk key reuse and signature forgeries

[Quantova @QuantovaGlobal]

In multi device environments, perfect coordination is unrealistic
Desync can occur via:
- concurrent signing
- backup/restore events
- partial state replication
Security then depends on state management guarantees

[Quantova @QuantovaGlobal]

@therollupco cryptographic assumptions change - systems must adapt accordingly

[Quantova @QuantovaGlobal]

@WuBlockchain P2PK outputs are structurally vulnerable under Shor, but freezing them introduces intervention and consensus complexity that’s arguably just as hard

[Quantova @QuantovaGlobal]

@TheBlockCo Glad the migration is happening, check out Quantova ( post quantum by protocol)

[Quantova @QuantovaGlobal]

Quantova will be attending @festival_web3 Hong Kong 🇭🇰

Looking forward to connecting with builders and researchers shaping the future of decentralized and post-quantum infrastructure

[Quantova @QuantovaGlobal]

@akashneelesh 😀😀😀

[Quantova @QuantovaGlobal]

@murchandamus Curious how it models mixed security states and asymmetric risk during the migration?

[Quantova @QuantovaGlobal]

Post quantum Bitcoin research is clearly accelerating

[BTC Times @BTCTimescom]

Post-quantum #Bitcoin research is gaining momentum as @n1ckler introduces SHRIMPS multi-device signatures, @avihu28 proposes quantum-safe transactions without a soft fork, and @roasbeef develops a zk-STARK wallet recovery prototype focused on long-term security.

https://t.co/vWS0Zg9ixm

[Quantova @QuantovaGlobal]

@kostascrypto Curious how you’re handling verification overhead, object growth, and validator load with PQ primitives deployed

[Quantova @QuantovaGlobal]

@NoodlesFi @kostascrypto Upgrading keys ≠ making a system quantum resistant

[Quantova @QuantovaGlobal]

@TheBlockCo You don’t wait for certainty
to start preparing for irreversible failure modes

[Quantova @QuantovaGlobal]

@WizzyOnChain key exposure + user inactivity, not just cryptography

[Quantova @QuantovaGlobal]

@tomshardware Great to see the movement

[Quantova @QuantovaGlobal]

GITEX AI Asia @gitexasia - Day 2 🇸🇬

Discussing quantum strategies, migration paths, and designing systems under new cryptographic assumptions

[Quantova @QuantovaGlobal]

interesting direction

Using zk proofs to preserve ownership under a keyspend disabling soft fork addresses one of the hardest problems - recovering funds without exposing additional key material
Trade offs around prove time, memory, and proof size will be critical for the viability

[Olaoluwa Osuntokun @roasbeef]

in the face of quantum adversary, a commonly discussed emergency soft fork for Bitcoin would be to disable the Taproot keyspend path (https://t.co/AQo96JiYQ7), effectively turning it into something that resembling BIP-360

assuming an existing precautionary soft-fork to add a pq signature scheme, this would safely allow holders to maintain unilaterally custody of their funds

a downside to this proposal is that any keyspend-only (normal schnorr sig) would be locked indefinitely

inspired by https://t.co/rBJMpJ8sR0, I set out to address the option problem in section 6, to create a variant of seed-lifting that doesn't reveal the wallet's master secret! 🤓

the end result is a zk-STARK proof that proves: "public key P was generated using a private key k, which itself was derived via BIP-32/BIP-86 with a master wallet secret S"

this generalizes beyond Taproot, and would allow the rightful owners of any BIP-32 derived wallets to move their funds in het case of a spend disabeling emergency softfork 🛡️

the final proof takes 50 seconds to run on my MacBook with Metal GPU acceleration, uses 12 GB of RAM during proving, with a final proof size of 1.7 MB

the proving code/statement is largely unoptimized, and it's possible to aggregate several proofs into a single smaller proof ⨻

an actual production deployment would likely use a smaller optimize circuit for this specific statement, this demo serves to demonstrate that such a proof is well within reach w/ today's hardware+software

to generate the proof I forked TinyGo to add a risc0 RISC-V ELF compilation target for TinyGo: https://t.co/eAMrgzh0x6

then I used some helper utilities and a C FFI wrapped risc0 library to create a generalized toolkit for TinyGo zk-STARK proofs: https://t.co/urVS6r1kA7

the final guest+host lives in the bip32-pq-zkp repo: https://t.co/7CoF0oL384

such a proof scheme is yet another tool in the post quantum toolkit for Bitcoin developers to prepare for an eventual PQ world 🤠

full details in my post to the Bitcoin dev mailing list: https://t.co/I6TlRfDoCC

[Quantova @QuantovaGlobal]

@Upcxofficial Great to see the shift is happening

[Quantova @QuantovaGlobal]

At the Quantum Advantage for Business Leaders workshop.

Discussions around real world quantum progress are accelerating, and so is the need for post-quantum ready infrastructure