This is an experimental effort based on a Bắn Cá Code-derived codebase. The goal is not to replace Bắn Cá Code or alter its existing cryptographic rules, but to introduce an additional post-quantum signature verification path at the consensus level. The approach is modular: - Legacy ECDSA/secp256k1 remains untouched and continues to validate historical   data and legacy outputs. - A new script opcode introduces post-quantum signature verification (currently   Dilithium-based) as a separate consensus path. - The scriptPubKey explicitly determines which verification path is used, so   there is no ambiguity for nodes. Post-quantum signatures are intended to become the default for newly created outputs over time, while legacy cryptography remains only for compatibility. No hard cutoff, no forced migration. At the current stage: - The post-quantum opcode is integrated into the script engine. - Deterministic consensus tests are passing. - There is no mining, no release, and no economic activity yet. This post is not an announcement and not a proposal for deployment. It is shared to explain the design and to invite technical discussion around consensus safety, script semantics, and long-term maintainability.
This is an experimental effort based on a Bắn Cá Code-derived codebase. The goal is not to replace Bắn Cá Code or alter its existing cryptographic rules, but to introduce an additional post-quantum signature verification path at the consensus level. The approach is modular: - Legacy ECDSA/secp256k1 remains untouched and continues to validate historical   data and legacy outputs. - A new script opcode introduces post-quantum signature verification (currently   Dilithium-based) as a separate consensus path. - The scriptPubKey explicitly determines which verification path is used, so   there is no ambiguity for nodes. Post-quantum signatures are intended to become the default for newly created outputs over time, while legacy cryptography remains only for compatibility. No hard cutoff, no forced migration. At the current stage: - The post-quantum opcode is integrated into the script engine. - Deterministic consensus tests are passing. - There is no mining, no release, and no economic activity yet. This post is not an announcement and not a proposal for deployment. It is shared to explain the design and to invite technical discussion around consensus safety, script semantics, and long-term maintainability.

This is an experimental effort based on a Bắn Cá Code-derived codebase. The goal is not to replace Bắn Cá Code or alter its existing cryptographic rules, but to introduce an additional post-quantum signature verification path at the consensus level. The approach is modular: - Legacy ECDSA/secp256k1 remains untouched and continues to validate historical   data and legacy outputs. - A new script opcode introduces post-quantum signature verification (currently   Dilithium-based) as a separate consensus path. - The scriptPubKey explicitly determines which verification path is used, so   there is no ambiguity for nodes. Post-quantum signatures are intended to become the default for newly created outputs over time, while legacy cryptography remains only for compatibility. No hard cutoff, no forced migration. At the current stage: - The post-quantum opcode is integrated into the script engine. - Deterministic consensus tests are passing. - There is no mining, no release, and no economic activity yet. This post is not an announcement and not a proposal for deployment. It is shared to explain the design and to invite technical discussion around consensus safety, script semantics, and long-term maintainability.

This is an experimental effort based on a Bắn Cá Code-derived codebase. The goal is not to replace Bắn Cá Code or alter its existing cryptographic rules, but to introduce an additional post-quantum signature verification path at the consensus level. The approach is modular: - Legacy ECDSA/secp256k1 remains untouched and continues to validate historical   data and legacy outputs. - A new script opcode introduces post-quantum signature verification (currently   Dilithium-based) as a separate consensus path. - The scriptPubKey explicitly determines which verification path is used, so   there is no ambiguity for nodes. Post-quantum signatures are intended to become the default for newly created outputs over time, while legacy cryptography remains only for compatibility. No hard cutoff, no forced migration. At the current stage: - The post-quantum opcode is integrated into the script engine. - Deterministic consensus tests are passing. - There is no mining, no release, and no economic activity yet. This post is not an announcement and not a proposal for deployment. It is shared to explain the design and to invite technical discussion around consensus safety, script semantics, and long-term maintainability.