Asset control
If a vulnerable signing key is compromised, an attacker could authorize transactions that the network accepts.
Long-term asset security depends on the authorization scheme as well as the transaction record.
Products / Blockchain
Mainnet in preparationDytallix L1
Evaluate before you deploy.
Dytallix L1 is designed to preserve authorization of shared records and digital assets through the quantum transition. The early-alpha testnet is retired. Follow the mainnet launch simulations and review the protocol before committing to deployment.
Quantum risk
Trust in transactions
Blockchains use digital signatures to decide who can authorize a transaction.
A sufficiently capable quantum computer could break widely used public-key signature schemes. A permanent record does not by itself prevent a forged authorization.
Source: NIST
Shared records
Forged signatures could make false approvals or new records appear to come from a trusted party.
Post-quantum authorization addresses that risk. It does not make public data confidential or prove that submitted information is true.
Dytallix L1
Post-quantum protocol
Dytallix L1 is a base blockchain designed around post-quantum transaction authorization. The launch simulations and the public repository let your team check the protocol's assumptions before mainnet.
Accounts
Review account control, key rotation, and recovery in the protocol design and the launch simulations.
Transactions
Review how the network checks signatures, fees, transaction order, and state changes.
Applications
Review the Rust and WebAssembly execution model before selecting a build for integration.
Shared records
Evaluate public proof references while keeping confidential source files outside the blockchain.
How it works
Launch path
- 01
Build the simulation tools and prove each one in the CI staging network.
- 02
Run the staging tests and the statistical campaign on the production hosts.
- 03
Freeze the release candidate for Hashlock's audit and a 30-day public review.
- 04
Pass seven full launch simulations on the final candidate, then sign and start genesis.
Before you plan
Check the launch status and the protocol references before you allocate engineering work.
- Launch status
- Follow the launch simulations and their evidence before planning integration.
- Network
- Confirm the chain identifier, fee denomination, and current status.
- Implementation
- Check repository instructions and the selected version before integration.
- Readiness
- Mainnet launches after the seven launch simulations pass. It is labeled unaudited until Hashlock's report is published.
Limits
Post-quantum signatures protect authorization. Public transaction data remains public. Contract defects, endpoint compromise, key loss, and governance failures remain separate risks.
Use cases
Application teams
Check whether the protocol fits your application's transaction and execution requirements before committing engineering resources.
Asset issuers
Evaluate the account and authorization model for a proposed digital asset. Check control and transfer rules in the protocol design before mainnet.
Record keepers
Assess whether a shared proof reference improves record verification without publishing the underlying confidential files.
Security researchers
Examine the cryptographic choices and trust assumptions. Compare the protocol papers with the selected implementation.
Infrastructure teams
Use the published pass criteria and monitoring design to define integration requirements before planning an operational deployment.
Protocol developers
Investigate unresolved protocol questions and contribute evidence that helps determine readiness for further use.