Siren SIREN

Claim: SIREN is a standard BEP-20 token on BNB Chain and inherently shares the base-layer QRI score.

Coverage basis: Token inherits L1 cryptographic security model; no custom crypto or cross-chain dependencies.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Assurance: Multiple independent sources (BscScan, CoinGecko, CoinMarketCap) confirm the token is a standard BEP-20 on BNB Chain with no custom cryptographic primitives.

Token inheritance rule applies. SIREN QRI = BNB Chain QRI, adjusted only for token-specific admin/governance keys.

• https://bscscan.com/token/0x997a58129890bbda032231a52ed1ddc845fc18e1
• https://www.coingecko.com/en/coins/siren-2
• https://coinmarketcap.com/currencies/siren-bsc/

Claim: Token contract ownership is renounced; the owner address is the zero address.

Coverage basis: Renounced ownership eliminates token-specific quantum-vulnerable admin attack surface.

Implementation score: 1 · Evidence confidence: Medium

Issue classification: none · Score treatment: not applicable

Assurance: Confidence is Medium because no independent formal audit confirms the renounced ownership and absence of hidden admin paths. CertiK Skynet is an automated scan, not a full manual audit. The contract source code is verified on BscScan and shows standard OpenZeppelin Ownable with renounced ownership.

The contract includes setMode() for transfer restrictions, but this function is onlyOwner and ownership is renounced, rendering it inert. No upgradeability proxy detected.

• https://skynet.certik.com/projects/siren
• https://bscscan.com/token/0x997a58129890bbda032231a52ed1ddc845fc18e1

Claim: All SIREN token transfers are authorized via BNB Chain's ECDSA (secp256k1) transaction signatures — quantum-vulnerable.

Coverage basis: Inherited from BNB Chain L1; no token-level signature scheme exists.

Implementation score: 0 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Quantum blocker: BNB Chain mainnet production spend authorization is ECDSA-only. No PQC or hybrid-PQC signatures are available on mainnet.

Assurance: BNB Chain's own May 2026 migration report confirms current production signatures are ECDSA (secp256k1). The PQC test using ML-DSA-44 is research-only, not deployed on mainnet.

This is the primary quantum-critical vulnerability for SIREN holders. All token transfers, approvals, and interactions require ECDSA signatures that Shor's algorithm can break.

• https://bscscan.com/token/0x997a58129890bbda032231a52ed1ddc845fc18e1
• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: BNB Chain addresses and key derivation follow Ethereum-compatible ECC design; public keys are exposed on-spend and at-rest for transacted EOAs.

Coverage basis: Inherited from BNB Chain L1; BNB Chain uses keccak-256-hashed public keys in Ethereum-style addresses.

Implementation score: 0 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Quantum blocker: BNB Chain account model exposes public keys for all transacted addresses, creating long-exposure attack surfaces.

SIREN token holders use standard BNB Chain addresses. Any address that has sent a transaction has an exposed public key vulnerable to offline quantum attack.

• https://bscscan.com/token/0x997a58129890bbda032231a52ed1ddc845fc18e1
• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: BNB Chain consensus uses BLS12-381 validator vote signatures — quantum-vulnerable.

Coverage basis: N/A at token level; token has no independent consensus mechanism.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

While N/A for direct token scoring, BNB Chain consensus vulnerability indirectly threatens all tokens including SIREN if finality or chain integrity is compromised.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: Token-level state integrity is managed by the BEP-20 contract on BNB Chain; no independent state-integrity mechanisms exist at the token layer.

Coverage basis: N/A at token level.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Claim: SIREN has no privacy or ZK proof layer.

Coverage basis: N/A — token has no privacy features.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Claim: P2P networking is an L1 concern; token has no P2P layer.

Coverage basis: N/A at token level.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Claim: No PQC or hybrid-PQC wallet/custody workflows exist for BNB Chain or SIREN.

Coverage basis: Inherited from BNB Chain L1; ECC-only wallet infrastructure.

Implementation score: 0 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Quantum blocker: No production PQC wallet, custody, or HSM support exists for BNB Chain tokens.

All SIREN holdings, including exchange-held and custody-held tokens, are protected only by ECDSA keys. No hardware wallet supports PQC for BNB Chain transactions.

Claim: 0% of SIREN value is quantum-protected. All ~$344M market cap is on quantum-vulnerable BNB Chain with ECDSA-only spend authorization.

Coverage basis: <25% coverage — no migration or protection exists.

Implementation score: 0.05 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Quantum blocker: 100% of SIREN value-at-risk is quantum-vulnerable with no migration path.

Assurance: Market cap figure (~$344M) from CertiK Skynet as of evaluation date. All value is on BNB Chain mainnet with zero PQC protection.

Coverage threshold <25% maps to score of 1 out of 20 under QRI §9.3.1.

• https://skynet.certik.com/projects/siren
• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: No SIREN-critical wallets (treasuries, exchanges, custodians, bridges, foundations) are quantum-protected. Token ownership is renounced so there is no admin treasury.

Coverage basis: No critical wallets migrated or protected.

Implementation score: 0 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Assurance: CertiK data shows top holder concentration (~32% major holding ratio) but these are standard EOA/contract addresses with no PQC protection.

While token ownership is renounced (no admin treasury to protect), exchange-held and large-holder SIREN balances remain fully quantum-vulnerable.

• https://skynet.certik.com/projects/siren

Claim: No legacy vulnerable pool identification or deprecation exists at the token or L1 level.

Coverage basis: No identification or mitigation of vulnerable pools.

Implementation score: 0 · Evidence confidence: Medium

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

All SIREN balances are in standard BNB Chain accounts vulnerable to quantum attack. No freeze, burn, deprecation, or migration mechanism exists for dormant or unmigratable vulnerable holdings.

Claim: BNB Chain has published a PQC migration research report (May 2026). SIREN has no independent roadmap.

Coverage basis: Inherited from BNB Chain; research report exists but is a proposal, not a committed deployment plan.

Implementation score: 0.25 · Evidence confidence: Medium

Issue classification: quantum-critical uncertainty · Score treatment: score-reducing

Assurance: BNB Chain's report is explicitly labeled as research/evaluation, not a committed deployment plan. No mainnet activation date, governance proposal, or hard fork schedule exists.

Score 0.25 reflects public design/research plan status. The report identifies ECDSA and BLS vulnerabilities and proposes ML-DSA-44/pqSTARK but does not commit to deployment.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput
• https://www.cryptotimes.io/2026/05/15/bnb-chain-shares-post-quantum-readiness-update/

Claim: No PQC account creation, wallet tooling, transaction paths, custody paths, user-facing warnings, or migration prompts exist for BNB Chain or SIREN.

Coverage basis: No migration tooling or accessibility exists.

Implementation score: 0 · Evidence confidence: High

Issue classification: quantum-critical vulnerability · Score treatment: score-reducing

Quantum blocker: No PQC account creation or transaction path exists for BNB Chain users.

BNB Chain's PQC research report notes wallet address format compatibility is preserved in the proposed design, but no wallet, SDK, or RPC infrastructure supports PQC transactions today.

Claim: No enforcement mechanisms exist. Token ownership is renounced, precluding token-level enforcement.

Coverage basis: N/A at token level — renounced ownership prevents token-level enforcement.

Implementation score: 1 · Evidence confidence: Medium

Issue classification: none · Score treatment: not applicable

The token's setMode() function (controlling transfer restrictions) is onlyOwner and permanently inaccessible due to renounced ownership. This is actually beneficial for quantum security as no admin can unexpectedly alter transfer rules.

• https://skynet.certik.com/projects/siren

Claim: No quantum-specific emergency disclosure or incident-response process exists for SIREN or BNB Chain.

Coverage basis: No quantum-specific incident-response process identified.

Implementation score: 0 · Evidence confidence: Low

Issue classification: assurance-only caveat · Score treatment: note-only

Assurance: This is an assurance-only caveat. The absence of a formal quantum-specific incident-response playbook does not itself create a current quantum-vulnerable path. It is noted for operational completeness.

No bug bounty program exists (CertiK Skynet confirms no CertiK or 3rd party bug bounty). No quantum-specific security contact or disclosure process identified.

Claim: BNB Chain's PQC research proposes ML-DSA-44 (NIST FIPS 204 standardized), but this is not deployed on mainnet.

Coverage basis: Inherited from BNB Chain research; algorithm selection exists but is not in production.

Implementation score: 0.25 · Evidence confidence: Medium

Issue classification: quantum-critical uncertainty · Score treatment: score-reducing

Assurance: ML-DSA-44 is NIST FIPS 204 standardized (August 2024). BNB Chain selected NIST Level 2 (AES-128 equivalent) for efficiency. This is a sound algorithm choice but remains unimplemented in production.

Score 0.25 reflects that the algorithm has been selected and specified in a public research report but is not implemented on mainnet.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput
• https://www.cryptotimes.io/2026/05/15/bnb-chain-shares-post-quantum-readiness-update/

Claim: No independent cryptographic audit exists for BNB Chain's PQC implementation or SIREN's token contract.

Coverage basis: No audit of quantum-critical scope exists.

Implementation score: 0 · Evidence confidence: Medium

Issue classification: assurance-only caveat · Score treatment: confidence-only

Assurance: CertiK Skynet confirms SIREN is 'Not Audited By CertiK' and has no 3rd party audit. BNB Chain's PQC research report has not undergone independent cryptographic review. This is treated as confidence-only because the mainnet system is ECC-only (already known vulnerable) and the PQC implementation is not yet in production.

Audit absence does not reduce the QRI score further because the quantum-critical vulnerability (ECC-only mainnet) is already established and scored.

• https://skynet.certik.com/projects/siren

Claim: SIREN token contract is open-source and verified on BscScan. BNB Chain's PQC research report describes the implementation approach but production code is not deployed.

Coverage basis: Token contract is open-source; PQC implementation is described but not in production.

Implementation score: 0.5 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Assurance: Token contract source code is fully available and verified on BscScan (Solidity 0.8.20, OpenZeppelin-style ERC20 + Ownable). BNB Chain's PQC test code artifacts are described in the migration report but the report itself is public.

Score 0.50 reflects that the token contract is open-source and verified, but the PQC implementation is only at research/prototype stage.

• https://bscscan.com/token/0x997a58129890bbda032231a52ed1ddc845fc18e1#code

Claim: BNB Chain's PQC research discusses parameter selection (ML-DSA-44 vs ML-DSA-65/87 tradeoffs) but no production upgrade path is defined.

Coverage basis: Inherited from BNB Chain research; parameter agility discussed but not implemented.

Implementation score: 0.25 · Evidence confidence: Medium

Issue classification: assurance-only caveat · Score treatment: note-only

Assurance: BNB Chain's report discusses why ML-DSA-44 was chosen over higher-security variants based on signature size tradeoffs. This demonstrates parameter awareness but not production agility.

Score 0.25 reflects research-level discussion. No production parameter agility mechanism exists.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: ML-DSA-44 is a stateless signature scheme; stateful-signature safety concerns are not applicable.

Coverage basis: Satisfied by design — the selected PQC algorithm (ML-DSA-44/Dilithium) is stateless.

Implementation score: 1 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Assurance: This applies to the research/proposed design, not current production (which is ECDSA). The satisfied-by-design designation is for the proposed PQC algorithm selection, not the current production system.

Even though the proposed design avoids stateful signatures, this does not mitigate the current production ECDSA vulnerability.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput

Claim: BNB Chain's PQC research report includes detailed performance benchmarking showing ~40% throughput reduction.

Coverage basis: Performance analysis exists at research/prototype level.

Implementation score: 0.5 · Evidence confidence: High

Issue classification: none · Score treatment: not applicable

Assurance: Multiple independent news sources corroborate the performance findings. The report provides specific metrics: TPS drop from 4,973 to 2,997, block size increase from ~130KB to ~2MB, signature size increase from 65B to 2,420B.

Score 0.50 reflects prototype-level benchmarking. Performance analysis exists but the 40% throughput penalty is an unresolved blocker for production deployment.

• https://www.coindesk.com/markets/2026/05/19/bsc-s-quantum-defense-works-the-trade-off-is-40-slower-transaction-throughput
• https://www.cryptotimes.io/2026/05/15/bnb-chain-shares-post-quantum-readiness-update/