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
Early-alpha testnetDytallix L1
Evaluate before you deploy.
Dytallix L1 is designed to preserve authorization of shared records and digital assets through the quantum transition. Use the early-alpha testnet to evaluate 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 early-alpha testnet lets your team inspect transactions and shared records while evaluating the protocol's assumptions.
Accounts
Use testnet keys to evaluate account control, balances, and transaction history.
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
Testnet workflow
- 01
Check network status and confirm the chain identifier and selected build.
- 02
Create a testnet account in the Wallet and request test assets from the faucet.
- 03
Submit a supported test transaction. Review its authorization, fee, and result.
- 04
Inspect the transaction and block record in the Explorer. Record failures and unresolved questions before extending the test.
Before testing
Check current network status and the protocol references before you allocate engineering work.
- Account
- Use testnet keys and test assets. The Wallet includes access to the faucet.
- Network
- Confirm the chain identifier, fee denomination, and current status.
- Implementation
- Check repository instructions and the selected version before integration.
- Readiness
- The early-alpha testnet does not establish mainnet or production readiness.
Limits
Post-quantum signatures protect authorization. Public transaction data remains public. Contract defects, endpoint compromise, key loss, and governance failures remain separate risks. Testnet assets have no production value.
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. Test control and transfer behavior using assets with no production value.
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 testnet activity to define monitoring and integration requirements before planning an operational deployment.
Protocol developers
Investigate unresolved protocol questions and contribute evidence that helps determine readiness for further use.