meme token
MemeCore M
MemeCore is an EVM-compatible Layer 1 blockchain tailored for meme coins, operating on a Proof of Staked Authority (PoSA) consensus mechanism derived from a standard Geth fork. The project relies entirely on classical cryptography (secp256k1 ECDSA) for spend authorization, consensus authentication, and account management. While a MiCA-compliant whitepaper includes a boilerplate disclosure acknowledging quantum computing as a potential risk, the project has no public cryptographic inventory, no PQC or hybrid-PQC implementation, and no migration roadmap. Unverified marketing claims regarding a 'post-quantum security layer' are directly contradicted by the open-source codebase. As of the evaluation date, MemeCore presents a full quantum-critical vulnerability surface across all applicable production layers.
Roadmap Only
Category breakdown
QRI Factors
Algorithm & Implementation Assurance
3 / 20
Migration Mechanism, Governance & Ecosystem Coordination
0 / 15
Migration Status & Value-at-Risk
0 / 25
Production Cryptographic Protection
0 / 35
Security Assessment & Evidence Preparedness
0 / 5
Critical Quantum Blockers
- Active production spend authorization remains entirely ECC-only (secp256k1 ECDSA) with no PQ or hybrid protection.
- No public cryptographic inventory or credible quantum mitigation design exists.
Key Risks
- Active production spend authorization and consensus authentication remain entirely ECC-only (secp256k1 ECDSA) with no PQ or hybrid protection.
- Standard EVM EOAs expose long-duration public keys on-chain upon first transaction, creating a long-exposure quantum vulnerability for all transacted accounts and dormant holdings.
- BEP-20 wrapper on BSC creates a two-way bridge dependency to a non-PQ-secure system, preserving a quantum-vulnerable fallback path for wrapped value.
- No public cryptographic inventory, migration roadmap, or quantum-specific incident response plan exists to coordinate a future transition.
Assurance Notes
- No independent audit covering quantum-critical implementation or PQC exists; CertiK audits cover general smart contract security, not quantum-specific cryptographic scope.
- MiCA whitepaper contains only boilerplate quantum risk disclosure, not a dedicated cryptographic inventory or mitigation plan.
- Unverified social media claims of a 'post-quantum decentralized security layer' are directly contradicted by the official Go-MemeCore GitHub repository, which is a standard Geth fork relying entirely on classical secp256k1 ECDSA.
- CertiK Skynet monitoring does not assess quantum readiness or PQC migration status.
Non-Scoring Caveats
- BEP-20 wrapper on BSC creates a two-way bridge dependency to a non-PQ-secure system, which would cap future QRI scores even if the L1 migrated.
- Standard EVM EOAs expose long-duration public keys on-chain upon first transaction, creating a long-exposure quantum vulnerability for all transacted accounts.
Evidence record
Claims and Caveats
Transaction
Spend authorization / transaction signatures are PQC or hybrid-PQC on mainnet
Claim: MemeCore L1 uses standard secp256k1 ECC for all transaction signatures.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Quantum blocker: Active production spend authorization remains entirely ECC-only.
Assurance: Verified via official Go-MemeCore GitHub repository (Geth fork).
Standard EVM ECDSA implementation.
Account
Account, address, public-key exposure, and key-derivation design prevents long-exposure quantum-vulnerable ownership paths
Claim: Native M token operates on MemeCore L1 with standard EVM address and transaction model.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: Standard EVM explorer behavior confirms classical ECC exposure and long-exposure public keys for transacted EOAs.
Long-exposure quantum vulnerability exists for all accounts that have sent a transaction.
Consensus
Consensus-critical authentication is PQC or hybrid-PQC where applicable
Claim: Consensus relies on PoA within epochs and staking-based validator selection; no PQ mechanisms described.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: Protocol design confirms no quantum-resistant consensus auth.
PoSA/Clique consensus relies on classical ECDSA for validator block signing.
State
State-integrity and data-availability mechanisms are quantum-safe where applicable
Claim: Standard EVM state trie and hashing.
Coverage basis: Classical ECC / Hash-based
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: Standard Geth fork state integrity.
While hashing is generally quantum-safe, state binding and authorization remain tied to vulnerable ECC signatures.
Privacy
Privacy and proof layers are quantum-safe where applicable
Claim: No privacy layer.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
P2P
P2P transport, node identity, and peer authentication are PQC, hybrid-PQC, or satisfied by design
Claim: Standard Geth P2P networking.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: operational/product caveat · Score treatment: score-reducing
Assurance: Node identity uses classical cryptography.
P2P identity is not directly spend-critical but remains a classical surface.
Wallet
Critical wallet, custody, HSM, signer, and hardware-wallet workflows support the production PQ/hybrid path
Claim: Standard EVM wallet compatibility.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: No PQ wallet support exists.
All custody and wallet workflows rely on classical ECDSA.
Migration
Percentage of economically relevant value-at-risk protected from quantum key-recovery attacks
Claim: 0% of value is protected by PQC.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Assurance: No migration has occurred or is planned.
Coverage is <25% (0%).
Migration
Critical wallets migrated, protected, or inherently PQ-native
Claim: No critical wallets are migrated or PQ-native.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Migration
Legacy vulnerable pools/accounts/UTXOs/contracts are identified, measurable, deprecated, migrated, frozen, or proven not to exist by design
Claim: No legacy pool management or deprecation policy exists.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
No mechanism to freeze or burn unmigratable vulnerable value.
Governance
Public migration or protection roadmap with sequencing, activation criteria, and dependencies
Claim: No public migration roadmap exists.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical uncertainty · Score treatment: score-reducing
Only boilerplate MiCA risk disclosure exists.
Governance
Migration accessibility and defaults
Claim: No PQ account creation or migration tooling exists.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Governance
Migration enforcement and coordination
Claim: No enforcement mechanisms or exchange coordination for PQ migration.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Governance
Emergency disclosure, incident-response, or governance process for quantum-related vulnerabilities
Claim: No quantum-specific IR playbook.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: assurance-only caveat · Score treatment: score-reducing
Algorithm
Uses NIST-standardized, standards-track, or broadly reviewed PQC/hybrid-PQC algorithms
Claim: No PQC algorithms used.
Coverage basis: Classical ECC
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical vulnerability · Score treatment: score-reducing
Relies entirely on secp256k1.
Algorithm
Independent cryptographic and implementation audit exists for the quantum-critical scope
Claim: No PQ audit exists.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: assurance-only caveat · Score treatment: score-reducing
Algorithm
Open-source, reproducible implementation
Claim: Go-MemeCore is open-source on GitHub.
Coverage basis: Classical ECC
Implementation score: 1 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Assurance: Code is publicly verifiable as a Geth fork.
Receives full implementation score for open-source transparency, though the underlying cryptography is classical.
Algorithm
Parameter agility and future upgrade path are documented
Claim: No PQ parameter agility documented.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: operational/product caveat · Score treatment: score-reducing
Algorithm
Stateful-signature safety, side-channel, fault-injection, or custody implementation risks are considered
Claim: No stateful PQ signatures used.
Coverage basis: N/A
Implementation score: 0 · Evidence confidence: High
Issue classification: none · Score treatment: not applicable
Algorithm
Performance and resource-impact analysis exists where PQ signature/verification costs could affect safe deployment
Claim: No PQ performance analysis exists.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: operational/product caveat · Score treatment: score-reducing
Preparedness
Public cryptographic inventory of critical public-key mechanisms and public quantum threat model
Claim: MiCA whitepaper acknowledges quantum risk as a boilerplate disclosure.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical uncertainty · Score treatment: score-reducing
Quantum blocker: No public cryptographic inventory or credible quantum mitigation design exists.
Assurance: Standard boilerplate risk disclosure for MiCA compliance, not a dedicated cryptographic inventory.
Prevents Stage 2 classification; caps Readiness & Risk at 10.
Preparedness
Public evidence record supporting the assessment
Claim: No evidence record supporting a quantum assessment.
Coverage basis: None
Implementation score: 0 · Evidence confidence: High
Issue classification: quantum-critical uncertainty · Score treatment: score-reducing
Report metadata